My monitoring world view (5)-How to reflect business scenarios in monitoring

My monitoring world view (5)-How to reflect business scenarios in monitoring

In my monitoring World View 1 ~ 4 describes the monitoring, storage, and display of a monitoring site. However, in the real world, the whole world is more like a graph. Each point can be a monitoring point, while the side is a call relationship or data stream between them.

Example:
Webserver-> mysql

For the simplest web service, it may consist of two parts: webserver and mysql Store Shop and product information. The webserver service interacts directly with browser users. In such a business scenario, some monitoring points on webserver may include UV and PV per unit time, while the Monitoring Points on mysql may have connections and requests per second.

In this way, we will closely integrate the monitoring points with our own business logic. In addition, we can think that the business of each company is completely different. So if we separate monitoring into layers, we find that monitoring also has layers.

3. Business-level monitoring
2. Data collection, storage, and aggregation at monitoring sites
1. monitoring site data collection

1) The traffic plan cannot be adopted for data collection at the monitoring site.
Besides basic monitoring, such as CPU usage, load, and disk usage
However, PV-like business indicators are hard to be unified.

2) data collection, storage, and aggregation at monitoring sites can be solved using a traffic solution.
Recently I have seen an article proposing to use ES for post-aggregation, so you do not need to perform first aggregation.

3) Business-level monitoring should reflect the call relationships between applications and services in the business flow, especially the data flow direction and traffic size. Data flow is the core element of each module.