Log levels explained

I’m always struggling with the method/level to use when logging from my application. In his Modern Structured Logging With Serilog and Seq pluralsight course Jason Roberts explains it this way:

Level Explain Example
Verbose how technical “calculated hash {hash} for order {id}”
Debug how functional “applied vip discount to user {user}”
Information what “created order {id}”
Warning problems “save of order {id} failed, will retry in 5 sec”
Error unexpected failure “saved of order {id} failed”
Fatal critical/stop “unhandled exception”

We have adopted this and have improved our logging quality.

If everything seems to be going well, you have obviously overlooked something
Murphy’s law

About erictummers

Working in a DevOps team is the best thing that happened to me. I like challenges and sharing the solutions with others. On my blog I’ll mostly post about my work, but expect an occasional home project, productivity tip and tooling review.
This entry was posted in Development and tagged , . Bookmark the permalink.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.