Centralize your Logging with Docker + Seq + .Net Core

Photo by Jon Butterworth on Unsplash

Logging is a big part of software development for many years now. One can argue that a logging mechanism is a must-have part of any application or library. I would agree with that statement.

First, why Logging?

Imagine this, you have your application in production, and your application have an error. You can’t Debug it. Logs might be the only information you have.

But don’t be confuse Logging with Monitoring.

Monitoring

Monitoring means there’s an automatic tool that reports information on your application. That information can be errors, performance or information about requests made.

Logging

You actively writes messages and exceptions to log. You can save the logs in a normal .txt file(not recommended). Or you can use Data Bases.

Ways to Log

• NoSQL -> CouchDB, logs are stored in JSON format.
• Time-series -> InfluxDB, store time-based events, better choise for high demanding logging.
• Searchables -> Seq, take the care to add, index and search with diferente filters.
• Files -> just logging into a .txt file, .json file.