CN109787850B

CN109787850B - Monitoring system, monitoring method and computing node

Info

Publication number: CN109787850B
Application number: CN201711107834.2A
Authority: CN
Inventors: 周宇
Original assignee: Alibaba Group Holding Ltd
Current assignee: Alibaba Cloud Computing Ltd
Priority date: 2017-11-10
Filing date: 2017-11-10
Publication date: 2022-12-16
Anticipated expiration: 2037-11-10
Also published as: CN109787850A

Abstract

The embodiment of the application provides a monitoring system, a monitoring method and a computing node, wherein the monitoring system comprises a monitoring front end, at least one service node connected with the monitoring front end and at least one agent node connected with each service node; each agent node is connected with at least one service node; the monitoring front end issues a monitoring rule to any service node; executing monitoring processing operation according to the monitoring data respectively uploaded by any service node; the service node issues the acquisition rule in the monitoring rule to any agent node connected with the service node; processing the service data reported by any agent node according to a calculation rule in the monitoring rule to obtain monitoring data, and uploading the monitoring data to a monitoring front end; and the agent node captures the service data of the corresponding service node based on the acquisition rule and reports the service data to the service node connected with the agent node. The embodiment of the application relieves the monitoring processing pressure and realizes high-efficiency and high-quality monitoring operation.

Description

Monitoring system, monitoring method and computing node

Technical Field

The embodiment of the application relates to the technical field of data processing, in particular to a monitoring system, a monitoring method and a computing node.

Background

With the development of computer technology and electronic technology, many services in various industries can be processed and completed in computer equipment, and service processing needs to be monitored in order to conveniently know service execution conditions such as service quality, service performance, service abnormality and the like.

Generally, the service monitoring process mainly includes monitoring operations such as data collection, data calculation, monitoring processing, and the like, and is executed by a monitoring node. As the service scenes become more and more complex, service partition deployment becomes a major trend, and service nodes in different service clusters or service nodes deployed in different service areas are responsible for executing services in corresponding service areas. If one monitoring node is still responsible for completing the monitoring operation of the service data in each area, as the service is continuously increased, the processing pressure of the monitoring node is increased, and a performance bottleneck occurs to influence the monitoring operation.

Disclosure of Invention

The embodiment of the application provides a monitoring system, a monitoring method and a computing node, which are used for solving the technical problems that monitoring processing pressure is high and monitoring operation is influenced in the prior art.

In a first aspect, an embodiment of the present application provides a monitoring system, including a monitoring front end, at least one service node connected to the monitoring front end, and at least one agent node connected to each service node; each agent node is connected with at least one service node;

the monitoring front end is used for issuing a monitoring rule to any service node; executing monitoring processing operation according to the monitoring data respectively uploaded by the any service node;

the service node is used for receiving the monitoring rule issued by the monitoring front end; sending the collection rules in the monitoring rules to any agent node connected with the collection rules; processing the service data reported by any agent node according to a calculation rule in the monitoring rule to obtain monitoring data; uploading the monitoring data to a monitoring front end;

the agent node is used for receiving an acquisition rule issued by a service node connected with the agent node; and capturing the service data of the corresponding service node based on the acquisition rule, and reporting the service data to a service node connected with the service node.

In a second aspect, an embodiment of the present application provides a monitoring method, which is applied to a monitoring system, where the monitoring system includes a monitoring front end, at least one service node connected to the monitoring front end, and at least one agent node connected to each service node; each agent node is connected with at least one service node;

the method comprises the following steps:

the monitoring front end issues a monitoring rule to any service node;

the monitoring front end executes monitoring processing operation according to the monitoring data uploaded by the any service node; the monitoring data is obtained by processing the service data reported by any agent node connected with the monitoring data by any service node according to a calculation rule in the monitoring rule; and the service data is obtained by capturing from the corresponding service node by the arbitrary agent node based on the acquisition rule in the monitoring rule.

In a third aspect, an embodiment of the present application provides a monitoring method, which is applied to a monitoring system, where the monitoring system includes a monitoring front end, at least one service node connected to the monitoring front end, and at least one agent node connected to each service node; each agent node is connected with at least one service node;

the method comprises the following steps:

the service node receives a monitoring rule issued by the monitoring front end;

the service node issues the acquisition rule in the monitoring rule to any agent node connected with the service node, so that the any agent node can capture the service data of the corresponding service node according to the acquisition rule;

the service node receives the service data reported by any agent node;

the service node processes the service data based on a calculation rule in the monitoring rule to obtain monitoring data;

and the service node reports the monitoring data to the monitoring front end so that the monitoring front end can execute monitoring processing operation by combining the monitoring data reported by different service nodes.

In a fourth aspect, an embodiment of the present application provides a monitoring method, which is applied to a monitoring system, where the monitoring system includes a monitoring front end, at least one service node connected to the monitoring front end, and at least one agent node connected to each service node; each agent node is connected with at least one service node;

the method comprises the following steps:

the agent node receives an acquisition rule issued by a service node connected with the agent node; the acquisition rule is contained in a monitoring rule which is issued by the monitoring front end to the service node;

the agent node captures the service data in the corresponding service node according to the acquisition rule;

the agent node reports the service data to a service node connected with the agent node, so that the service node processes the service data reported by different agent nodes according to a calculation rule in the monitoring rule to obtain monitoring data; and uploading the monitoring data to a monitoring front end, and executing monitoring processing operation by the monitoring front end in combination with the monitoring data reported by different service nodes.

In a fifth aspect, an embodiment of the present application provides a computing node, including one or more processors and one or more memories;

the one or more memories store one or more computer program instructions;

the one or more processors are operable to invoke and execute the one or more computer program instructions to:

issuing a monitoring rule to any service node;

executing monitoring processing operation according to the monitoring data uploaded by any service node; the monitoring data is obtained by processing the service data reported by any agent node connected with the monitoring data by any service node according to a calculation rule in the monitoring rule; and the service data is obtained by capturing from the corresponding service node by the arbitrary agent node based on the acquisition rule in the monitoring rule.

In a sixth aspect, an embodiment of the present application provides a computing node, including one or more processors and one or more memories;

the one or more memories store one or more computer program instructions;

receiving a monitoring rule issued by the monitoring front end;

sending the collection rule in the monitoring rule to any agent node connected with the collection rule so that the any agent node can capture the service data of the corresponding service node according to the collection rule;

receiving the service data reported by any agent node;

processing the service data based on a calculation rule in the monitoring rule to obtain monitoring data;

and reporting the monitoring data to the monitoring front end so that the monitoring front end can execute monitoring processing operation by combining different received monitoring data.

In a seventh aspect, an embodiment of the present application provides a computing node, including one or more processors and one or more memories;

the one or more memories store one or more computer program instructions;

receiving an acquisition rule issued by a service node connected with the service node; the acquisition rule is contained in a monitoring rule which is issued by the monitoring front end to the service node;

capturing service data in corresponding service nodes according to the acquisition rule;

reporting the service data to a service node connected with the service node, so that the service node processes the service data reported by different agent nodes according to a calculation rule in the monitoring rule to obtain monitoring data; and uploading the monitoring data to a monitoring front end, and executing monitoring processing operation by the monitoring front end in combination with the monitoring data reported by different service nodes.

In the embodiment of the application, a monitoring system is responsible for monitoring operation, and the monitoring system comprises a monitoring front end, at least one service node connected with the monitoring front end and at least one agent node connected with each service node; each agent node is connected with at least one service node; the monitoring front end is responsible for monitoring processing operation; the service node is responsible for data calculation operation, and the agent node is responsible for data collection Cao Zu, so that the influence on the processing performance of a certain device caused by monitoring processing pressure is relieved through a hierarchical deployment structure, and efficient and high-quality execution of monitoring operation is guaranteed.

These and other aspects of the present application will be more readily apparent from the following description of the embodiments.

Drawings

In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings used in the embodiments or the prior art descriptions will be briefly described below, and it is obvious that the drawings in the following descriptions are some embodiments of the present application, and other drawings can be obtained by those skilled in the art without creative efforts.

FIG. 1 is a schematic structural diagram illustrating an embodiment of a monitoring system provided herein;

FIG. 2 is a schematic diagram of a monitoring system provided in the present application in a practical application;

FIG. 3 is a schematic diagram illustrating a monitoring system according to another embodiment of the present application;

FIG. 4 is a schematic diagram illustrating a monitoring system provided by the present application in yet another practical application;

FIG. 5 is a flow chart illustrating one embodiment of a monitoring method provided herein;

FIG. 6 is a flow chart illustrating a further embodiment of a monitoring method provided herein;

FIG. 7 is a flow chart illustrating a further embodiment of a monitoring method provided herein;

fig. 8 shows a signaling diagram of yet another embodiment of the monitoring method provided by the present application;

FIG. 9 is a schematic diagram illustrating an embodiment of a monitoring device provided herein;

FIG. 10 is a block diagram illustrating one embodiment of a compute node provided by the present application;

FIG. 11 is a schematic diagram illustrating a monitoring device according to another embodiment of the present application;

FIG. 12 is a schematic structural diagram illustrating yet another embodiment of a compute node provided herein;

FIG. 13 is a schematic diagram illustrating the structure of another embodiment of the monitoring device provided in the present application;

fig. 14 shows a schematic structural diagram of another embodiment of a computing node provided in the present application.

Detailed Description

In order to make the technical solutions better understood by those skilled in the art, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application.

In some of the flows described in the specification and claims of this application and in the above-described figures, a number of operations are included that occur in a particular order, but it should be clearly understood that these operations may be performed out of order or in parallel as they occur herein, the number of operations, e.g., 101, 102, etc., merely being used to distinguish between various operations, and the number itself does not represent any order of performance. Additionally, the flows may include more or fewer operations, and the operations may be performed sequentially or in parallel. It should be noted that, the descriptions of "first", "second", etc. in this document are used for distinguishing different messages, devices, modules, etc., and do not represent a sequential order, nor limit the types of "first" and "second" to be different.

The technical scheme of the application is mainly suitable for various service monitoring scenes, and as various services in various industries are processed and completed in computer equipment, for example, electronic commerce enterprises provide various electronic commerce services such as order service, payment service, logistics service and the like, each service can provide multiple services, for example, the order service can provide services for order processing such as order creation, order submission, order cancellation and the like, and the services are realized based on a computer and a network thereof. The service processing is executed by the service node, and different service data can be generated according to the execution result. Therefore, the service monitoring is mainly to monitor the service execution conditions such as service quality, service performance, service abnormality and the like through analyzing and processing the service data.

As the service scenes are more and more complex, the service processing amount is more and more, and the service partition deployment becomes a big trend, that is, a service node serving a certain service area is responsible for executing the service corresponding to the service area. For example, in an electronic commerce service, each order may come from different regions, and each region is divided into a service area, so that the service node responsible for each region may perform order processing for the corresponding region. A service node serving a certain service area may form a service cluster, so that a certain service cluster is responsible for executing a service in its corresponding area.

The service monitoring process mainly includes monitoring operations such as data collection, data calculation, monitoring processing and the like, and all the monitoring operations are completed by one monitoring node in the prior art, but the single-point monitoring mode is not suitable for the situations that service scenes are relatively complex and service is deployed in different areas, and in the situations, the processing amount is usually large, so that the performance of the monitoring node is seriously influenced, the monitoring efficiency is reduced, and the monitoring operation is influenced.

The inventor researches that if monitoring nodes are sunk into each service area, that is, one monitoring node is correspondingly deployed in each service area, and the monitoring nodes in the service areas are responsible for monitoring operation of service processing in each service node in the service areas, although the method is simple to deploy, each service area needs to be respectively configured with rules and the like, the configuration is complex, and due to the fact that service data corresponding to each service area are comprehensively considered in practical application, an overall monitoring scene of the service execution condition of the overall service, such as the error rate of a certain service provided by the certain service, the average response time and the like, cannot be comprehensively calculated, and the applicability is poor.

In order to not affect the monitoring operation, relieve the processing pressure and ensure the high-efficiency and high-quality execution of the monitoring operation, the inventor provides the technical scheme of the application through further research, and peels off various monitoring operations to perform multi-stage processing deployment. The monitoring system comprises a monitoring front end, at least one service node connected with the monitoring front end and at least one agent node connected with each service node, wherein each agent node is connected with at least one service node; each service node corresponds to a service cluster or a service area. The monitoring system provided by the embodiment of the application can relieve the processing pressure of any node, improve the processing efficiency and ensure the high-efficiency and high-quality execution of the monitoring operation through multi-level deployment.

The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.

Fig. 1 is a schematic structural diagram of an embodiment of a monitoring system provided in the present application.

The monitoring system comprises a monitoring front end 10, at least one service node 20 connected with the monitoring front end 10 and at least one agent node 30 connected with each service node 20; wherein each proxy node 30 is connected to at least one service node 40; for ease of viewing, only two service nodes connected to the monitoring front end are shown in FIG. 1, as well as two agent nodes connected to each service node.

When the service area includes only one service node, the monitoring system also includes one service node. Alternatively, each proxy node 30 may be connected to only one service node 40, and fig. 1 shows that one proxy node 30 is connected to one service node 40 and is responsible for collecting service data of one service node 40 connected thereto.

In a service sub-region deployment scenario, each service node 20 corresponds to a service region, each service region generally corresponds to a plurality of service nodes 40, each service node 40 may be connected to one proxy node 30, and the plurality of proxy nodes 30 are connected to the service node 20 corresponding to the service region, so that the service node 20 corresponding to each service region and the proxy node 30 connected to the service node 20 are responsible for acquiring and calculating service data of each service node 40 in the service region. The service nodes and the agent nodes in each service area form a monitoring cluster.

The monitoring front-end 10 may be constituted by one monitoring node.

When each proxy node 30 is connected to one service node 40, the proxy node 30 may be embedded in the service node 40, that is, the proxy node 30 and the service node 40 may be deployed in the same physical machine, as shown in fig. 1.

Specifically, the method comprises the following steps:

the monitoring front end 10 is configured to issue a monitoring rule to any service node 20; executing a monitoring processing operation according to the monitoring data respectively uploaded by the arbitrary service node 20;

the service node 20 is configured to receive a monitoring rule issued by the monitoring front end 10; sending the collection rule in the monitoring rule to any agent node 30 connected with the collection rule; processing the service data reported by any agent node 30 according to a calculation rule in the monitoring rule to obtain monitoring data; uploading the monitoring data to a monitoring front end;

the agent node 30 is configured to receive an acquisition rule issued by the service node 20 connected thereto; and capturing the service data of the corresponding service node based on the acquisition rule, and reporting the service data to the service node 20 connected with the service node.

The monitoring rule may be provided by a user, and the monitoring front end 10 may immediately issue the monitoring rule to the service node 20 after receiving the monitoring rule.

The monitoring front end 10 may specifically receive a monitoring request; issuing a monitoring rule in the monitoring request to any service node requesting monitoring; and executing monitoring processing operation according to the monitoring data respectively uploaded by the any service node.

The service node 20 may specifically issue the collection rule in the monitoring rule to any agent node 30 connected thereto and requesting monitoring;

the monitoring request is triggered by a user and monitoring rules may be included in the monitoring request.

In addition, as an alternative mode: the monitoring request can comprise service node identifiers and agent node identifiers corresponding to each service node identifier, so that any service node requesting monitoring is each service node corresponding to the service node identifier; and any agent node requesting monitoring is each agent node corresponding to the agent node identifier.

The service node 20 processes the service data reported by any agent node 30 according to the calculation rule in the monitoring rule, and the obtaining of the monitoring data may specifically be to process the service data reported by each agent node 30 connected thereto according to the calculation rule in the monitoring rule, so as to obtain the monitoring data. Service node 20 may perform real-time computations in conjunction with the computation rules and the traffic data reported by the various proxy nodes.

That is, from the layer of the whole service cluster, the collected service data reported by each proxy node in the service area is processed, so as to judge the service availability, the service error rate, the average response time and the like in the service area from the whole point of view. As another alternative: the monitoring request may include an area identifier, so that any service node requesting monitoring is a service node corresponding to the service area represented by the area identifier, and any agent node requesting monitoring may be each agent node corresponding to the service area represented by the area identifier.

Optionally, in some embodiments, after receiving the monitoring rule, the monitoring front end 10 specifically issues the monitoring rule to each service node connected to the monitoring front end, where the arbitrary service node includes all service nodes connected to the monitoring front end 10, so that the monitoring front end 10 may obtain monitoring data uploaded by each service node 20, and perform a monitoring processing operation according to each monitoring data. Therefore, the overall monitoring of the service processing of one service is realized.

Of course, the monitoring front end 10 may also implement monitoring of corresponding service processes in a partial service area based on any service node 20 requesting monitoring determined by the monitoring request.

The corresponding service node may be each service node connected to the proxy node, or may be a service node requesting monitoring determined based on the monitoring request. Therefore, the monitoring request can also include the service node identification so as to determine the service node requesting monitoring.

Alternatively, the monitoring front end 10 may be only responsible for monitoring one kind of traffic, and the traffic node 40, which the monitoring front end 10 establishes association with through the service node 20 and the proxy node 30, may only execute the traffic monitored by the monitoring front end.

The monitoring processing operation executed by the monitoring front end 10 may include, for example, determining whether the monitoring data satisfies an alarm condition, and giving an alarm when the monitoring data satisfies the alarm condition; or display the monitoring data through a large disk, and the like. As in the prior art, it is not described herein in any greater detail.

The monitoring rules comprise acquisition rules and calculation rules, wherein the acquisition rules specify how the data are acquired, and the calculation rules specify how the data are calculated.

Optionally, in order to facilitate the content of the monitoring rule of the proxy node, the service node may further parse the monitoring rule, so as to repackage and obtain the acquisition rule that can be understood and executed by the proxy node and the calculation rule that can be understood and executed by the service node.

The collection rules may include the type of collection and the format of the data return, etc. The data acquisition mode can be determined according to the acquisition type, and the data format of the service data can be constrained according to the data return format.

According to different actual requirements, the current collection types mainly include three types: the system comprises an instruction collection class, a log collection class and a service monitoring service class.

The instruction collection type is to collect the service data according to a collection instruction, and the collection instruction may be included in a collection rule and issued by the monitoring front end 10. The service data collected by the instruction collection is mainly suitable for abnormal monitoring of machine granularity, and can make monitoring response in time for very sensitive errors,

The log collection type refers to collecting operation logs of service nodes, and performing aggregation processing on the operation logs to obtain service data, wherein the service data collected by the log collection type is mainly suitable for monitoring the service quality and performance, such as the damage condition of the service quality of a certain service of a service in unit time.

The service monitoring service class is a specific implementation of an instruction collection class, the service monitoring service class mainly collects service data actively provided by a service node, and the service data collected by the service monitoring service class is mainly suitable for monitoring core services, monitoring whether each service of the core services is available, and the like.

Of course, it is understood that the types of acquisition are not limited to the above three categories.

Wherein, calculating the rule may include: summation (sum), averaging (avg), counting (count), maximum (max), and minimum (min), among others.

Therefore, the service node 20 may perform aggregate calculation on the received different service data according to the calculation rule, so as to obtain the monitoring data.

In a particular implementation, the calculation rule may be null, so that the service node 20 uploads the traffic data to be received directly as monitoring data to the monitoring front-end.

Optionally, in some embodiments, after the service node 20 obtains the monitoring data, the monitoring data may be cached.

The service node 20 may be configured with a monitoring API (Application Programming Interface); the service node 20 specifically receives the monitoring rule issued by the monitoring front end 10 through the monitoring API; sending the collection rules in the monitoring rules to any agent node 30 connected with the collection rules through the monitoring API; processing the service data reported by any agent node 30 according to a calculation rule in the monitoring rule to obtain monitoring data; and uploading the monitoring data to the monitoring front end 10 through the monitoring API. I.e. the calling side of the monitoring API in the service node 20 may be a proxy node or a monitoring front-end.

In practical applications, the proxy node 30 in the embodiment of the present application may be implemented by one or more physical machines, and may also be configured in the same physical machine as the service node 40. Service node 20 may be implemented by one or more physical machines and monitoring front-end 10 may be implemented by one or more physical machines. The physical machine may refer to a computing service device, such as a server, a computer, or the like.

As shown in fig. 2, a schematic structural diagram of a monitoring system provided in the embodiment of the present application in a practical application is shown.

In addition, in some monitoring scenarios, for example, in an overall monitoring scenario, the monitoring front end obtains monitoring data reported by each service node, and before performing a monitoring processing operation, secondary aggregation calculation may be performed on each monitoring data, which may include summing, averaging, counting, finding a maximum value, finding a minimum value, and the like.

For example, in order to monitor the average response time of a service in a certain service, each service node may average the service data (service response time) reported by each agent node connected to the service node to obtain each monitoring data, where each monitoring data is only the average response time corresponding to each service area, and in order to evaluate the average response time of the entire service, the monitoring front end may average each monitoring data again, that is, may calculate the average response time of the entire service.

Therefore, as another embodiment, the monitoring front end may process monitoring data uploaded by any service node connected thereto to obtain aggregated data; and executing monitoring processing operation according to the aggregated data.

Furthermore, to further relieve the processing pressure of the monitoring front-end, as shown in fig. 3, the monitoring front-end 10 may include a monitoring node 11, and a global node 12 connected to the monitoring node 11 and each service node 20, respectively;

the global node 12 is configured to process monitoring data uploaded by any service node 20 connected thereto, and obtain aggregated data; reporting the aggregated data to the monitoring node 11;

the monitoring node 11 is configured to issue a monitoring rule to the arbitrary service node 20 through the global node 12; and executing a monitoring processing operation according to the aggregated data reported by the global node 12.

The global node 12 processes the monitoring data uploaded by any service node 20 connected thereto, and the obtained aggregated data may be obtained by calculation according to an aggregation rule in the monitoring rules. Therefore, the calculation rule may specifically specify how the business data is calculated, and the aggregation rule may specify how the monitoring data is calculated.

The global node is deployed outside the service area, functions realized by the global node and the service node are similar, only service objects are different, and the global node is changed from the service node to the service node from a calling target. In a scenario where only one service area is deployed, the global node is not included.

In practical applications, the proxy node 30 in the embodiment of the present application may be implemented by one or more physical machines, and may also be configured in the same physical machine as the service node 40. The service node 20 may be implemented by one or more physical machines, the monitoring node 10 may be implemented by one or more physical machines, and the global node may be implemented by one or more physical machines.

As shown in fig. 4, a schematic structural diagram of a monitoring system provided in the embodiment of the present application in a practical application is further provided.

Fig. 5 is a flowchart of a monitoring method implemented by a monitoring system according to any one of the embodiments in the present application, where the monitoring method described in this embodiment is applied to a monitoring front end, and is described from the perspective of the monitoring front end. The method may comprise the steps of:

501: and the monitoring front end issues a monitoring rule to any service node.

As an alternative, the arbitrary service node may refer to each service node connected to the monitoring front end; in the overall monitoring scenario, the service data of each service node in each service area needs to be considered comprehensively, so that the monitoring rule in the overall service monitoring scenario is issued to each service node connected with the monitoring front end.

Alternatively, the arbitrary service node may be one or more service nodes connected to the monitoring head end.

In yet another embodiment, the operations of step 501 may include: receiving a monitoring request; and issuing the monitoring rule in the monitoring request to any service node requesting monitoring.

The monitoring request is triggered by a user, and the monitoring rule may be included in the monitoring request, as an alternative: the monitoring request can comprise service node identifiers and agent node identifiers corresponding to each service node identifier, so that any service node requesting monitoring is each service node corresponding to the service node identifier; and any agent node requesting monitoring is each agent node corresponding to the agent node identifier.

As another alternative: the monitoring request may include an area identifier, so that any service node requesting monitoring is a service node corresponding to the service area represented by the area identifier, and any agent node requesting monitoring may be each agent node corresponding to the service area represented by the area identifier.

Therefore, the user can trigger the monitoring front end to send the monitoring rule to one, a plurality of or all the service nodes according to the requirement of the user.

502: and the monitoring front end executes monitoring processing operation according to the monitoring data uploaded by any service node.

And the monitoring data is obtained by processing the service data reported by any agent node connected with the monitoring data by any service node according to a calculation rule in the monitoring rule. The arbitrary proxy node may be determined according to the proxy node identifier in the monitoring request. In the overall monitoring scenario, the arbitrary proxy node includes each proxy node connected to the service node.

And the service data is obtained by capturing from the corresponding service node by the arbitrary agent node based on the acquisition rule in the monitoring rule. And the acquisition rule is issued by the arbitrary service node to the arbitrary proxy node connected with the arbitrary service node.

In some embodiments, when the monitoring front end comprises a monitoring node and a global node, the monitoring node issues a monitoring rule to any service node through the global node;

processing the monitoring data uploaded by any service node by a global node to obtain aggregated data, and uploading the aggregated data to the monitoring node;

and executing monitoring processing operation by the monitoring node according to the aggregated data.

Fig. 6 is a flowchart of a monitoring method implemented by a monitoring system according to any one of the embodiments in the present application, where the monitoring method described in this embodiment is applied to a service node, and is described from the perspective of the service node. The method may comprise the steps of:

601: and the service node receives the monitoring rule issued by the monitoring front end.

602: and the service node issues the acquisition rule in the monitoring rule to any agent node connected with the service node, so that the any agent node can capture the service data of the corresponding service node according to the acquisition rule.

The monitoring node may issue the collection rule in the monitoring rule to any agent node connected with the monitoring node and requesting monitoring.

An optional manner of any proxy node requesting monitoring may be determined based on the proxy node identifier in the monitoring request, and another optional manner may be determined based on the area identifier in the monitoring request.

Of course, in a particular implementation, such as an overall monitoring scenario, the arbitrary proxy node refers to each proxy node connected to the service node.

603: and the service node receives the service data reported by the arbitrary proxy node.

604: the service node processes the service data based on a calculation rule in the monitoring rule to obtain monitoring data;

605: and the service nodes report the monitoring data to the monitoring front end so that the monitoring front end can execute monitoring processing operation by combining the monitoring data reported by different service nodes.

Fig. 7 is a flowchart of a monitoring method implemented by a monitoring system according to any one of the embodiments in a further embodiment of the present application, where the monitoring method described in this embodiment is applied to a proxy node, and is described from the perspective of the proxy node. The method may comprise the steps of:

701: and the agent node receives the acquisition rule issued by the service node connected with the agent node.

The acquisition rule is included in a monitoring rule issued by the monitoring front end to the service node.

702: and the proxy node captures the service data in the corresponding service node according to the acquisition rule.

Wherein, the corresponding service node may refer to each service node connected to the proxy node; or the service node requesting monitoring can be determined based on the monitoring request received by the monitoring front end.

703: the agent node reports the service data to a service node connected with the agent node, so that the service node processes the service data reported by different agent nodes according to a calculation rule in the monitoring rule to obtain monitoring data; and uploading the monitoring data to a monitoring front end.

In order to better understand the technical solution of the present application, as shown in fig. 8, a signaling diagram of a monitoring method implemented by a monitoring system provided based on any one of the above embodiments in a further embodiment of the present application is shown.

With reference to fig. 8, the monitoring front end 10 receives a monitoring request in step 801, wherein the monitoring request may be triggered by a user, including a monitoring rule. Then, the monitoring front end 10 executes step 802 to issue the monitoring rule to any service node 20 requesting monitoring (only two service nodes 20 are exemplarily shown in fig. 8), where the determination of any service node 20 requesting monitoring may be as described above, and is not described herein again.

Optionally, the monitoring front end 10 may include a monitoring node 11 and a global node 12, and the monitoring node 11 may receive a monitoring request and issue a monitoring rule to any service node 20 that requests monitoring through the global node 12.

Any service node 20 receiving the monitoring rule executes step 803, and issues the acquisition rule in the monitoring rule to any agent node 30 connected with the service node and requesting monitoring; any proxy node requesting monitoring can refer to the above description, and is not described herein again.

Any agent node 30 receiving the collection rule executes step 804, and captures the service data of the service node connected with the agent node based on the collection rule; and step 805 is executed, the service data is uploaded to the service node 20 connected to the service node;

any service node 20 that receives the service data executes step 806, processes the service data reported by any proxy node according to the calculation rule in the monitoring rule, obtains monitoring data, and uploads the monitoring data to the monitoring front end 10.

The monitoring front end 10 executes step 807, and executes a monitoring processing operation according to the monitoring data uploaded by each service node 20 requesting monitoring.

Optionally, when the monitoring front end 10 includes the monitoring node 11 and the global node 12, any service node 20 that receives the service data specifically uploads the monitoring data to the global node 12, and the global node 12 processes the monitoring data uploaded by each service node 20 that requests monitoring, to obtain aggregated data; and uploading the aggregated data to the monitoring node 11, and executing, by the monitoring node 11, a monitoring processing operation according to the aggregated data.

As can be seen from the above description, in the technical scheme provided in this embodiment of the present application, the monitoring system is deployed in a hierarchical manner, and the monitoring operation is stripped, that is, the data collection, the data calculation, and the monitoring processing are stripped, so as to form a multi-level deployment structure, it is not necessary to deploy a monitoring node in each service area or service cluster, thereby avoiding the complexity of repeated deployment, relieving the processing pressure in a single monitoring scene, satisfying all monitoring scenes, and achieving both the service monitoring of a part of service areas and the overall monitoring of a certain service, with higher applicability.

As can be seen from the above description, the technical solution provided in the embodiment of the present application may be applied to an overall monitoring scenario, for example, in an electronic commerce service, taking order creation service as an example, the order creation service needs to be monitored integrally, for example, average order creation response time of the order creation service needs to be monitored, where the order creation response time refers to response time for creating a corresponding order in response to an order creation request when the order creation request is received, and therefore, service data obtained from each service node is also referred to as order creation response time. In a service zoning deployment environment, it is necessary to obtain a response time length for creating each order generated by a service node in each service zone, so that a monitoring rule can be defined accordingly, an acquisition rule in the monitoring rule can specify that data is acquired according to a log collection type mode, a calculation rule specifies that an average value of each service data is calculated, and the monitoring rule can further include an aggregation rule for specifying a global node to perform secondary calculation so as to average the monitoring data uploaded by each service node to obtain aggregated data as each service zone needs to be comprehensively considered. Then, the monitoring node obtains the monitoring rule and can issue the monitoring rule to each service node connected with the monitoring node; each service node issues the collection rule of the monitoring rule to each agent node connected with the service node; each agent node is used for acquiring the service data in the service node connected with the agent node according to the acquisition node, namely the order creating response time and reporting the order creating response time to the service node at the upper stage; each service node creates response time according to the order uploaded by each agent node, and averages according to a calculation rule, so that monitoring data of each service area can be obtained, namely the area average creating response time; each service node uploads the area average creating response time length obtained by respective calculation to a global node; the global node averages the average creation response time of each area, that is, the average creation response time of the order for creating the order service can be obtained, so that the monitoring node can perform monitoring processing operation based on the average creation response time of the order, for example, if the average creation response time of the order is greater than a preset time, an alarm can be given.

Fig. 9 is a schematic structural diagram of an embodiment of a monitoring apparatus provided in the present application, which may be configured in the monitoring front end 10, and includes:

a first rule issuing module 901, configured to issue a monitoring rule to any service node;

a monitoring processing module 902, configured to execute a monitoring processing operation according to the monitoring data uploaded by the arbitrary service node; the monitoring data is obtained by processing the service data reported by any agent node connected with the monitoring data by any service node according to a calculation rule in the monitoring rule; and the service data is obtained by capturing from the corresponding service node by the arbitrary agent node based on the acquisition rule in the monitoring rule.

In one possible design, the monitoring apparatus shown in fig. 9 may be implemented as a computing node, which may include one or more processors 1001 and one or more memories 1002, as shown in fig. 10;

the one or more memories 1002 store one or more pieces of computer program instructions;

the one or more processors 1001 call and execute the one or more computer program instructions to perform the following operations:

issuing a monitoring rule to any service node;

The computing node shown in fig. 10 may be implemented as the monitoring front end in any one of embodiments shown in fig. 1 to 4.

When the computing node includes multiple memories 1002 and multiple processors 1001, the multiple memories 1002 may be deployed in one or more physical machines and the multiple processors 1001 may be deployed in one or more physical machines.

Optionally, the computing node may further comprise components necessary to implement its functionality, such as a display, a transmitter, a communication module, I/O interfaces and/or power components.

The memory 1002 may be implemented, for example, by any type of volatile or non-volatile memory device or combination thereof, such as Static Random Access Memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic or optical disk.

Accordingly, an embodiment of the present application further provides a computer-readable storage medium, which stores a computer program, and when the computer program is executed by a computer, the monitoring method of the embodiment shown in fig. 5 may be implemented.

Furthermore, as can be seen from the above description, the monitoring front end 10 may be composed of a monitoring node 11 and a global node 12, so as to provide, as yet another embodiment, a monitoring apparatus, which may be configured in the monitoring node 11, and includes:

the rule processing unit is used for issuing the monitoring rule to any service node through the global node;

and the monitoring processing unit is used for executing monitoring processing operation according to the aggregation data reported by the global node.

The aggregated data is obtained by processing the monitoring data uploaded by any service node connected with the global node by the global node.

In one possible design, the apparatus may be implemented as a compute node comprised of one or more processors and one or more memories;

the one or more memories store one or more computer program instructions;

the one or more processors invoke and execute the one or more computer program instructions to perform operations comprising:

issuing a monitoring rule to any service node through a global node;

and executing monitoring processing operation according to the aggregated data reported by the global node.

In addition, as another embodiment, the present application further provides a monitoring apparatus, which may be configured in the global node 12, and includes:

the rule receiving unit is used for receiving the monitoring rule issued by the monitoring node and sending the monitoring rule to any service node;

the data calculation unit is used for processing the monitoring data uploaded by any service node connected with the data calculation unit to obtain aggregated data;

and the data reporting unit is used for reporting the aggregated data to the monitoring node so that the monitoring node executes monitoring processing operation according to the aggregated data.

In one possible design, the apparatus may be implemented as a computing node comprised of one or more processors and one or more memories;

the one or more memories store one or more computer program instructions;

receiving a monitoring rule issued by a monitoring node, and sending the monitoring rule to any service node;

processing monitoring data uploaded by any service node connected with the monitoring data to obtain aggregated data;

and reporting the aggregated data to the monitoring node so that the monitoring node executes monitoring processing operation according to the aggregated data.

Fig. 11 is a schematic structural diagram of another embodiment of a monitoring apparatus provided in the present application, where the apparatus may be configured in a service node 20, and includes:

a first rule receiving module 1101, configured to receive a monitoring rule issued by the monitoring front end;

a second rule issuing module 1102, configured to issue an acquisition rule in the monitoring rule to any agent node connected to the monitoring rule, so that the any agent node captures service data of a corresponding service node according to the acquisition rule;

a data collection module 1103, configured to receive the service data reported by the arbitrary proxy node;

a calculating module 1104, configured to process the service data based on a calculating rule in the monitoring rules to obtain monitoring data;

a data reporting module 1105, configured to report the monitoring data to the monitoring front end, so that the monitoring front end performs a monitoring processing operation in combination with the monitoring data reported by different service nodes.

In one possible design, the monitoring apparatus shown in fig. 11 may be implemented as a computing node, which may include one or more processors 1201 and one or more memories 1202, as shown in fig. 12;

the one or more memories 1202 store one or more pieces of computer program instructions;

the one or more processors 1201 invoke and execute the one or more computer program instructions to perform the following operations:

receiving a monitoring rule issued by the monitoring front end;

receiving the service data reported by any proxy node;

The computing node shown in fig. 12 may be implemented as the service node in any embodiment of fig. 1 to 4.

When the computing node includes multiple memories 1202 and multiple processors 1201, the multiple memories 1202 may be deployed in one or more physical machines and the multiple processors 1201 may be deployed in the one or more physical machines.

Optionally, the computing node may further comprise components necessary to achieve its functionality, such as receivers, transmitters, communication modules, I/O interfaces and/or power components.

Wherein the one or more processors 1201 may enable the reception of service data and the upload of monitoring data by calling a monitoring API.

The memory 1202 may be implemented, for example, by any type or combination of volatile and non-volatile memory devices such as Static Random Access Memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic or optical disks.

Accordingly, an embodiment of the present application further provides a computer-readable storage medium, which stores a computer program, and when the computer program is executed by a computer, the monitoring method of the embodiment shown in fig. 6 may be implemented.

Fig. 13 is a schematic structural diagram of another embodiment of a monitoring apparatus provided in the present application, where the apparatus may be configured in a proxy node 20, and includes:

a second rule receiving module 1301, configured to receive an acquisition rule issued by a service node connected to the second rule receiving module; the acquisition rule is contained in a monitoring rule which is issued by the monitoring front end to the service node;

a data acquisition module 1302, configured to capture service data in a corresponding service node according to the acquisition rule;

a data uploading module 1303, configured to upload the service data to a service node connected to the service node, so that the service node processes each reported service data according to a calculation rule in the monitoring rule to obtain monitoring data; uploading the monitoring data to a monitoring front end; the monitoring front end is used for executing monitoring processing operation by combining the monitoring data reported by different service nodes.

In one possible design, the monitoring apparatus shown in fig. 14 may be implemented as a computing node, which may include one or more processors 1401 and one or more memories 1402;

the one or more processors 1401 invokes and executes the one or more computer program instructions to perform the following operations:

The computing node shown in fig. 14 may be implemented as a proxy node in any one of embodiments shown in fig. 1 to 4.

Where the compute node includes multiple memories 1402 and multiple processors 1401, the multiple memories 1402 may be deployed in one or more physical machines, and the multiple processors 1401 may be deployed in the one or more physical machines.

Optionally, the computing node may further comprise receivers, transmitters, communication modules, I/O interface and/or power supply components, etc. necessary for its functionality.

The memory 1502 may be implemented by any type or combination of volatile or non-volatile memory devices, such as Static Random Access Memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic or optical disks.

Accordingly, an embodiment of the present application further provides a computer-readable storage medium, which stores a computer program, and when the computer program is executed by a computer, the monitoring method of the embodiment shown in fig. 7 may be implemented.

It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.

The above-described embodiments of the apparatus are merely illustrative, and the units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the present embodiment. One of ordinary skill in the art can understand and implement it without inventive effort.

Through the above description of the embodiments, those skilled in the art will clearly understand that each embodiment can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware. With this understanding in mind, the above-described technical solutions may be embodied in the form of a software product, which can be stored in a computer-readable storage medium such as ROM/RAM, magnetic disk, optical disk, etc., and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to execute the methods described in the embodiments or some parts of the embodiments.

Finally, it should be noted that: the above embodiments are only used to illustrate the technical solutions of the present application, and not to limit the same; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; and such modifications or substitutions do not depart from the spirit and scope of the corresponding technical solutions in the embodiments of the present application.

Claims

1. A monitoring system is characterized by comprising a monitoring front end, at least one service node connected with the monitoring front end and at least one agent node connected with each service node; each agent node is connected with at least one service node, and each service node corresponds to one service cluster or one service area;

the monitoring front end is used for issuing a monitoring rule to any service node; executing monitoring processing operation according to the monitoring data respectively uploaded by the arbitrary service nodes; the monitoring rules comprise acquisition rules and calculation rules, the acquisition rules are used for stipulating data acquisition, and the calculation rules are used for stipulating data calculation;

the service node is used for receiving the monitoring rule issued by the monitoring front end; sending the collection rule in the monitoring rule to any agent node connected with the collection rule; processing the service data reported by any proxy node according to a calculation rule in the monitoring rule to obtain monitoring data; uploading the monitoring data to a monitoring front end;

the service node is also used for analyzing the monitoring rule and repackaging the monitoring rule to obtain the acquisition rule corresponding to the agent node and the calculation rule corresponding to the service node;

the agent node is used for receiving an acquisition rule issued by a service node connected with the agent node; and capturing the service data of the corresponding service node based on the acquisition rule, and reporting the service data to the service node connected with the service node.

2. The system of claim 1, wherein the monitoring front end comprises a monitoring node and a global node connected to the monitoring node and each service node, respectively;

the global node is used for processing the monitoring data uploaded by any service node connected with the global node to obtain aggregated data; reporting the aggregated data to the monitoring node;

the monitoring node is used for issuing a monitoring rule to the any service node through the global node; and executing monitoring processing operation according to the aggregated data reported by the global node.

3. The system of claim 1, wherein each proxy node is connected to a service node;

and the agent node captures the service data of the service node connected with the agent node specifically based on the acquisition rule.

4. The system according to claim 1, wherein the monitoring front-end is specifically configured to receive a monitoring request; issuing a monitoring rule to any service node requesting monitoring; executing monitoring processing operation according to the monitoring data respectively uploaded by the arbitrary service nodes;

the step of the service node issuing the collection rule in the monitoring rule to any agent node connected with the service node is specifically to issue the collection rule in the monitoring rule to any agent node connected with the service node and requesting monitoring.

5. The system of claim 1, wherein the service node is configured with a monitoring API;

the service node receives a monitoring rule issued by the monitoring front end through the monitoring API; sending the collection rules in the monitoring rules to any agent node connected with the collection rules through the monitoring API; processing the service data reported by any agent node according to a calculation rule in the monitoring rule to obtain monitoring data; and uploading the monitoring data to a monitoring front end through the monitoring API.

6. The monitoring method is characterized by being applied to a monitoring system, wherein the monitoring system comprises a monitoring front end, at least one service node connected with the monitoring front end and at least one agent node connected with each service node; each agent node is connected with at least one service node, and each service node corresponds to one service cluster or one service area;

the method comprises the following steps:

the monitoring front end issues a monitoring rule to any service node; the monitoring rules comprise acquisition rules and calculation rules, the acquisition rules are used for stipulating data acquisition, and the calculation rules are used for stipulating data calculation;

the monitoring front end executes monitoring processing operation according to the monitoring data uploaded by the any service node; the monitoring data is obtained by processing the service data reported by any agent node connected with the monitoring data by any service node according to a calculation rule in the monitoring rule; the service data is obtained by capturing from the corresponding service node by the arbitrary agent node based on the acquisition rule in the monitoring rule;

the collection rule and the calculation rule are obtained by analyzing and repackaging the monitoring rule by the service node, the collection rule corresponds to the agent node, and the calculation rule corresponds to the service node.

7. The monitoring method is characterized by being applied to a monitoring system, wherein the monitoring system comprises a monitoring front end, at least one service node connected with the monitoring front end and at least one agent node connected with each service node; each agent node is connected with at least one service node, and each service node corresponds to one service cluster or one service area;

the method comprises the following steps:

the service node receives a monitoring rule issued by the monitoring front end; the monitoring rules comprise acquisition rules and calculation rules, the acquisition rules are used for stipulating data acquisition, and the calculation rules are used for stipulating data calculation;

the service node issues an acquisition rule in the monitoring rule to any agent node connected with the service node, so that the any agent node can capture the service data of the corresponding service node according to the acquisition rule;

the service node receives the service data reported by any agent node;

the service node reports the monitoring data to the monitoring front end so that the monitoring front end can execute monitoring processing operation by combining the monitoring data reported by different service nodes;

and the service node analyzes the monitoring rule and encapsulates again to obtain the acquisition rule corresponding to the proxy node and the calculation rule corresponding to the service node.

8. The monitoring method is characterized by being applied to a monitoring system, wherein the monitoring system comprises a monitoring front end, at least one service node connected with the monitoring front end and at least one agent node connected with each service node; each agent node is connected with at least one service node, and each service node corresponds to one service cluster or one service area;

the method comprises the following steps:

the agent node reports the service data to a service node connected with the agent node, so that the service node processes the service data reported by different agent nodes according to a calculation rule in the monitoring rule to obtain monitoring data; uploading the monitoring data to a monitoring front end, and executing monitoring processing operation by the monitoring front end in combination with the monitoring data reported by different service nodes;

the monitoring rules comprise acquisition rules, and the acquisition rules are used for regulating data acquisition;

the acquisition rule is acquired as follows: and analyzing the monitoring rule by the service node, and repackaging to obtain the acquisition rule corresponding to the proxy node.

9. A computing node comprising one or more processors and one or more memories;

the one or more memories store one or more computer program instructions;

the one or more processors are operable to invoke and execute the one or more computer program instructions to perform operations comprising:

issuing a monitoring rule to any service node, wherein each service node corresponds to a service cluster or a service area; the monitoring rules comprise acquisition rules and calculation rules, the acquisition rules are used for stipulating data acquisition, and the calculation rules are used for stipulating data calculation;

executing monitoring processing operation according to the monitoring data uploaded by any service node; the monitoring data is obtained by processing the service data reported by any agent node connected with the monitoring data by any service node according to a calculation rule in the monitoring rule; the service data is obtained by capturing from the corresponding service node by the arbitrary agent node based on the acquisition rule in the monitoring rule;

10. A computing node comprising one or more processors and one or more memories;

the one or more memories store one or more computer program instructions;

receiving a monitoring rule issued by a monitoring front end; the monitoring rules comprise acquisition rules and calculation rules, the acquisition rules are used for stipulating data acquisition, and the calculation rules are used for stipulating data calculation;

receiving the service data reported by any agent node;

reporting the monitoring data to the monitoring front end so that the monitoring front end can execute monitoring processing operation by combining different received monitoring data;

and the service node analyzes the monitoring rule and repackages the monitoring rule to obtain the acquisition rule corresponding to the agent node and the calculation rule corresponding to the service node.

11. A computing node comprising one or more processors and one or more memories;

the one or more memories store one or more computer program instructions;

receiving an acquisition rule issued by a service node connected with the service node; the acquisition rule is contained in a monitoring rule which is issued to the service node by a monitoring front end; the monitoring rules comprise acquisition rules, and the acquisition rules are used for regulating data acquisition;

reporting the service data to a service node connected with the service node, so that the service node processes the service data reported by different agent nodes according to a calculation rule in the monitoring rule to obtain monitoring data; uploading the monitoring data to a monitoring front end, and executing monitoring processing operation by the monitoring front end in combination with the monitoring data reported by different service nodes, wherein each service node corresponds to a service cluster or a service area;