Characteristics of good logging
Logging is implemented but the information in the logs is not useful for building insights or debugging production issues. How many times have you seen this issue?
That's where best practices come into the picture, to implement good logging in your application. Some of the characteristics of good logging are as follows:
- It should not affect the actual application performance.
- It should be accurate and complete.
- It should be leveraged for data analytics and learning about application usages, such as concurrent users, peak load time, and most/least used features.
- It should help us reproduce the issue reported for root cause analysis and minimize unable to reproduce instances.
- It should be distributed and easily accessible by everyone – development, product owner, and support.
- It should not contain protected or sensitive information, personally identifiable information (PII), or duplicate or unnecessary logs. ...
