ASP.NET 5: What is the recommended approach to catch and log all unhandled exceptions?

Question

I'm building an api app. In the old ASP.NET there was Application_Error() to catch all unhandled exceptions

protected void Application_Error()
{
    var exception = Server.GetLastError();
    _logger.FatalException("Fatal error.", exception);
}

What should be used in ASP.NET 5?

There is a nice explanation of this on SO. Use ILoggerProvider and ILogger from the namespace Microsoft.Framework.Logging. The details can be found here. stackoverflow.com/questions/28385889/…. The github also have sample for same. github.com/aspnet/Diagnostics/tree/dev/samples/… — J-D
– J-D, Commented Jan 6, 2016 at 5:41

Boris Lipschitz · Accepted Answer · 2016-01-06 07:10:29Z

5

The solution is to add a custom filter. This is how it could be done:

public void ConfigureServices(IServiceCollection services)
{
    services.AddMvc(options => options.Filters.Add(new MyExceptionFilter()));
}

Now the custom filter should derive from IExceptionFilter:

public class MyExceptionFilter : ActionFilterAttribute, IExceptionFilter
{
    public void OnException(ExceptionContext context)
    {

    }
}

Unfortunately, it doesn't catch exceptions during Startup.Configuration()

answered Jan 6, 2016 at 6:02

Boris Lipschitz

9,5766 gold badges55 silver badges64 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

Have you been able to find a better way of doing this like "Application_Error" on asp. net 4