Open fgheysels opened 2 years ago
Interesting. But the Arcus request tracking is also there, right? That doesn't fix a little bit the problem? Otherwise, yeah, definitely a thing to consider.
The way the Serilog request middleware component is set up, it seems that they do kind of the same thing as we do with the HTTP request tracking middleware, but since we also make sure that we provide additional options for tracking headers and bodies, the added-value of this middleware component is maybe not much anymore. It could even obscure the logging as we would track the request twice, in that case.
Should we include
UseSerilogRequetLogging
in the web-api template ?With regular logging, logs are quite stuffed with traces regarding the request and response that is generated by ASP.NET. When including the
UseSerilogRequestLogging
middleware, those logs are tidied up a little bit. More background info can be found here: https://andrewlock.net/using-serilog-aspnetcore-in-asp-net-core-3-reducing-log-verbosity/