With elmah.io, monitoring your ASP.NET Core application requires no more than a few lines of configuration. We automatically pick up all errors on your website and log them to a log on elmah.io.
Errors are decorated with a lot of contextual information to help you to fix each error. Server variables, cookies and form values can play an essential part in debugging why an error is happening. Using our well-documented NuGet package for ASP.NET Core, appending custom variables is a piece of cake.
ASP.NET Core introduced the new concept of health checks. Using health checks, your application continuously verifies its own state by executing a set of predefined rules. With the elmah.io integration for ASP.NET Core Health Checks, failing health checks are automatically logged as failing heartbeats on elmah.io.
With elmah.io Uptime Monitoring, you are notified as soon as your application starts failing. By combining Uptime Monitoring with ASP.NET Core Health Checks, you are told exactly why your endpoints are failing. You won't believe the difference in time-to-fix when going from "Your website failed with a status code of 500" to "Your website failed because it couldn't connect to the database".
Logging uncaught exceptions is one thing. What about all of the log statements that developers need to add today? With our integration with Microsoft.Extensions.Logging, you can log everything from verbose to fatal messages from ASP.NET Core.
Since messages logged through Microsoft.Extensions.Logging goes in the same error log as uncaught errors, existing rules and notifications just work.
The elmah.io integration for Microsoft.Extensions.Logging supports structured logging. If you ever tried scrolling through file-based log files, you know how important being able to separate and search by properties can be.