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

.NET 8–Keyed/Named Services

A feature that a lot of IoC container libraries support but that was missing in the default DI container provided by Microsoft is the support for Keyed or Named Services. This feature allows you to register the same type multiple times using different names, allowing you to resolve a specific instance based on the circumstances. Although there is some controversy if supporting this feature is a good idea or not, it certainly can be handy. To support this feature a new interface IKeyedServiceProvider got introduced in .NET 8 providing 2 new methods on our ServiceProvider instance: object? GetKeyedService(Type serviceType, object? serviceKey); object GetRequiredKeyedService(Type serviceType, object? serviceKey); To use it, we need to register our service using one of the new extension methods: Resolving the service can be done either through the FromKeyedServices attribute: or by injecting the IKeyedServiceProvider interface and calling the GetRequiredKeyedServic...
Read more

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

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...
Read more