Best practices for devops observability
My first blog post in 2005 was about application logging, and I shared 10 practices I hoped my development team would follow. Today’s devops implementations around observability are more sophisticated and scalable, but several of my recommendations remain relevant, especially logging session IDs, specifying code-location details, and ensuring logs are free from security and privacy-related data.
Building observability best practices into the software development life cycle is critically important today because more apps deliver mission-critical customer and employee experiences. Devops teams should not be just concerned about faster mean time to resolve major incidents; they should ensure that apps and services are observable to continuously improve an experience’s robustness, reliability, and ease of use.
Author: . [Source Link (*), InfoWorld]