When deploying a web application in production, setting up and configuring monitoring is a critical part of the process. As a DevOps, Web developer, or an IT administrator, you need to be alerted when performance issues or incidents occur, and be able to find the root cause of the problem to quickly get it fixed.
There are numerous methods and levels of web applications monitoring – from simple reachability tests to sophisticated code-level diagnostics of distributed apps. In this article, we’ll cover an approach that is
- Quick and easy to implement,
- Can be applied to almost any web application technology stack,
- Complete and applicable to a vast majority of common problems.
Three levels of web application monitoring
The monitoring framework consists of three levels with multiple types of monitors.
- External website monitoring
- Application level monitoring
- Server (OS) level monitoring
When dealing with web applications (especially complex and distributed), the health of the entire system depends on the performance of many individual application components. Any problem in the IT system must be tracked down in order to identify the root cause. For example, a slow response time (website monitoring level) can be caused by database performance problems, which may be the result of a high CPU load.