Logs are an essential operational tool.
But they are only useful if you're able to make sense out of them.
Most important for that: using log levels consistently!
· ℹ️ Trace
· 💡 Debug
· ⚪️ Info
· 🟠 Warn
· 🔴️ Error
· ⚡️ Fatal
A small thread about when to use what 🧵↓
But they are only useful if you're able to make sense out of them.
Most important for that: using log levels consistently!
· ℹ️ Trace
· 💡 Debug
· ⚪️ Info
· 🟠 Warn
· 🔴️ Error
· ⚡️ Fatal
A small thread about when to use what 🧵↓
(1/7) ℹ️ Trace
Your most verbose logs containing the most fine-grained information.
It gives you detailed insights into what's happening - not only in your code but also in third-party libraries.
Can go as far as documenting every step in a single algorithm.
Your most verbose logs containing the most fine-grained information.
It gives you detailed insights into what's happening - not only in your code but also in third-party libraries.
Can go as far as documenting every step in a single algorithm.
(2/7) 💡 Debug
Less information than 'trace' level, but still extended to a way that's needed to troubleshoot problems in detail.
Majorly used for pre-production/testing environments and often logs out sensitive information that can't be logged on production.
Less information than 'trace' level, but still extended to a way that's needed to troubleshoot problems in detail.
Majorly used for pre-production/testing environments and often logs out sensitive information that can't be logged on production.
(3/7) ⚪ ️Info
The base level of logging.
These logs help you to identify the certain states the application or process has gone through, e.g. "User successfully authenticated" or "Payment information has been processed".
There's no granularity rule, but don't overdo it.
The base level of logging.
These logs help you to identify the certain states the application or process has gone through, e.g. "User successfully authenticated" or "Payment information has been processed".
There's no granularity rule, but don't overdo it.
(4/7) 🟠 Warn
Something unexpected happened.
It doesn't implicitly mean that a process has failed or the user received an error.
It's a warning about an expected state and further actions that have to be taken, but not immediately.
Something unexpected happened.
It doesn't implicitly mean that a process has failed or the user received an error.
It's a warning about an expected state and further actions that have to be taken, but not immediately.
(5/7) 🔴 Error
Some business functions may be broken or a dependent system is not available, but your core business processes are still intact.
Mostly it requires immediate action and your users are (partly) affected.
Some business functions may be broken or a dependent system is not available, but your core business processes are still intact.
Mostly it requires immediate action and your users are (partly) affected.
(6/7) ⚡ Fatal
Crucial functions of your application are not working and business processes can't be completed by your users, e.g. because your database is not available or your payment provider is not reachable.
Your business can be at risk and this requires immediate action.
Crucial functions of your application are not working and business processes can't be completed by your users, e.g. because your database is not available or your payment provider is not reachable.
Your business can be at risk and this requires immediate action.
(7/7) Key takeaways
Maybe it feels obvious, but it's often times not for your junior colleagues.
Help them by giving them some guidance so they know which information has which severity.
Stumbling through thousands of logs that can't be easily filtered for severity is painful.
Maybe it feels obvious, but it's often times not for your junior colleagues.
Help them by giving them some guidance so they know which information has which severity.
Stumbling through thousands of logs that can't be easily filtered for severity is painful.
• • •
Missing some Tweet in this thread? You can try to
force a refresh
