![]() Their first responsibility is to accept and store incoming and historical data. Monitoring systems fulfill many related functions. Monitoring takes metrics data, aggregates it, and presents it in various ways that allow humans to extract insights from the collection of individual pieces. Data is composed of raw, unprocessed facts, while information is produced by analyzing and organizing data to build context that provides value. In general, the difference between metrics and monitoring mirrors the difference between data and information. The data from various parts of your environment are collected into a monitoring system that is responsible for storage, aggregation, visualization, and initiating automated responses when the values meet specific requirements. While metrics represent the data in your system, monitoring is the process of collecting, aggregating, and analyzing those values to improve awareness of your components’ characteristics and behavior. ![]() Metrics are the basic values used to understand historic trends, correlate diverse factors, and measure changes in your performance, consumption, or error rates. They represent the raw material used by your monitoring system to build a holistic view of your environment, automate responses to changes, and alert human beings when required. Metrics are useful because they provide insight into the behavior and health of your systems, especially when analyzed in aggregate. Collecting and exposing metrics is sometimes known as adding instrumentation to your services. Many web servers, database servers, and other software also provide their own metrics which can be passed forward as well.įor other components, especially your own applications, you may have to add code or interfaces to expose the metrics you care about. are already available, provide value immediately, and can be forwarded to a monitoring system without much additional work. Data about disk space, CPU load, swap usage, etc. ![]() Often, the easiest metrics to begin with are those already exposed by your operating system to represent the usage of underlying physical resources. Some metrics are presented in relation to a total capacity, while others are represented as a rate that indicates the “busyness” of a component. These might be low-level usage summaries provided by the operating system, or they can be higher-level types of data tied to the specific functionality or work of a component, like requests served per second or membership in a pool of web servers. Metrics represent the raw measurements of resource usage or behavior that can be observed and collected throughout your systems. What Are Metrics and Why Do We Collect Them? In this section, we’ll take a look at these individual concepts and how they fit together. If the metrics fall outside of your expected ranges, these systems can send notifications to prompt an operator to take a look, and can then assist in surfacing information to help identify the possible causes. They have the ability to provide visibility into the health of your systems, help you understand trends in usage or behavior, and to understand the impact of changes you make. Metrics, monitoring, and alerting are all interrelated concepts that together form the basis of a monitoring system. What Are Metrics, Monitoring and Alerting? We will be introducing some key terminology along the way and will end with a short glossary of some other terms you might come across while exploring this space. We will talk about why they are important, what types of opportunities they provide, and the type of data you may wish to track. In this guide, we will discuss what metrics, monitoring, and alerting are. One of the best ways to gain this insight is with a robust monitoring system that gathers metrics, visualizes data, and alerts operators when things appear to be broken. Information about the health and performance of your deployments not only helps your team react to issues, it also gives them the security to make changes with confidence. Understanding the state of your infrastructure and systems is essential for ensuring the reliability and stability of your services.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |