Monitoring

Out in the real world, in a production environment, is where your application gets really tested to its limits. Despite all the effort in developing test scenarios, and going through different stages of quality assurance, there will come a time when there are edge case scenarios that the development team or the quality assurance team might have not considered and, therefore, these missed edge case scenarios might cause bugs to occur. There are times when hardware-related issues will be encountered, or sometimes there will be some code-related performance bottlenecks causing timeouts and unhappy clients. It happens, but it’s not the end of the world. It would be great if the development team had access to a production environment’s usage statistics, the CPU or memory usage of the containers, the most accessed controllers, the stack trace of an exception, and so on.

Having this information will help you and your team resolve issues more quickly when they happen...