Serilog MinimumLevel Override is not working

Question

{
"Logging":{
  "LogLevel":{
    "Default": "Warning",
    "System.Net.Http.HttpClient.SomeClassLibraryName": "Error"
   }
  }
}

If I add the above code in my app settings then the logs for above-provided namespace only get written for the error and it works.

But when I try to achieve the same thing using the logging configuration for Serilog in .NET 6 WEB API it does not work. This is the method of which I am calling for setting the log configuration :

public static void LoggingConfiguration()
{
    Log.Logger = new LoggerConfiguration()
        .MinimumLevel.Information()
        .MinimumLevel.Override("System.Net.Http.HttpClient.SomeClassLibraryName", LogEventLevel.Error)
        .MinimumLevel.Override("Microsoft", LogEventLevel.Information)
        .MinimumLevel.Override(SomeClassLibraryName, LogEventLevel.Information)
        .Enrich.FromLogContext()
        .WriteTo.Async(c => c.File("Logs/Log.txt", rollingInterval: RollingInterval.Day))
        .WriteTo.Async(c => c.Console())
        .CreateLogger();
}

I have tested this code for Microsoft and by changing the minimum level from information to warning and error, it works for them but is not working for a specific case.

I have explored the following options so far but did not find any satisfactory results.

https://github.com/serilog/serilog/wiki/Writing-Log-Events#source-contexts

https://github.com/serilog/serilog/issues/1390

https://github.com/serilog/serilog-extensions-logging/issues/177

And where do you call this LoggingConfiguration? I would expect it requires registration via options or smth. Like here: learn.microsoft.com/en-us/aspnet/core/fundamentals/logging/… — Pawel
– Pawel, Commented Aug 17, 2024 at 17:44
The method is being called in the Program.cs and its working fine, I hv tested some scenerios — Hakuna
– Hakuna, Commented Aug 17, 2024 at 17:47
"System.Net.Http.HttpClient.SomeClassLibraryName": "Error", at the same time if I put this in the app settings it works perfectly, but due to constraint I want to control it via my custom method not app settings — Hakuna
– Hakuna, Commented Aug 17, 2024 at 17:49

Pawel · Accepted Answer · 2024-08-17 19:20:59Z

1

You should rely on built-in registration like here.

Try moving the registration to builder like so:

var builder = WebApplication.CreateBuilder();
builder.Logging.SetMinimumLevel(LogLevel.Warning);

or

var builder = WebApplication.CreateBuilder();
builder.Logging.AddFilter("System.Net.Http.HttpClient.ClassLibraryName", LogLevel.None);

answered Aug 17, 2024 at 19:20

Pawel

6344 silver badges19 bronze badges

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

Comments

Guru Stron · Accepted Answer · 2024-08-17 22:00:11Z

1

Serilog does not use the default Logging section, by default it uses Serilog one (with MinimumLevel for log level configs, see for example How to prevent logging all of my Entity Framework SQL queries? or the docs), it is used by the build-in logger, so either register Serilog (from the Serilog.AspNetCore docs):

LoggingConfiguration(); // call your Serilog setup
// install the Serilog.AspNetCore package
builder.Services.AddSerilog();

or use the build-in logger APIs (docs):

builder.Logging.SetMinimumLevel(LogLevel.Warning);
builder.Logging.AddFilter("System.Net.Http.HttpClient.ClassLibraryName", LogLevel.None);

Though personally I would recommend to stick with the config approach as far more flexible one.

answered Aug 17, 2024 at 22:00

Guru Stron

150k11 gold badges186 silver badges231 bronze badges

Collectives™ on Stack Overflow

Serilog MinimumLevel Override is not working

2 Answers 2

Comments

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related