NET developer, but as it turns out that Console‘s static Write and WriteLine methods both send their output to STDOUT. STDOUT and STDERR aren’t terms that I was familiar with as a. CloudWatch and GCP Logs integrate directly with their own logging drivers, while the fluentd logging driver makes it easy to integrate with popular products like Elasticsearch.Īn application running in Docker has two output streams, STDOUT and STDERR, which are persisted by the configured logging driver. By default, the Docker host machine is configured to write logs to a text file, where each row is a JSON document that includes the time the event occurred and the related log message.Ī text file isn’t the only destination for the logs - other logging drivers make it possible to send data to external sources. Logging Infrastructureĭocker determines the destination for log messages via a logging driver. This post explores the building blocks upon which Docker logging is built, and how it relates to ASP.NET Core’s logging.
Docker has its own log handling behaviour that integrates nicely with ASP.NET Core when running on Linux. ASP.NET Core’s built-in logging mechanisms give you control over most aspects of an application’s logs, from where they are written to how they are formatted.
