WriteTo.Seq(..) doesn't respect MinimumLevel.Override

I’m configuring Serilog with Seq like that:

hostBuilder.UseSerilog((builder, loggerConfiguration) =>
            {
                var env = builder.HostingEnvironment;
                var seqConfig = builder.Configuration.GetSection("Seq");

                var loggingLevelSwitch = new LoggingLevelSwitch();

                loggerConfiguration.MinimumLevel.ControlledBy(loggingLevelSwitch)
                                   .MinimumLevel.Override("Microsoft", LogEventLevel.Warning)
                                   .MinimumLevel.Override("BeatPulse", LogEventLevel.Warning)
                                   .Enrich.FromLogContext()
                                   .Enrich.WithMachineName()
                                   .Enrich.WithEnvironmentUserName()
                                   .Enrich.WithProperty("Environment", env.EnvironmentName)
                                   .WriteTo.Console()
                                   .WriteTo.Seq(url ?? seqConfig["Url"], apiKey: apiKey ?? seqConfig["ApiKey"], controlLevelSwitch: loggingLevelSwitch);
            });

The console sink respects the override and doesn’t prompt messages from Microsoft and BeatPulse. Unfortunately the Seq-Sink does not.

I’m not sure if it’s a wrong config or it isn’t supported yet?

[stephanprobst]

Hey @nblumhardt ! I finally found it. We had multiple clients which logged to the same seq instance (which wasn’t intended in this case). It resulted in a view where you could think that the logging doesn’t work. Infact I looked at messages from a different client. So I have to apologize. It was all my fault. Many thanks for your help and work!

[nblumhardt]

Awesome, glad it turned out to be something simple 👍