It can monitor response times, status codes, and even look for specific content on the page. Retrace can run these types of HTTP “ping” checks every minute for you. If you have a web application, the easiest way to monitor application availability is via a simple scheduled HTTP check. Most companies use this as a way to measure uptime for service level agreements (SLA). Monitoring and measuring if your application is online and available is a key metric you should be tracking. It is important to track them per server but also as an aggregate across all the individually deployed instances of your application. Virtually all server and application monitoring tools can track your CPU usage and provide monitoring alerts. Monitoring the CPU usage of your server and applications is a basic and critical metric. If the CPU usage on your server is extremely high, you can guarantee you will have application performance problems. This is another interesting metric to track to see how it correlates. If you have a busy API that suddenly gets no traffic at all, that could be a really bad thing to watch out for.Ī similar but slightly different metric to track is the number of concurrent users. Monitoring the request rate can also be good to watch for spikes or even inactivity. Request rates can be useful to correlate to other application performance metrics to understand the dynamics of how your application scales. Potentially all other application performance metrics are affected by increases or decreases in traffic. Understanding how much traffic your application receives will impact the success of your application. (Not to mention your hosting bill going way up!) 5. You would instead see the number of server instances get high. This also creates some unique monitoring challenges.įor example, if your application automatically scales up based on CPU usage, you may never see your CPU get high.
Auto-scaling can help ensure your application scales to meet demand and saves you money during off-peak times. If your application scales up and down in the cloud, it is important to know how many server/application instances you have running. Hidden application exceptions can cause a lot of performance problems. It is common to see thousands of exceptions being thrown and ignored within an application. Thrown Exceptions – Number of all exceptions that have been thrown.Logged Exceptions – Number of unhandled and logged errors from your application.HTTP Error % – Number of web requests that ended in an error.There are potentially 3 different ways to track application errors: Monitoring error rates is a critical application performance metric. The last thing you want your users to see are errors. That said, averages are still a useful application performance metric. I highly recommend using the aforementioned user satisfaction Apdex scores as a preferred way to track overall performance. Let me start by saying that averages suck.
0 kommentar(er)
