![]() Later in this post, you’ll learn how to use New Relic to measure golden signals by percentile. The 95th percentile is a good starting point, but the exact number will vary depending on your application’s needs. That’s why you should be looking not just at the average but also at pages in a specific percentile for latency. If 95 percent of the requests have minimal latency but 5 percent of the requests are painfully slow for users, just looking at the average will mask potential problems with an application-especially if the slow pages are important, high-traffic pages like landing pages or pages for user signups. The average request may be completed very quickly, but it’s more important to focus on a web application’s slowest requests. Measuring the average latency of requests can give you a bird’s eye view of a web application’s performance, but it can also be misleading if you don’t drill down further. The longer it takes for a user to load a page or make another request, the more likely that user is to abandon an application for a competitor. Latency is the time between when a request is made and when it is completed. While there are many other performance metrics worth monitoring, the golden signals cover the essentials. Regardless of whether you have an established APM tool or are just getting started with monitoring, monitoring the golden signals allows you to quickly see an overview of the health of your application. Golden signals are the gold standard when it comes to monitoring a web application’s metrics.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |