Structured variables not shown when Serilog used

[vladopandzic]

I get logs to cloudwatch however variables are not recognized inside aws cloudwatch.
This is my configuration:

"serilog": {
    "Using": [
      "AWS.Logger.SeriLog"
    ],
    "LogGroup": "rimacSD-alecs-api-production",
    "IncludeLogLevel": true,
    "IncludeCategory": true,
    "IncludeNewline": true,
    "IncludeException": true,
    "IncludeEventId": true,
    "IncludeScopes": true,
    "Region": "eu-west-1",
    "MinimumLevel": {
      "Default": "Information",
      "Override": {
        "Microsoft": "Warning",
        "System": "Warning",
        "Microsoft.Hosting.Lifetime": "Information"
      }
    },
    "Enrich": [ "FromLogContext", "WithMachineName", "WithEnvironmentUserName", "FromLogContext" ],
    "WriteTo": [
      {
        "Name": "AWSSeriLog",
        
      }
    ]
  },

If I use alternative Serilog.Sinks.AwsCloudWatch then I get variables inside cloudwatch but I can't figure out how to remove logs
from Microsoft and would rather use this official library.

Inide Program.cs I have this:

        public static IHostBuilder CreateHostBuilder(string[] args) =>
            Host.CreateDefaultBuilder(args)
                .UseSerilog((hostingContext, services, loggerConfiguration) =>
                {
                    _ = loggerConfiguration.ReadFrom.Configuration(hostingContext.Configuration)
                                        .Enrich.WithProperty("Application", hostingContext.HostingEnvironment.ApplicationName)
                                        .Enrich.WithProperty("Environment", hostingContext.HostingEnvironment.EnvironmentName);
                })
                .ConfigureWebHostDefaults(webBuilder =>
                {
                    _ = webBuilder.UseStartup<Startup>();
                });
    }

[ashishdhingra]

Hi @VladoP,

Good morning.

Thanks for posting the issue. Could you please elaborate what variables you are referring to and provide some code sample to investigate the issue? Any logs would also be helpful. Are you referring to enrichers FromLogContext, WithMachineName and WithEnvironmentUserName?

Preferred format for sharing above information:

Expected Behavior

Current Behavior

Possible Solution

Steps to Reproduce (for bugs)

Context

Your Environment

• AWSSDK.Core version used:
• Service assembly and version used:
• Operating System and version:
• Visual Studio version:
• Targeted .NET platform:

.NET Core Info

• .NET Core version used for development:
• .NET Core version installed in the environment where application runs:
• Output of dotnet --info:
• Contents of project.json/project.csproj:

Thanks,
Ashish

[github-actions]

This issue has not received a response in a week. If you want to keep this issue open, please just leave a comment below and auto-close will be canceled.

I'm also seeing an issue with structured logging variables not showing up with the .Net Core API, so I don't think it's Serilog specific. I have the following configuration:

builder.Services.AddLogging(config =>
{
    config.AddAWSProvider(builder.Configuration.GetAWSLoggingConfigSection());
    config.SetMinimumLevel(LogLevel.Trace);
});

Here is my appSettings.json:

  "AWS.Logging": {
    "Region": "us-east-2",
    "LogGroup": "WidgetService",
    "LogLevel": {
      "Default": "Information",
      "System": "Information",
      "Microsoft": "Information"
    }
  },

I'm logging the following structured log:

_logger.LogError("error test message {Test} {Field1} {Field2}", "Text", "1", 42);

I would expect this to be sent as a structured log to CloudWatch, but it appears to send an interpolated string:

Here, I would expect to see the variables:
@test Text
@field1 1
@field2 42

It appears the library doesn't preserve the message. I'm guessing this is what the OP was expressing, that when they use Serilog with Serilog's AWS sink that it correctly preserves the variables, but when using the "official" microsoft library for logging to CloudWatch with Serilog that it isn't preserving the variables. Seems like it's because the core library just doesn't properly support structured logging.