CN112835766A

CN112835766A - Application monitoring method and device

Info

Publication number: CN112835766A
Application number: CN202110183429.9A
Authority: CN
Inventors: 许子恒
Original assignee: Hangzhou Chengying Data Technology Co ltd
Current assignee: Hangzhou Chengying Data Technology Co ltd
Priority date: 2021-02-10
Filing date: 2021-02-10
Publication date: 2021-05-25

Abstract

The present specification provides an application monitoring system, method and apparatus, wherein the application monitoring system includes a monitoring container group, at least one service application container group and a monitoring server; the monitoring container group is used for receiving a monitoring request sent by the monitoring server and sending the monitoring request to a target service application container group to be monitored, wherein the target service application container group is one of the at least one service application container group; the target business application container group is used for acquiring monitoring data based on the monitoring request and feeding the monitoring data back to the monitoring container group; the monitoring server is used for acquiring the monitoring data from the monitoring container group. According to the scheme, one monitoring container group is independently deployed to monitor the applications in the service application container groups, so that a monitoring service module does not need to be added in each service application container group, the load of the service application container groups is reduced, and the deployment difficulty and the maintenance cost of the container groups are reduced.

Description

Application monitoring method and device

Technical Field

The present disclosure relates to the field of computer application monitoring technologies, and in particular, to an application monitoring system, method and apparatus, a computing device, and a computer-readable storage medium.

Background

The health monitoring of the application of the terminal through Prometheus service in the monitoring server is an effective way to ensure the normal operation of the application. The prometies service generally cannot directly collect monitoring data in applications, and therefore promemeus officials proposed that metrics service modules can be configured in each business application container group. Referring to fig. 1A, each service application container group includes a metrics service module for monitoring applications, in addition to its own service processing module. And a sdecar auxiliary container can be added to the metrics service module, and monitoring data of the application is collected from the service execution module in the service application container group through the sdecar auxiliary container, so that the monitoring server can obtain the monitoring data from the metrics service module in the service application container group.

Therefore, in the method, the metrics service module is deployed in the service application container group, and the auxiliary container is additionally added for monitoring data acquisition, so that the service application container group is increased from only one module to two modules, the load of the service application container group is increased, and the deployment difficulty and the maintenance cost of the service application container group are increased.

Disclosure of Invention

In view of this, the embodiments of the present specification provide an application monitoring system. The present specification also relates to an application monitoring method, an application monitoring apparatus, a computing device, and a computer-readable storage medium, which are used to solve the technical defects in the prior art.

According to a first aspect of embodiments herein, there is provided an application monitoring system, the application monitoring system comprising a monitoring server, a monitoring container group and at least one service application container group;

the monitoring container group is used for receiving a monitoring request sent by the monitoring server and sending the monitoring request to a target service application container group to be monitored, wherein the target service application container group is one of the at least one service application container group;

the target business application container group is used for acquiring monitoring data based on the monitoring request and feeding the monitoring data back to the monitoring container group;

the monitoring server is used for acquiring the monitoring data from the monitoring container group.

Optionally, the monitoring container group includes a monitoring service module and a data acquisition module;

the monitoring service module is used for receiving the monitoring request and sending the monitoring request to the data acquisition module, wherein the monitoring request comprises a container group identifier;

the data acquisition module is used for determining the target service application container group based on the container group identification and sending the monitoring request to the target service application container group.

Alternatively,

the target service application container group is specifically used for sending the monitoring data to the data acquisition module;

correspondingly, the data acquisition module is used for receiving the monitoring data;

the monitoring service module is used for acquiring the monitoring data from the data acquisition module and performing data format conversion on the monitoring data to obtain target monitoring data.

Alternatively,

the monitoring server is specifically configured to obtain the target monitoring data from the monitoring service module.

Optionally, a database is further deployed in the monitoring container group:

the data acquisition module is also used for storing the monitoring data into the database;

correspondingly, the monitoring service module is specifically configured to obtain the monitoring data from the database.

Optionally, the application monitoring system further comprises an asset configuration management database;

and the monitoring container group is also used for receiving an application identifier sent by the asset configuration management database, carrying the application identifier in the monitoring request and sending the monitoring request to the target service application container group.

Alternatively,

the target service application container group is specifically used for acquiring the monitoring data of the application indicated by the application identifier based on the application identifier.

According to a second aspect of embodiments of the present specification, there is provided an application monitoring method applied to monitoring a group of containers, the method including:

receiving a monitoring request, and sending the monitoring request to a target service application container group to be monitored;

and receiving monitoring data and sending the monitoring data to a monitoring server.

Optionally, the monitoring request includes a container group identifier, and sending the monitoring request to a target service application container group to be monitored includes:

and determining the target business application container group based on the container group identification, and sending the monitoring request to the target business application container group.

Optionally, a database is further deployed in the monitoring container group, and after receiving the monitoring data, the method further includes:

performing data format conversion on the monitoring data to obtain target monitoring data;

and storing the target monitoring data into the database.

Optionally, before sending the monitoring request to the target service application container group to be monitored, the method further includes:

receiving an application identifier;

correspondingly, the sending the monitoring request to the target service application container group to be monitored includes:

and carrying the application identifier in the monitoring request and sending the monitoring request to the target service application container group.

Optionally, sending the monitoring data to a monitoring server includes:

and acquiring the target monitoring data from the database and sending the target monitoring data to the monitoring server.

According to a third aspect of embodiments herein, there is provided an application monitoring apparatus applied to a monitoring container group, including:

the system comprises a first sending module, a second sending module and a monitoring module, wherein the first sending module is used for receiving a monitoring request and sending the monitoring request to a target service application container group to be monitored;

and the second sending module is used for receiving the monitoring data and sending the monitoring data to the monitoring server.

According to a fourth aspect of embodiments herein, there is provided a computing device comprising:

a memory and a processor;

the memory is to store computer-executable instructions, and the processor is to execute the computer-executable instructions to:

According to a fifth aspect of embodiments herein, there is provided a computer-readable storage medium storing computer-executable instructions that, when executed by a processor, implement the steps of the application monitoring method.

The application monitoring system provided by the specification comprises a monitoring server, a monitoring container group and at least one service application container group; the monitoring container group is used for receiving a monitoring request sent by the monitoring server and sending the monitoring request to a target service application container group to be monitored, wherein the target service application container group is one of the at least one service application container group; the target business application container group is used for acquiring monitoring data based on the monitoring request and feeding the monitoring data back to the monitoring container group; the monitoring server is used for acquiring the monitoring data from the monitoring container group. According to the scheme, one monitoring container group is independently deployed to monitor the applications in the service application container groups, so that a monitoring service module does not need to be added in each service application container group, each service application container group only comprises a service processing module of the service processing module, the load of the service application container group is reduced, and the deployment difficulty and the maintenance cost of the container group are also reduced.

Drawings

FIG. 1A is a schematic diagram of an application monitoring system in the prior art;

FIG. 1B is a schematic diagram of another monitoring system of the prior art;

fig. 2 is a schematic structural diagram of an application monitoring system according to an embodiment of the present disclosure;

fig. 3 is a schematic structural diagram of another application monitoring system provided in an embodiment of the present specification;

FIG. 4 is a flow chart of a method for monitoring an application provided in an embodiment of the present disclosure;

FIG. 5 is a flow chart of another application monitoring method provided in an embodiment of the present disclosure;

FIG. 6 is a flow chart of another application monitoring method provided in an embodiment of the present specification;

fig. 7 is a schematic structural diagram of an application monitoring apparatus according to an embodiment of the present disclosure;

fig. 8 is a block diagram of a computing device according to an embodiment of the present disclosure.

Detailed Description

In the following description, numerous specific details are set forth in order to provide a thorough understanding of the present description. This description may be embodied in many different forms and should not be construed as limited to the embodiments set forth herein, as those skilled in the art will be able to make and use the present disclosure without departing from the spirit and scope of the present disclosure.

The terminology used in the description of the one or more embodiments is for the purpose of describing the particular embodiments only and is not intended to be limiting of the description of the one or more embodiments. As used in one or more embodiments of the present specification and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used in one or more embodiments of the present specification refers to and encompasses any and all possible combinations of one or more of the associated listed items.

It will be understood that, although the terms first, second, etc. may be used herein in one or more embodiments to describe various information, these information should not be limited by these terms. These terms are only used to distinguish one type of information from another. For example, a first can also be referred to as a second and, similarly, a second can also be referred to as a first without departing from the scope of one or more embodiments of the present description. The word "if" as used herein may be interpreted as "at … …" or "when … …" or "in response to a determination", depending on the context.

First, the noun terms to which one or more embodiments of the present specification relate are explained.

Promiphos/Prometoeus: google open source system monitoring software.

Promiers index service/Metric service: and the monitoring acquisition unit feeds back monitoring data in a Prometheus data format.

SpringActuator: health check plug-in under the java spring framework.

K8S/Kubernetes: a container arrangement platform for google open source.

SaaS: SoftwareAsA Service software as a Service.

Container/Container: and the source opening software packages and isolates the application environment.

A container group: the row unit in the K8S Container platform consists of 1 or more containers (containers).

CMDB/asset configuration management database: and the database manages various assets and configurations such as IT and applications in the enterprise.

Zabbix: an enterprise-level distributed open source monitoring scheme.

Next, an application scenario of the application monitoring method provided in the embodiments of the present specification is briefly described.

In implementation, in order to perform a health check on the application to ensure that the application is operating normally, an application monitoring system may be deployed on the container platform for monitoring the application. Referring to fig. 1B, data output in the upper part of the graph in fig. 1B is monitoring data in a specific format required by the promiscuous monitoring service, data in the lower part of the graph in fig. 1B is monitoring data that can be fed back by the business application container group for application monitoring, and a format of the monitoring data required by the monitoring server is different from a format of the monitoring data of the application that can be fed back by the business application container group, and the monitoring server cannot directly acquire the monitoring data of the application for use, so that the application monitoring needs to be performed by an intermediate proxy service and the monitoring data needs to be acquired.

It should be noted that the log, the disk usage, the database connection, and the cache connection in fig. 1B may be regarded as monitoring data that needs to be monitored by the application monitoring.

In the prior art, a Zabbix monitoring scheme can be adopted to monitor the application, wherein the Zabbix monitoring scheme is to deploy Zabbix servers (services) or Zabbix Proxy into a container network in a container mode and then perform secondary development of a data collection script. However, the Zabbix scheme is a monitoring system with a Host (Host) as a core, all monitoring data are required to be attached to the Host finally, the concept of the Host does not exist in application monitoring in k8s but does not exist in the Host, and therefore how to store and analyze the monitoring data becomes a difficult problem; the IP (internet protocol address) dynamic change of the container in the container network needs to utilize the discovery function of Zabbix to perform the secondary development of the script, and the interaction is relatively complicated and the flexibility is not good; the problem that the monitoring data in the Zabbix and the monitoring data in the CMDB are staggered or not aligned is solved, the Zabbix needs to be packaged so as to dynamically obtain the monitoring data, and the difficulty of container deployment is improved.

Therefore, the application monitoring method provided by the present application can solve the above problems, and specific implementations thereof can be seen in the following embodiments.

In the present specification, an application monitoring system is provided, and the present specification relates to an application monitoring method, an application monitoring apparatus, a computing device, and a computer-readable storage medium, which are described in detail one by one in the following embodiments.

Fig. 2 is a schematic structural diagram illustrating an application monitoring system according to an embodiment of the present disclosure. The application monitoring system may include a monitoring container group 202, at least one business application container group 204, and a monitoring server 206;

the monitoring container group 202 is configured to receive a monitoring request sent by the monitoring server, and send the monitoring request to a target service application container group to be monitored, where the target service application container group is one of the at least one service application container group;

the target service application container group 204 is configured to obtain monitoring data based on the monitoring request and feed the monitoring data back to the monitoring container group;

the monitoring server 206 is configured to obtain the monitoring data from the monitoring container group.

In this illustrative embodiment, the application monitoring system may be deployed on the K8S platform. In addition, the application monitoring method provided by the application can be used for monitoring Java/Spring applications in the container and can also be used for monitoring applications based on a Linux/Windows operating system.

As an example, the monitoring container group may be considered as a container group serving as an intermediate proxy, and is used for collecting monitoring data from the business application container group and feeding the monitoring data back to the monitoring server. The business application container group may include one or more containers, each container for storing monitoring data for an application.

Illustratively, as can be seen from fig. 2, the monitoring server 206 establishes a communication connection with the monitoring container group 202, and the service application container group 204 establishes a communication connection with the monitoring container group 202.

In some embodiments, a user may select a service application container group to be monitored through a visualization device, and then the server may generate a monitoring request based on the selection to send to the monitoring container group, where the monitoring request may include a container group identifier of the service application container group to be monitored, and then the monitoring container group may receive the monitoring request, determine a target service application container group based on the container group identifier, and send the monitoring request to the target service application container group to obtain monitoring data. The container group identifier may be used to uniquely identify a service application container group, and the container group identifier may be a letter, a number, a character, and the like, which is not limited in this specification.

Illustratively, the monitoring data may be used to represent the operational status of the application. For example, the monitoring data may include a spring web site dead-live state, a database Redis connection state, a Java virtual machine CPU running state, a memory size, a disk usage rate, and the like.

In some embodiments, the target business application container group may be configured to receive the monitoring request, obtain monitoring data based on the monitoring request, and send the monitoring data to the monitoring container group.

As an example, the target service application container group may include a SpringActuactor plugin, which is used to monitor the application and obtain monitoring data.

In some embodiments, the monitoring server may be configured to periodically obtain monitoring data from the set of monitoring containers. Specifically, the monitoring server may send a data obtaining request to the monitoring container group, and the monitoring container group may feed back the monitoring data to the monitoring server based on the data obtaining request.

As an example, the monitoring server may send a data obtaining request to the monitoring container group, where the data obtaining request may include a container group identifier and an application identifier, and the monitoring container group may obtain monitoring data corresponding to both the container group identifier and the application identifier based on the container group identifier and the application identifier, and send the monitoring data to the monitoring server, and the monitoring server may obtain the monitoring data.

As an example, the monitoring server may have promemeus monitoring software installed therein, and monitoring data may be obtained from the monitoring container group through the monitoring software.

In an optional embodiment of the present application, the monitoring container group 202 includes a monitoring service module and a data collection module; the monitoring service module is used for receiving the monitoring request and sending the monitoring request to the data acquisition module, wherein the monitoring request comprises a container group identifier; the data acquisition module is used for determining the target service application container group based on the container group identification and sending the monitoring request to the target service application container group.

That is, the process of receiving the monitoring request and sending the monitoring request to the target service application container group by the monitoring service module and the data acquisition module in the monitoring container group is realized. And the monitoring service module is used for receiving a monitoring request sent by the monitoring server and sending the monitoring request to the data acquisition module, and the data acquisition module is used for receiving the monitoring request, determining a target service application container group based on a container identifier in the monitoring request and sending the monitoring request to the target service application container group.

As an example, the monitoring service module and the data collection module are both packaged in the monitoring container group, and both the monitoring service module and the data collection module are disposed in the monitoring container of the monitoring container group.

As an example, the set of monitoring containers may be referred to as SPHC Pod, the monitoring containers may be referred to as SPHC Container, the collection containers may be referred to as Collection Container, and the monitoring service modules may be referred to as metrics, or Promiers index service/Metric service data. The acquisition module may be referred to as a pycur Function. And, the data acquisition module can be packaged with a data acquisition function for acquiring monitoring data.

For example, referring to fig. 2, a monitoring service module and a data acquisition module may be included in the monitoring container group, the monitoring service module and the data acquisition module are both disposed in the monitoring container, and a communication connection is established between the monitoring service module and the data acquisition module, so that data transmission may be performed.

In the embodiment of the description, a monitoring container group comprising a monitoring service module and a data acquisition module is separately deployed for application monitoring, and modules do not need to be added in a service application container group, that is, the application monitoring method provided by the application can monitor the health conditions of applications and call chains in a non-invasive manner, so that the problems of service application container transformation and container invasion are solved, the service application container is more portable and brief, the light deployment of the service application container is realized, and the application monitoring is realized without an auxiliary container.

In an optional embodiment of the present application, the application monitoring system further includes an asset configuration management database; the monitoring container group 202 is further configured to receive an application identifier sent by the asset configuration management database, carry the application identifier in the monitoring request, and send the monitoring request to the target service application container group.

The asset configuration management database, which may be referred to as a CMDB, may be managed by an administrator to determine the applications that need to be monitored.

That is to say, the application monitoring system further includes an asset configuration management database, and the asset configuration management database may send an application identifier to the monitoring container group, and after receiving the application identifier, the monitoring container group may carry the identifier in a monitoring request and send the monitoring request to the target service application container group.

As an example, each business application container group may include monitoring data of a plurality of applications, and the plurality of applications are implemented by different programming languages, and the monitoring server may only monitor applications implemented by a certain programming language, that is, monitoring data of some applications cannot be collected or does not need to be collected, so that it is not enough to determine only a target business application container group, and applications to be monitored need to be determined. For example, configuration parameters related to application monitoring in the asset configuration management database may be set by an administrator through a visualization device, where the configuration parameters may include an application identifier, and the monitoring container group may receive the application identifier through a data acquisition module, and send the application identifier carried in a monitoring request to a target service application container group, so that the target service application container group determines which application data needs to be acquired. Therefore, the situation that unnecessary monitoring data are collected and container resources are wasted can be avoided.

In the embodiment of the specification, the application monitoring is linked with the CMDB, so that the monitoring object and the monitoring range can be dynamically adjusted, namely, the application to be monitored is adjusted, and the flexibility is stronger. In addition, the application monitoring is linked with the CMDB, and the monitoring container group can determine the application to be monitored according to the application identifier sent by the CMDB, so that the monitoring instantaneity can be improved, and the time cost for manually maintaining the monitoring configuration is reduced.

For example, referring to fig. 3, the application monitoring system shown in fig. 3 further includes an asset configuration management database, which may be managed by an administrator, and the asset configuration management database may establish a communication connection with the data acquisition module for data transmission.

In an optional embodiment of the present application, the target service application container group 204 is specifically configured to obtain, based on the application identifier, monitoring data of an application indicated by the application identifier.

For example, assuming that the application identifier is JAVA, which indicates that the monitoring server needs to monitor the application implemented in the JAVA programming language, the target service application container group may obtain the monitoring data of the application implemented in the JAVA programming language.

In an optional embodiment of the present application, the target service application container group 204 is specifically configured to send the monitoring data to the data acquisition module; correspondingly, the data acquisition module is used for receiving the monitoring data; the monitoring service module is used for acquiring the monitoring data from the data acquisition module and performing data format conversion on the monitoring data to obtain target monitoring data.

As an example, in the monitoring container group, the data acquisition module is configured to acquire monitoring data in the service application container group, and the monitoring service module is configured to perform data format conversion on the acquired monitoring data to obtain data meeting the format requirement of the monitoring server. Therefore, after the target service application container group acquires the monitoring data, the monitoring data can be sent to the data acquisition module of the monitoring container group, and the data acquisition module realizes the function of monitoring data acquisition. In addition, because the monitoring data received by the data acquisition module is in a format different from that of the monitoring data required by the monitoring server, in order to obtain the monitoring data meeting the format requirement, the monitoring service module can obtain the monitoring data from the data acquisition module and perform data format conversion on the monitoring data, so that the target monitoring data meeting the format requirement can be obtained.

For example, referring to fig. 2, the target service application container group 204 may perform data transmission with the data collection module of the monitoring container group 202, that is, the data collection module may receive monitoring data from the target service application container group.

Furthermore, the target service application container group acquires the monitoring data through a single thread, one monitoring request can be executed only after the execution of the other monitoring request, and all the required monitoring data can be completely acquired after waiting for a long time under the condition that the monitoring requests are more, so that not only is time wasted, but also the data acquisition efficiency is reduced. Therefore, in the embodiment of the present specification, data acquisition may be performed in a multi-thread concurrent manner, that is, multiple sub-threads may be created, and different monitoring requests may be executed at the same time, so that the time for data acquisition may be shortened, and the efficiency of data acquisition may be improved.

Referring to fig. 3, in fig. 3, when monitoring data acquisition is performed by a single thread, in the case of a large number of monitoring requests, a waiting time t1 may be required to complete the monitoring data acquisition process, in fig. 3B, the data acquisition process is performed by a multi-thread concurrent manner, and the monitoring data acquisition process may be completed by t2, where t2 is less than t1, which may be considered that the efficiency of monitoring data acquisition is improved by the multi-thread concurrent manner.

In an optional embodiment of the present application, a database is also deployed in the monitoring container group 202; the data acquisition module is also used for storing the monitoring data into the database; the monitoring service module is specifically configured to obtain the monitoring data from the database.

In some embodiments, the period of data collection and the period of monitoring data acquisition by the monitoring server may be different, and the data collection module collects a plurality of monitoring data in a short time, but the monitoring server may not need as much monitoring data at one time, so that after the monitoring data is collected, the monitoring data may be stored and may be acquired from the monitoring container group when the monitoring server needs the monitoring data.

Therefore, in the embodiment of the present specification, the monitoring container group may further be deployed with a database, and the data acquisition module may store the acquired monitoring data in the database, so that the monitoring service module may acquire the monitoring data from the database, perform data format conversion on the monitoring data, and obtain target monitoring data to store the target monitoring data in the database again. Therefore, the problem that the data acquisition period of the monitoring container group is unequal to the data acquisition period of the monitoring server, so that the monitoring data cannot be stored after being acquired can be solved.

For example, referring to fig. 3, in the application monitoring system shown in fig. 3, a database is further deployed in the monitoring container group, the data acquisition module may store the monitoring data in the database, and the monitoring service module may obtain the monitoring data from the database and perform data format conversion.

In this embodiment of the present specification, the emptyDir of the K8S platform may be used as a database for storing monitoring data, the monitoring data may also be read and written normally in the case of separate reading and writing of the monitoring data, and the collected monitoring data may be stored in the case of asynchronous collection of the monitoring data and feedback of the monitoring data to the monitoring server, so as to implement data sharing between data collection and data feedback.

In an optional embodiment of the present application, the monitoring server 206 is specifically configured to obtain the target monitoring data from the monitoring service module.

In some embodiments, the monitoring server and the monitoring service module of the monitoring container group may perform data transmission, and the monitoring server may obtain the monitoring data through the monitoring service module.

As an example, the monitoring server may send a data obtaining request to the monitoring service module, where the data obtaining request may include a container group identifier and an application identifier, and the monitoring container group may obtain, based on the container group identifier and the application identifier, monitoring data corresponding to both the container group identifier and the application identifier from a database, and send the monitoring data to the monitoring server.

In other embodiments, the monitoring server obtains the target monitoring data from the monitoring service module.

As an example, the monitoring server may send a data obtaining request to the monitoring service module, where the data obtaining request may include a container group identifier and an application identifier, and in a case that the monitoring service module performs data format conversion on the monitoring data, the monitoring container group may obtain, based on the container group identifier and the application identifier, target monitoring data corresponding to both the container group identifier and the application identifier from a database, and send the target monitoring data to the monitoring server.

It should be noted that, the application monitoring system provided in this specification does not need to modify the service application container group, reduces container configuration of the service application container group, avoids cost caused by container modification, and reduces load consumption of the container platform. In addition, a monitoring container group comprising a monitoring service module and a data acquisition module is independently deployed for application monitoring of all applications, a monitoring server is not required to send a monitoring request to each service application container, and resource use of the monitoring server is reduced.

The application monitoring system provided by the specification comprises a monitoring server, a monitoring container group and at least one service application container group; the monitoring container group is used for receiving a monitoring request sent by the monitoring server and sending the monitoring request to a target service application container group to be monitored, wherein the target service application container group is one of the at least one service application container group; the target business application container group is used for acquiring monitoring data based on the monitoring request and feeding the monitoring data back to the monitoring container group; the monitoring server is used for acquiring the monitoring data from the monitoring container group. The scheme has the advantages that the function of monitoring data acquisition is independent from the service application container group and is configured in the monitoring container group, namely, one monitoring container group is independently deployed to monitor the application in the service application container group, so that a monitoring service module does not need to be added in each service application container group, each service application container group only comprises a service processing module of the service processing module, the load of the service application container group is reduced, the invasive damage to the service application container group caused by the monitoring service module additionally added in the service application container group can be avoided, and the deployment difficulty and the maintenance cost of the container group are also reduced.

Fig. 4 is a flowchart illustrating an application monitoring method according to an embodiment of the present disclosure, where the application monitoring method is applied to an application monitoring system, where the application monitoring system includes a monitoring container group, at least one service application container, and a monitoring server, and specifically includes the following steps:

step 402, the monitoring container group receives a monitoring request sent by the monitoring server, and sends the monitoring request to a target service application container group to be monitored, wherein the target service application container group is one of the at least one service application container group.

As an example, a user may select a service application container group to be monitored through a visualization device, and then the server may generate a monitoring request based on the selection to send to the monitoring container group, where the monitoring request may include a container group identifier of the service application container group to be monitored, and then the monitoring container group may receive the monitoring request, determine a target service application container group based on the container group identifier, and send the monitoring request to the target service application container group to obtain monitoring data.

In some embodiments, the monitoring container group may include a monitoring service module and a data collection module. In this case, the specific implementation that the monitoring container group receives the monitoring request and sends the monitoring request to the target service application container group may include: the monitoring service module receives the monitoring request and sends the monitoring request to the data acquisition module, wherein the monitoring request comprises a container group identifier; and the data acquisition module determines the target service application container group based on the container group identifier and sends the monitoring request to the target service application container group.

That is, the process of receiving the monitoring request and sending the monitoring request to the target service application container group by the monitoring service module and the data acquisition module in the monitoring container group is realized. And the monitoring service module is used for receiving the monitoring request sent by the monitoring server and sending the monitoring request to the data acquisition module, and after receiving the monitoring request, the data acquisition module can determine a target service application container group based on the container identifier in the monitoring request and send the monitoring request to the target service application container group.

Further, the application monitoring system further comprises an asset configuration management database, and the monitoring container group may further receive an application identifier sent by the asset configuration management database; accordingly, the monitoring container group may carry the application identifier in the monitoring request and send the monitoring request to the target service application container group.

And step 404, the target service application container group obtains monitoring data based on the monitoring request and feeds the monitoring data back to the monitoring container group.

The monitoring data may be used to indicate the running state of the application. For example, the monitoring data may include a spring web site dead-live state, a database Redis connection state, a Java virtual machine CPU running state, a memory size, a disk usage rate, and the like.

In some embodiments, the specific implementation of the target service application container group for acquiring the monitoring data based on the monitoring request may include: and the target service application container group acquires the monitoring data of the application indicated by the application identifier based on the application identifier.

In some embodiments, the feeding back the monitoring data to the specific implementation of the monitoring container group by the target service application container group may include: and the target service application container group sends the monitoring data to the data acquisition module, and the data acquisition module receives the monitoring data.

That is to say, after the target service application container group acquires the monitoring data, the monitoring data can be sent to the data acquisition module of the monitoring container group, and the data acquisition module realizes the function of monitoring data acquisition.

Further, the method further comprises: and the monitoring service module acquires the monitoring data from the data acquisition module and performs data format conversion on the monitoring data to obtain target monitoring data.

As an example, in the monitoring container group, the data acquisition module is configured to acquire monitoring data in the service application container group, and the monitoring service module is configured to perform data format conversion on the acquired monitoring data to obtain data meeting the format requirement of the monitoring server.

In some embodiments, the monitoring data received by the data acquisition module is in a format different from that of the monitoring data required by the monitoring server, and in order to obtain the monitoring data meeting the format requirement, the monitoring service module may obtain the monitoring data from the data acquisition module, and perform data format conversion on the monitoring data, so as to obtain the target monitoring data meeting the format requirement.

Further, a database is also deployed in the monitoring container group, and the method further includes: the data acquisition module stores the monitoring data into the database; correspondingly, the monitoring service module acquires the monitoring data from the database.

In some embodiments, the period of data collection and the period of monitoring data acquisition by the monitoring server may be different, and the data collection module collects a plurality of monitoring data in a short time, but the monitoring server may not need the monitoring data at one time, so that the monitoring data can be stored after the monitoring data is collected, and the monitoring data can be acquired from the monitoring container group when the monitoring server needs the monitoring data.

Therefore, in the embodiment of the present specification, the monitoring container group may further be deployed with a database, and the data acquisition module may store the acquired monitoring data in the database, so that the monitoring service module may acquire the monitoring data from the database, perform data format conversion on the monitoring data, and obtain target monitoring data to store the target monitoring data in the database again. Therefore, the problem that the data acquisition period of the monitoring container group is unequal to the data acquisition period of the monitoring server can be solved.

Step 406, the monitoring server obtains the monitoring data from the monitoring container group.

In an implementation, the monitoring server may periodically obtain monitoring data from the monitoring container set. Specifically, the monitoring server may send a data acquisition request to the monitoring container group, and the monitoring container group may feed back monitoring data to the monitoring server based on the data acquisition request.

As an example, the monitoring server may send a data obtaining request to the monitoring container group, where the data obtaining request may include a container group identifier and an application identifier, and the monitoring container group may obtain monitoring data corresponding to both the container group identifier and the application identifier based on the container group identifier and the application identifier, and send the monitoring data to the monitoring server.

In other embodiments, the monitoring server obtains the target monitoring data from the monitoring service module. As an example, the monitoring server may send a data obtaining request to the monitoring service module, where the data obtaining request may include a container group identifier and an application identifier, and in a case that the monitoring service module performs data format conversion on the monitoring data, the monitoring container group may obtain, based on the container group identifier and the application identifier, target monitoring data corresponding to both the container group identifier and the application identifier from a database, and send the target monitoring data to the monitoring server.

In addition, the application monitoring system in this specification is unrelated to the host, so that the application monitoring method can realize the library dropping and analysis of the monitoring data without the host, and the application monitoring system can include the CMDB, so that the problem that the monitoring data is not targeted can be avoided, and the container does not need to be deployed again.

It should be noted that the embodiment of the application monitoring method corresponds to the embodiment of the application monitoring system, and specific implementation of the embodiment of the application monitoring method may refer to related description of the embodiment of the application monitoring system, which is not described herein again.

Fig. 5 is a flowchart of another application monitoring method according to an exemplary embodiment, which is applied to an application monitoring system that includes a monitoring server, a monitoring container group, and at least one service application container group, and next, another application monitoring method according to an embodiment of the present disclosure is described with reference to fig. 3 and fig. 5, where the method specifically includes the following steps:

step 502: and the monitoring server sends a monitoring request to the monitoring service module.

Step 504: the monitoring service module receives the monitoring request and sends the monitoring request to the data acquisition module.

Step 506: and the data acquisition module receives the monitoring request and determines a target service application container group based on the monitoring request.

Wherein, the monitoring request can be identified by a container group.

For example, the data acquisition module may determine, according to a container group identifier carried in the monitoring request, a service application container group corresponding to the container group identifier, determine the service application container group as a target service application container group, and send the monitoring request to the service application container group.

Step 508: and the data acquisition module receives the application identification sent by the asset configuration management database.

Since only the tag that can determine the target service application container group is carried in the monitoring request, but one service application container may include multiple applications, and the multiple applications are implemented in different programming languages, while the monitoring server may only monitor the applications implemented in a certain programming language, it is necessary to determine the application identifier to be monitored in the target service application container group.

Step 510: and the data acquisition module carries the application identifier in the monitoring request and sends the monitoring request to the target service application container group.

For example, configuration parameters related to application monitoring in the asset configuration management database may be set by an administrator through a visualization device, where the configuration parameters may include an application identifier, and the monitoring container group may receive the application identifier through a data acquisition module, and send the application identifier carried in a monitoring request to a target service application container group, so that the target service application container group determines which application data needs to be acquired. Therefore, the situation that unnecessary monitoring data are collected and container resources are wasted can be avoided.

Step 512: and the target service application container group receives the monitoring request and acquires the monitoring data of the application indicated by the application identifier based on the application identifier.

Step 514: and the target service application container group sends the monitoring data to the data acquisition module.

Step 516: the data acquisition module receives the monitoring data and stores the monitoring data into a database.

Step 518: the monitoring service module acquires the monitoring data from the database to perform data format conversion, and the target monitoring data is obtained and stored in the database.

In implementation, since the data format of the monitoring data is different from the data format required by the monitoring server, the format of the monitoring data needs to be converted into a data format that can be processed by the monitoring server.

In step 520, the monitoring service module receives a data acquisition request from the monitoring server.

In step 522, the monitoring service module obtains the target monitoring data from the database and sends the target monitoring data to a monitoring server (Prometheus).

For example, referring to fig. 3, the monitoring server may send a data obtaining request to the monitoring service module, and if the database is the target monitoring data after data format conversion, the monitoring service module may obtain the target monitoring data from the database and send the target monitoring data to the monitoring server, and the monitoring server may obtain the target monitoring data of the application to be monitored.

Fig. 6 is a flowchart illustrating another application monitoring method according to an exemplary embodiment, where the method is applied to monitoring a container group, and the method specifically includes the following steps:

step 602, receiving a monitoring request, and sending the monitoring request to a target service application container group to be monitored.

As an example, to perform a health check on an application to ensure that the application is operating properly, an application monitoring system may be deployed on the container platform for monitoring the application. The format of the monitoring data required by the monitoring server is different from the format of the monitoring data of the application that can be fed back by the service application container group, and the monitoring server cannot directly acquire the monitoring data of the application for use, so that the application monitoring needs to be performed through an intermediate proxy service, and the monitoring data needs to be acquired. That is, in the embodiment of this specification, the function of monitoring data acquisition is separated from the service application container group and configured in the monitoring container group, which not only reduces the load of the service application container group, but also avoids the invasive damage to the service application container group caused by additionally adding a monitoring service module to the service application container group.

In some embodiments, a user may select a service application container group to be monitored through the visualization device, and the server may generate a monitoring request based on the selection to send to the monitoring container group, and the monitoring container group may receive the monitoring request.

In some embodiments, the monitoring request may include a container group identifier, and sending the monitoring request to a specific implementation of a target service application container group to be monitored may include: and determining the target business application container group based on the container group identification, and sending the monitoring request to the target business application container group.

That is, after receiving the monitoring request, the monitoring container group may determine the target service application container group based on the container group identifier, and send the monitoring request to the target service application container group.

As an example, the monitoring container group may be packaged with a monitoring service module and a data collection module. The process that the monitoring container group receives the monitoring request and sends the monitoring request to the target service application container group is realized through a monitoring service module and a data acquisition module in the monitoring container group. Specifically, the monitoring server module may receive a monitoring request sent by the monitoring server, send the monitoring request to the data acquisition module, and after receiving the monitoring request, the data acquisition module may determine a target service application container group based on a container identifier in the monitoring request and send the monitoring request to the target service application container group.

Further, before sending the monitoring request to the target service application container group to be monitored, the method further includes: an application identification is received. Correspondingly, the sending the monitoring request to the target service application container group to be monitored includes: and carrying the application identifier in the monitoring request and sending the monitoring request to the target service application container group.

In some embodiments, each business application container group may include monitoring data of a plurality of applications, and the plurality of applications are implemented by different programming languages, and the monitoring server may only monitor applications implemented by a certain programming language, that is, monitoring data of some applications cannot be collected or does not need to be collected, so that it is not enough to determine only a target business application container group, and applications to be monitored need to be determined. The application identifier may be sent by the asset configuration management database, and after receiving the application identifier, the monitoring container group may send the identifier to the target service application container group by carrying the identifier in the monitoring request, so that the target service application container group determines which application data needs to be collected. Therefore, the situation that unnecessary monitoring data are collected and container resources are wasted can be avoided.

As an example, the monitoring container group may receive the application identifier through the data acquisition module, and send the application identifier carried in the monitoring request to the target service application container group.

Step 604, receiving the monitoring data and sending the monitoring data to the monitoring server.

In some embodiments, after receiving the monitoring request, the target service application container group may obtain the monitoring data based on the application identifier and send the monitoring data to the monitoring container group, and then the monitoring container group may receive the monitoring data.

Further, a database is also deployed in the monitoring container group, and after receiving the monitoring data, the method further includes: performing data format conversion on the monitoring data to obtain target monitoring data; and storing the target monitoring data into the database.

In some embodiments, the monitoring data received by the data acquisition module is in a format different from that of the monitoring data required by the monitoring server, and in order to obtain the monitoring data meeting the format requirement, the monitoring container group may perform data format conversion on the monitoring data, so as to obtain the target monitoring data meeting the format requirement. And the period of data acquisition and the period of monitoring data acquisition of the monitoring server may be different, and the data acquisition module acquires a plurality of monitoring data in a short time, but the monitoring server may not need the monitoring data once, so that the monitoring data can be stored in the database after being acquired, and can be acquired from the database of the monitoring container group when the monitoring server needs the monitoring data. Therefore, the problem that the data acquisition period of the monitoring container group is unequal to the data acquisition period of the monitoring server can be solved.

As an example, the monitoring container group may receive the monitoring data through the data acquisition module and store the monitoring data in the database, and the monitoring service module may obtain the monitoring data from the database and perform data format conversion on the monitoring data to obtain target monitoring data and store the target monitoring data in the database again.

In some embodiments, sending the monitoring data to a monitoring server comprises: and acquiring the target monitoring data from the database and sending the target monitoring data to the monitoring server.

As an example, the monitoring server may send a data obtaining request to the monitoring container group, where the data obtaining request may include a container group identifier and an application identifier, and the monitoring container module may obtain, based on the container group identifier and the application identifier, monitoring data corresponding to both the container group identifier and the application identifier from the database, and send the monitoring data to the monitoring server.

According to the scheme, one monitoring container group is independently deployed to monitor the applications in the service application container groups, so that a monitoring service module does not need to be added in each service application container group, each service application container group only comprises a service processing module of the service processing module, the load of the service application container group is reduced, and the deployment difficulty and the maintenance cost of the container group are also reduced. The above is an exemplary scheme of the application monitoring system of this embodiment. It should be noted that the technical solution of the application monitoring system and the technical solution of the application monitoring method belong to the same concept, and details that are not described in detail in the technical solution of the application monitoring system can be referred to the description of the technical solution of the application monitoring method.

Corresponding to the above embodiment of the application monitoring method applied to the monitoring container group, the present specification further provides an embodiment of an application monitoring apparatus, referring to fig. 7, where fig. 7 is a schematic structural diagram of an application monitoring apparatus provided in an embodiment of the present specification, and the application monitoring apparatus is applied to the monitoring container group, and the apparatus may include:

a first sending module 702, configured to receive a monitoring request, and send the monitoring request to a target service application container group to be monitored;

a second sending module 704, configured to receive the monitoring data and send the monitoring data to the monitoring server.

Optionally, the first sending module 702 is configured to:

the monitoring request comprises a container group identifier, the target service application container group is determined based on the container group identifier, and the monitoring request is sent to the target service application container group.

Optionally, the second sending module 704 is further configured to:

a database is also deployed in the monitoring container group, and data format conversion is carried out on the monitoring data to obtain target monitoring data;

and storing the target monitoring data into the database.

Optionally, the first sending module 702 is further configured to:

receiving an application identifier;

Optionally, the second sending module 704 is configured to:

According to the scheme, one monitoring container group is independently deployed to monitor the applications in the service application container groups, so that a monitoring service module does not need to be added in each service application container group, each service application container group only comprises a service processing module of the service processing module, the load of the service application container group is reduced, and the deployment difficulty and the maintenance cost of the container group are also reduced.

The above is an exemplary scheme of the monitoring device of this embodiment. It should be noted that the technical solution of the application monitoring apparatus and the technical solution of the application monitoring method belong to the same concept, and details that are not described in detail in the technical solution of the application monitoring apparatus can be referred to the description of the technical solution of the application monitoring method.

Fig. 8 illustrates a block diagram of a computing device 800 provided in accordance with an embodiment of the present description. The components of the computing device 800 include, but are not limited to, memory 810 and a processor 820. The processor 820 is coupled to the memory 810 via a bus 830, and the database 850 is used to store data.

Computing device 800 also includes access device 840, access device 840 enabling computing device 800 to communicate via one or more networks 860. Examples of such networks include the Public Switched Telephone Network (PSTN), a Local Area Network (LAN), a Wide Area Network (WAN), a Personal Area Network (PAN), or a combination of communication networks such as the internet. Access device 840 may include one or more of any type of network interface (e.g., a Network Interface Card (NIC)) whether wired or wireless, such as an IEEE802.11 Wireless Local Area Network (WLAN) wireless interface, a worldwide interoperability for microwave access (Wi-MAX) interface, an ethernet interface, a Universal Serial Bus (USB) interface, a cellular network interface, a bluetooth interface, a Near Field Communication (NFC) interface, and so forth.

In one embodiment of the present description, the above-described components of computing device 800, as well as other components not shown in FIG. 8, may also be connected to each other, such as by a bus. It should be understood that the block diagram of the computing device architecture shown in FIG. 8 is for purposes of example only and is not limiting as to the scope of the description. Those skilled in the art may add or replace other components as desired.

Computing device 800 may be any type of stationary or mobile computing device, including a mobile computer or mobile computing device (e.g., tablet, personal digital assistant, laptop, notebook, netbook, etc.), a mobile phone (e.g., smartphone), a wearable computing device (e.g., smartwatch, smartglasses, etc.), or other type of mobile device, or a stationary computing device such as a desktop computer or PC. Computing device 800 may also be a mobile or stationary server.

Wherein, the processor 820 is configured to execute the following computer-executable instructions:

The above is an illustrative scheme of a computing device of the present embodiment. It should be noted that the technical solution of the computing device and the technical solution of the application monitoring method belong to the same concept, and details that are not described in detail in the technical solution of the computing device can be referred to the description of the technical solution of the application monitoring method.

An embodiment of the present specification also provides a computer readable storage medium storing computer instructions that, when executed by a processor, are operable to:

The above is an illustrative scheme of a computer-readable storage medium of the present embodiment. It should be noted that the technical solution of the storage medium belongs to the same concept as the technical solution of the application monitoring method, and details that are not described in detail in the technical solution of the storage medium can be referred to the description of the technical solution of the application monitoring method.

The foregoing description has been directed to specific embodiments of this disclosure. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims may be performed in a different order than in the embodiments and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing may also be possible or may be advantageous.

The computer instructions comprise computer program code which may be in the form of source code, object code, an executable file or some intermediate form, or the like. The computer-readable medium may include: any entity or device capable of carrying the computer program code, recording medium, usb disk, removable hard disk, magnetic disk, optical disk, computer Memory, Read-Only Memory (ROM), Random Access Memory (RAM), electrical carrier wave signals, telecommunications signals, software distribution medium, etc. It should be noted that the computer readable medium may contain content that is subject to appropriate increase or decrease as required by legislation and patent practice in jurisdictions, for example, in some jurisdictions, computer readable media does not include electrical carrier signals and telecommunications signals as is required by legislation and patent practice.

It should be noted that, for the sake of simplicity, the foregoing method embodiments are described as a series of acts or combinations, but those skilled in the art should understand that the present disclosure is not limited by the described order of acts, as some steps may be performed in other orders or simultaneously according to the present disclosure. Further, those skilled in the art should also appreciate that the embodiments described in this specification are preferred embodiments and that acts and modules referred to are not necessarily required for this description.

In the above embodiments, the descriptions of the respective embodiments have respective emphasis, and for parts that are not described in detail in a certain embodiment, reference may be made to related descriptions of other embodiments.

The preferred embodiments of the present specification disclosed above are intended only to aid in the description of the specification. Alternative embodiments are not exhaustive and do not limit the invention to the precise embodiments described. Obviously, many modifications and variations are possible in light of the above teaching. The embodiments were chosen and described in order to best explain the principles of the specification and its practical application, to thereby enable others skilled in the art to best understand the specification and its practical application. The specification is limited only by the claims and their full scope and equivalents.

Claims

1. An application monitoring system is characterized in that the application monitoring system comprises a monitoring container group, at least one service application container group and a monitoring server;

2. The application monitoring system of claim 1, wherein the monitoring container group comprises a monitoring service module and a data collection module;

3. The application monitoring system of claim 2,

4. The application monitoring method system of claim 3,

5. The application monitoring system of claim 3, wherein a database is further deployed in the monitoring container set:

6. The application monitoring system of claim 1 or 2, further comprising an asset configuration management database;

7. The application monitoring system of claim 6,

8. An application monitoring method, applied to a monitoring container group, the method comprising:

9. The application monitoring method according to claim 8, wherein the monitoring request includes a container group identifier, and sending the monitoring request to a target service application container group to be monitored includes:

10. The application monitoring method of claim 8, wherein a database is further deployed in the monitoring container group, and after receiving the monitoring data, the method further comprises:

and storing the target monitoring data into the database.

11. The application monitoring method of claim 8, wherein before sending the monitoring request to the set of target business application containers to be monitored, further comprising:

receiving an application identifier;

12. The application monitoring method of claim 10, wherein sending the monitoring data to a monitoring server comprises:

13. An application monitoring apparatus, the apparatus comprising:

14. A computing device, comprising:

a memory and a processor;

the memory is configured to store computer-executable instructions, and the processor is configured to execute the computer-executable instructions to implement the method of:

15. A computer readable storage medium storing computer instructions which, when executed by a processor, carry out the steps of the application monitoring method of any one of claims 8 to 12.