Skip to main content

Serilog - Filter out the ASP.NET Core info

When you are using the built-in logging in ASP.NET Core, you can filter out specific information by changing the log levels in the appsettings.json:

But when you switch to Serilog, this no longer works and the configuration values are ignored.

Our original configuration looked like this:

Here is what was logged by default after switching to Serilog:

2022-02-03 12:17:07.861 +01:00 [WRN] Failed to determine the https port for redirect.

2022-02-03 12:17:58.429 +01:00 [WRN] Failed to determine the https port for redirect.

2022-02-03 12:19:19.555 +01:00 [WRN] Failed to determine the https port for redirect.

2022-02-03 12:20:21.553 +01:00 [INF] OnStarted has been called.

2022-02-03 12:20:21.631 +01:00 [INF] Request starting HTTP/1.1 POST http://localhost/mail/ application/json;+charset=utf-8 318

2022-02-03 12:20:21.631 +01:00 [INF] Request starting HTTP/1.1 POST http://localhost/mail/ application/json;+charset=utf-8 318

2022-02-03 12:20:21.631 +01:00 [INF] Request starting HTTP/1.1 POST http://localhost/mail/ application/json;+charset=utf-8 318

2022-02-03 12:20:21.636 +01:00 [INF] Request starting HTTP/1.1 POST http://localhost/mail/ application/json;+charset=utf-8 318

2022-02-03 12:20:21.639 +01:00 [INF] Request starting HTTP/1.1 POST http://localhost/mail/ application/json;+charset=utf-8 318

2022-02-03 12:20:21.639 +01:00 [INF] Request starting HTTP/1.1 POST http://localhost/mail/ application/json;+charset=utf-8 318

2022-02-03 12:20:21.640 +01:00 [INF] Request starting HTTP/1.1 POST http://localhost/mail/ application/json;+charset=utf-8 318

2022-02-03 12:20:21.640 +01:00 [INF] Request starting HTTP/1.1 POST http://localhost/mail/ application/json;+charset=utf-8 318

2022-02-03 12:20:21.640 +01:00 [INF] Request starting HTTP/1.1 POST http://localhost/mail/ application/json;+charset=utf-8 318

2022-02-03 12:20:21.640 +01:00 [INF] Request starting HTTP/1.1 POST http://localhost/mail/ application/json;+charset=utf-8 318

2022-02-03 12:20:21.671 +01:00 [WRN] Failed to determine the https port for redirect.

2022-02-03 12:20:21.677 +01:00 [INF] Executing endpoint 'Mailing.API.Controllers.MailController.Send (Mailing.API)'

2022-02-03 12:20:21.677 +01:00 [INF] Executing endpoint 'Mailing.API.Controllers.MailController.Send (Mailing.API)'

2022-02-03 12:20:21.677 +01:00 [INF] Executing endpoint 'Mailing.API.Controllers.MailController.Send (Mailing.API)'

2022-02-03 12:20:21.706 +01:00 [INF] Route matched with {action = "Send", controller = "Mail"}. Executing controller action with signature System.Threading.Tasks.Task`1[Microsoft.AspNetCore.Mvc.IActionResult] Send(Mailing.DTO.SendMailMessage, System.Threading.CancellationToken) on controller Mailing.API.Controllers.MailController (Mailing.API).

2022-02-03 12:20:21.717 +01:00 [INF] Route matched with {action = "Send", controller = "Mail"}. Executing controller action with signature System.Threading.Tasks.Task`1[Microsoft.AspNetCore.Mvc.IActionResult] Send(Mailing.DTO.SendMailMessage, System.Threading.CancellationToken) on controller Mailing.API.Controllers.MailController (Mailing.API).

2022-02-03 12:20:21.729 +01:00 [INF] Route matched with {action = "Send", controller = "Mail"}. Executing controller action with signature System.Threading.Tasks.Task`1[Microsoft.AspNetCore.Mvc.IActionResult] Send(Mailing.DTO.SendMailMessage, System.Threading.CancellationToken) on controller Mailing.API.Controllers.MailController (Mailing.API).

2022-02-03 12:20:21.794 +01:00 [INF] Configured endpoint mediator, Consumer: Mailing.API.Domain.MailConsumer

2022-02-03 12:20:21.900 +01:00 [INF] Executing action method Mailing.API.Controllers.MailController.Send (Mailing.API) - Validation state: "Valid"

2022-02-03 12:20:21.900 +01:00 [INF] Executing action method Mailing.API.Controllers.MailController.Send (Mailing.API) - Validation state: "Valid"

2022-02-03 12:20:21.900 +01:00 [INF] Executing action method Mailing.API.Controllers.MailController.Send (Mailing.API) - Validation state: "Valid"

Whoops! That’s way too much information.

To fix it, you can override the minimal loglevel in Serilog for specific targets:

This will help you to keep the amount of log data under control.

Labels:

Popular posts from this blog

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.
Read more

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...
Read more

Cleaner switch expressions with pattern matching in C#

Ever find yourself mapping multiple string values to the same result? Being a C# developer for a long time, I sometimes forget that the C# has evolved so I still dare to chain case labels or reach for a dictionary. Of course with pattern matching this is no longer necessary. With pattern matching, you can express things inline, declaratively, and with zero repetition. A small example I was working on a small script that should invoke different actions depending on the environment. As our developers were using different variations for the same environment e.g.  "tst" alongside "test" , "prd" alongside "prod" .  We asked to streamline this a long time ago, but as these things happen, we still see variations in the wild. This brought me to the following code that is a perfect example for pattern matching: The or keyword here is a logical pattern combinator , not a boolean operator. It matches if either of the specified pattern...
Read more