![]() ![]() It also showed us that we had two specific exceptions that were happening a lot. We could instantly see a big spike in exceptions around 12:45. Following the alert, we checked our error monitoring dashboard, and this is what we saw below. We received an alert from Retrace about page load times being too high and high error rates. You should immediately check your error logs for potential problems.įor example, a couple of days ago our system was working fine but was running really slow. If your web application is not working correctly, your error logs are your first line of defense. These types of HTTP checks can be very useful for a wide array of things! Elasticsearch Monitoring with Retrace How to Monitor Application Errors We can look for specific text like “number_of_nodes”:11 to know if the correct number of Elasticsearch nodes is up and running. In the previous example, we are looking for “Sign In” on our log in page.Īs another example, we also use it to monitor our Elasticsearch cluster. This is useful to ensure that the page is not only loading with a 200 HTTP status code but returning a proper response. ![]() Most monitoring tools even allow you to check for specifying text as part of the response. Website Availability Monitoring with Retrace We can monitor the response time and ensure that they are responding with an HTTP status code of 200. The best way to do application availability monitoring is with a simple HTTP ping monitor that runs every minute.įor example, we use this at Stackify to monitor our various web applications and marketing websites. The easiest part of web performance monitoring is ensuring your web application is online and available for your users.
0 Comments
Leave a Reply. |