We had to load things about what they had purchased, contact history, notes, etc. It had one specific page that did a ton of SQL queries to load a lot of details about a customer. Example #1: Customer page in a CRM applicationĪ long time ago I worked on a CRM application. Let me provide some more details with a couple of good examples. Critical web requests like a shopping cart page.Problematic web requests that tend to slow down.Here are some of the common things to consider monitoring: What you need to monitor for an e-commerce site is very different than a REST API. Depending on your type of web application, it could be a wide variety of things.
#Online server monitoring how to#
How to Monitor Important Web Requests or Key TransactionsĮvery application has important web requests or “ key transactions” that should be closely monitored. You should send all of your application errors to an error monitoring and reporting service. Azure was having some weird issue with their Redis hosting for a few minutes.Įrror monitoring is a critical component of web application performance monitoring. On that day, the issue ended up going away on its own.
Since our applications rely heavily on Redis for caching, any issue with it definitely causes some problems. Our exception logs pointed us directly to Redis as being a problem in this instance. It was the smoke from the production fire that we needed. Thanks to having these errors, we knew exactly where to dig deeper. 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.
#Online server monitoring code#
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.
Google found that reducing the speed of Google searches by just 400 milliseconds would cause 8,000,000 fewer searches to be run every day. Next time, I might remember that bad experience and not even go back to that other pizza restaurant. If I go to order pizza online and their website is being really slow or throwing errors, I will just order pizza from somewhere else. It is important to monitor your application in multiple different ways to ensure your entire application stack is working correctly.Īs some say, “ Performance is a feature”. As you know, it is possible for your web application to be online and loading quickly, but returning an error every time. Web performance monitoring is a mixture of web application monitoring techniques to ensure that your application is online, loading quickly, and working correctly. Although, I guess it might also help you avoid meetings about production problems. It won’t help you get out of meetings, but it will help prevent production fires and put them out faster. All developers need to understand the basics of web performance monitoring. Especially meetings or fighting production problems. As developers, we would rather be writing code all day than doing anything else.
0 kommentar(er)
