For apps running in Kubernetes, it's particularly important to be storing log messages in a central location. I'd argue that this is important for all apps, whether or not you're using Kubernetes or docker, but the ephemeral nature of pods and containers make the latter cases particularly important.

A Step by Step Guide to Logging with ElasticSearch, Kibana, ASP.NET Core 2.1 and Docker

Usually, when getting errors logged through MEL, all of the HTTP context data is logged as part of the error, making it easy to spot why an error happened or at least making it a lot easier recreating the error. Today's error didn't include much more information than an error message and a request-id.

Properties, such as MVC-specific features like the action method ID, RazorPages Handler name, or the ModelValidationState are only available in an MVC context, so can't be directly accessed by Serilog's middleware. In this post, I show how you can create action/page filters to record these properties for you, which the middleware can access later when creating the log.

In this post I will explore and highlight an approach to logging which you can apply in high-performance, high load applications to reduce the overhead of logging.

Logging, is perhaps one of the most essential components in an application. An application once moved to production still needs maintenance and monitoring for any uncovered bugs and runtime errors and a good logging mechanism implemented with essential attributes being logged can be a lot helpful in understanding the issues better.