Serilog alongside Azure Monitor OpenTelemetry

[SamueleFurnari]

Description
In an AspNet 8.0 project I configured Azure Monitor OpenTelemetry to make monitoring easy on Microsoft Azure cloud platform. At the same time I would like to use the flexibility of serilog to write formatted logs to console and file.

In the project I also use entity framework. If I disable Serilog, on Azure Application Insight I also find the queries towards the database logged. If I enable Serilog, I no longer see the traces.

On stack overflow I found this question, but by configuring serilog as indicated, I see the traces on app insights but I still do not see the sql entity framework queries.

Thanks a lot for any help!
Samuele

Reproduction

1. Add Serilog configuration in app.settings:

"Serilog": {
  "Using": [ "Serilog.Sinks.Console", "Serilog.Sinks.File" ],
  "WriteTo": [
    { "Name": "Console" },
    {
      "Name": "File",
      "Args": {
        "path": "/logs/log-.txt",
        "rollingInterval": "Day",
        "rollOnFileSizeLimit": true,
        "formatter": "Serilog.Formatting.Compact.CompactJsonFormatter, Serilog.Formatting.Compact"
      }
    }
  ],
  "Enrich": [ "FromLogContext", "WithMachineName", "WithThreadId" ]
}

2. Configure Serilog and Azure Monitor Telemetry as below.

var resourceAttributes = new Dictionary<string, object>
{
    { "service.name", "my-service" },
    { "service.namespace", "my-namespace" },
    { "service.instance.id", "my-instance" }
};

builder.Logging.ClearProviders();

builder.Services
    .AddOpenTelemetry()
    .UseAzureMonitor()
    .ConfigureResource(resourceBuilder => resourceBuilder.AddAttributes(resourceAttributes));

builder.Services.AddSerilog(
    (services, lc) => lc
        .ReadFrom.Configuration(builder.Configuration)
        .ReadFrom.Services(services)
        .Enrich.FromLogContext(), writeToProviders: true);

Expected behavior
I want to see traces logged on Console, File and Application Insight but with this configuration I see traces only on Console and File logging.

Relevant package, tooling and runtime versions
I'm using Azure.Monitor.OpenTelemetry.AspNetCore v. 1.2.0 and Serilog.AspNetCore v. 9.0.0
The .NET framework is v. 8.0

[sciocoder]

same configuration and relevant package version, traces are successfully sent to Application Insight but unhandled exceptions are not tracked

[bh3605]

@sciocoder What does your configuration look like? OP says his traces aren't showing in Application Insights.

I have a similar situation.

public void ConfigureHost(IHostBuilder host)
{
    host.UseSerilog((ctx, _, logConfig) =>
    {
        logConfig.ReadFrom.Configuration(ctx.Configuration);
    });
}

public void AddOpenTelemetry(IServiceCollection services)
{
    services.AddOpenTelemetry().UseAzureMonitor();
}

    "Serilog": {
        "MinimumLevel": {
            "Default": "Information",
            "Override": {
                "Microsoft.AspNetCore.Mvc": "Warning",
                "Microsoft.AspNetCore.Routing": "Warning",
                "Microsoft.AspNetCore.Hosting": "Warning"
            }
        },
        "Enrich": [ "FromLogContext", "WithMachineName", "WithThreadId" ],
        "Destructure": [
            {
                "Name": "ToMaximumDepth",
                "Args": { "maximumDestructuringDepth": 4 }
            },
            {
                "Name": "ToMaximumStringLength",
                "Args": { "maximumStringLength": 100 }
            },
            {
                "Name": "ToMaximumCollectionCount",
                "Args": { "maximumCollectionCount": 10 }
            }
        ]
    }

[nblumhardt]

Hi! This is most likely a usage issue: if Azure Monitor relies on the MEL pipeline (e.g. UseAzureMonitor() adds providers) these will be lost when builder.Services.AddSerilog() is called, since it replaces the MEL pipeline with Serilog.

To plug Serilog into the MEL pipeline, and have both coexist, use builder.Logging.AddSerilog() instead.

HTH!

[Frulfump]

Hi! This is most likely a usage issue: if Azure Monitor relies on the MEL pipeline (e.g. UseAzureMonitor() adds providers) these will be lost when builder.Services.AddSerilog() is called, since it replaces the MEL pipeline with Serilog.

To plug Serilog into the MEL pipeline, and have both coexist, use builder.Logging.AddSerilog() instead.

HTH!

Oh is it possible to add an analyzer and docs note (if it doesn't already exist) for that?

[nblumhardt]

I'll move this to the serilog-extensions-logging repo, which would be the appropriate place to try to document the differences between the two models.