Hangfire does not log exception using configured Logger

Question

Starting from Hangfire 1.3.0, you are not required to do anything, if your application already uses one of the following libraries through the reflection (so that Hangfire itself does not depend on any of them). Logging implementation is automatically chosen by checking for the presence of corresponding types in the order shown below.

Serilog
NLog
Log4Net
EntLib
Logging
Loupe
Elmah

I have ASP.NET Core 2.0 application that is using Serilog like below

public class Program
{
    public static void Main(string[] args)
    {
        BuildWebHost(args).Run();
    }

    public static IWebHost BuildWebHost(string[] args) =>
        WebHost.CreateDefaultBuilder(args)
        .UseStartup<Startup>()
        .UseApplicationInsights()
        .UseUrls("http://*:40006")
        .ConfigureAppConfiguration((hostingContext, config) =>
        {
           // removed for bravity
        })
        .ConfigureLogging((hostingContext, logging) =>
        {                
                Log.Logger = new LoggerConfiguration()
                .ReadFrom.Configuration(hostingContext.Configuration)
                .CreateLogger();

                logging.AddSerilog();

        })
        .Build();
}

The application is configured to use Hangfire. During background job processing if there is any exception occurs, Hangfire re-tries the job 10 times with increasing delay as expected, and it shows the exceptions in dashboard.

Issue
The Hangfire dashboard shows the exception on UI however it does not log the exception into configured Serilog sink.

Note: The Hangfire dashboard shows exception but it formats the exception see here which hides critical information about the exception. I think if it logs the exception, Serilog logger would log the complete exception.

score 1 · Answer 1 · answered Jun 12 '20 at 09:08

I had the same issue with the latest Hangfire version using .NET Core 3.1.

The solution was to call the UseSerilogLogProvider() method of IGlobalConfiguration in StartUp.cs.

For example:

 GlobalConfiguration.Configuration.UseSerilogLogProvider();

or

services.AddHangfire(configuration => configuration
 .UseSimpleAssemblyNameTypeSerializer()
 .UseRecommendedSerializerSettings()
 .UseSerilogLogProvider());

Normally this call shouldn't be needed but there are some cases where automatic wiring isn't working (an example would be referencing multiple logging providers). You can read more about this in the official Hangfire documentation: Configure Logging

Hangfire does not log exception using configured Logger

1 Answers1