Cloud logging for Umbraco

Quick Fixes

elmah.io provides quick fixes developed especially for Umbraco. With elmah.io you have the perfect overview of your Umbraco installation.

But wait, there's more. We analyzed thousands of Umbraco errors and found a set of common log messages in Umbraco. With this set of data, we provide you with links to the best and most relevant help articles from the Umbraco documentation.

Uptime Monitoring & Heartbeats

Logging errors is one aspect of securing a well-working website. But it doesn't solve everything. You also need to make sure that users can reach your website and maybe even from different parts of the world.

With elmah.io Uptime Monitoring, we ping your Umbraco sites from up to 5 different regions every 5 minutes. If your site is not accessible, an error is logged in your error log. This will trigger all of the notification rules and app integrations already configured on your account.

elmah.io Heartbeats is a feature to monitor the internal state of your website that is not visible from the public web. The elmah.io package for Umbraco support native integration between Umbraco's health check feature and elmah.io Heartbeats. Publish health checks directly to elmah.io and get a notification as soon as one or more features inside Umbraco starts complaining.

Let your AI agent read your Umbraco errors

Connect Claude Code, Cursor, VS Code or Visual Studio to the elmah.io MCP server. Your agent can list new errors, read the stack trace and message details, check what changed after a deployment, and mark an error as fixed once you have shipped the change.

In Claude Code, add the server with one command:

claude mcp add --transport http --client-id claudecode elmahio https://mcp.elmah.io/mcp

The MCP server is included on every plan and is currently in beta. Set up the MCP server.

Set up in a few lines

Install the NuGet package, add elmah.io to Program.cs with your API key and log ID, and add the Serilog sink to also log everything Umbraco writes to its log.

dotnet add package Elmah.Io.Umbraco

builder.Services.AddElmahIo(options =>
{
    options.ApiKey = "API_KEY";
    options.LogId = new Guid("LOG_ID");
});

WebApplication app = builder.Build();

await app.BootUmbracoAsync();

app.UseElmahIo();

app.UseUmbraco()
    // ...

{
  "Serilog": {
    "WriteTo": [
      {
        "Name": "ElmahIo",
        "Args": {
          "apiKey": "API_KEY",
          "logId": "LOG_ID"
        }
      }
    ]
  }
}

Call UseElmahIo after the middleware that handles exceptions and authentication, and before UseUmbraco. The example is for Umbraco 13 and newer. Umbraco 10 to 12 use Startup.cs, and the documentation has the steps for those and for Umbraco 8 and 7. Your API key and log ID are shown on the install page when you sign up. Read the full setup guide.

How it looks

Here is what elmah.io logs from an Umbraco site:

• Uncaught exceptions, with the request, server variables, form values and the stack trace.
• The messages Umbraco writes to its Serilog log, when the sink is configured.
• Umbraco health check results as heartbeats, with a notification when a check fails.
• Links to relevant help articles from the Umbraco documentation for common errors.

Frequently asked questions