CN111459749A - Prometous-based private cloud monitoring method and device, computer equipment and storage medium - Google Patents
Prometous-based private cloud monitoring method and device, computer equipment and storage medium Download PDFInfo
- Publication number
- CN111459749A CN111459749A CN202010189434.6A CN202010189434A CN111459749A CN 111459749 A CN111459749 A CN 111459749A CN 202010189434 A CN202010189434 A CN 202010189434A CN 111459749 A CN111459749 A CN 111459749A
- Authority
- CN
- China
- Prior art keywords
- configuration file
- monitoring
- local disk
- request
- prometous
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3003—Monitoring arrangements specially adapted to the computing system or computing system component being monitored
- G06F11/3006—Monitoring arrangements specially adapted to the computing system or computing system component being monitored where the computing system is distributed, e.g. networked systems, clusters, multiprocessor systems
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3003—Monitoring arrangements specially adapted to the computing system or computing system component being monitored
- G06F11/3034—Monitoring arrangements specially adapted to the computing system or computing system component being monitored where the computing system component is a storage system, e.g. DASD based or network based
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3051—Monitoring arrangements for monitoring the configuration of the computing system or of the computing system component, e.g. monitoring the presence of processing resources, peripherals, I/O links, software programs
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/32—Monitoring with visual or acoustical indication of the functioning of the machine
- G06F11/324—Display of status information
- G06F11/327—Alarm or error message display
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/17—Details of further file system functions
- G06F16/178—Techniques for file synchronisation in file systems
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
Abstract
The embodiment of the invention discloses a Prometheus-based private cloud monitoring method, a Prometheus-based private cloud monitoring device, computer equipment and a storage medium, wherein the method comprises the steps of initiating a first connection request to a main node according to a monitoring request if the monitoring request initiated by a cloud management platform is received; if first response information returned by the main node in response to the first connection request is received within a preset time range, acquiring a first configuration file monitored by Prometous in a local disk of the main node; analyzing the acquired first configuration file to acquire a first data acquisition strategy, and acquiring corresponding data according to the first data acquisition strategy; storing the acquired data into a Prometous database in a local disk of the main node; and performing alarm analysis on corresponding data read from a Prometous database in a local disk of the main node according to a first alarm strategy of the first configuration file. The invention can improve the high availability of private cloud monitoring, can generate an alarm in time and is convenient for a user to operate and maintain.
Description
Technical Field
The invention relates to the field of cloud monitoring, in particular to a Prometous-based private cloud monitoring method and device, computer equipment and a storage medium.
Background
Cloud services are an augmentation, usage, and interaction model for internet-based related services, typically involving the provision of dynamically scalable and often virtualized resources over the internet. The cloud service can put software, hardware and data required by enterprises on a network, and different IT devices are used for interconnection at any time and any place, so that the purposes of data access, operation and the like are achieved. Currently, common Cloud services are Public Cloud (Public Cloud) and Private Cloud (Private Cloud). Among them, Private cloud (Private cloud) is constructed for one client to use alone, and thus can provide the most effective control of data, security and service quality.
The current private cloud scheme is a troffer for each cloud manufacturer, and the most important of the private cloud is the monitoring scheme set by the private cloud, and the monitoring availability determines the delivery reliability of the private cloud scheme and whether an alarm can be generated in time when the availability of the private cloud service is in a problem. At present, the monitoring scheme of the private cloud mostly directly uses the monitoring scheme of the public cloud. Meanwhile, the monitoring scheme of Prometous adopted in the public cloud basically realizes high availability by using a Remote _ read mode and a Remote _ write mode. However, when the private cloud is deployed and delivered and is a small private cloud product scheme, a storage scheme of remote reading and writing is not provided, and when only a storage scheme of a local disk is provided, a remote reading and writing scheme of the private cloud is not available, and at this time, high availability of monitoring cannot be achieved.
Disclosure of Invention
The embodiment of the invention provides a Prometous-based private cloud monitoring method, a Prometous-based private cloud monitoring device, computer equipment and a storage medium, which can improve the high availability of private cloud monitoring, can generate an alarm in time and are convenient for a user to operate and maintain.
In a first aspect, an embodiment of the present invention provides a Prometheus-based private cloud monitoring method, where the method includes:
if a monitoring request initiated by a cloud management platform is received, initiating a first connection request to a main node according to the monitoring request;
if first response information returned by the main node in response to the first connection request is received within a preset time range, acquiring a first configuration file monitored by Prometous in a local disk of the main node, wherein the first configuration file comprises a first data acquisition strategy and a first alarm strategy;
analyzing the acquired first configuration file to acquire the first data acquisition strategy, and acquiring corresponding data according to the first data acquisition strategy;
storing the acquired data into a Prometous database in a local disk of the main node;
and performing alarm analysis on corresponding data read from a Prometous database in a local disk of the main node according to the first alarm strategy of the first configuration file.
In a second aspect, an embodiment of the present invention further provides a Prometheus-based private cloud monitoring apparatus, where the apparatus includes:
the cloud management platform comprises a first request unit and a second request unit, wherein the first request unit is used for initiating a first connection request to a main node according to a monitoring request initiated by a cloud management platform if the monitoring request is received;
a first obtaining unit, configured to obtain a first configuration file monitored by Prometheus in a local disk of a host node if first response information returned by the host node in response to the first connection request is received within a preset time range, where the first configuration file includes a first data acquisition policy and a first alarm policy;
the first processing unit is used for analyzing the acquired first configuration file to acquire the first data acquisition strategy and carrying out corresponding data acquisition according to the first data acquisition strategy;
the first storage unit is used for storing the acquired data into a Prometous database in a local disk of the main node;
and the first analysis unit is used for performing alarm analysis on corresponding data read from a Prometous database in a local disk of the main node according to the first alarm strategy of the first configuration file.
In a third aspect, an embodiment of the present invention further provides a computer device, which includes a memory and a processor, where the memory stores a computer program, and the processor implements the above method when executing the computer program.
In a fourth aspect, the present invention also provides a computer-readable storage medium, which stores a computer program, and the computer program can implement the above method when being executed by a processor.
The embodiment of the invention provides a Prometheus-based private cloud monitoring method and device, computer equipment and a storage medium. Wherein the method comprises the following steps: if a monitoring request initiated by a cloud management platform is received, initiating a first connection request to a main node according to the monitoring request; if first response information returned by the main node in response to the first connection request is received within a preset time range, acquiring a first configuration file monitored by Prometous in a local disk of the main node, wherein the first configuration file comprises a first data acquisition strategy and a first alarm strategy; analyzing the acquired first configuration file to acquire the first data acquisition strategy, and acquiring corresponding data according to the first data acquisition strategy; storing the acquired data into a Prometous database in a local disk of the main node; and performing alarm analysis on corresponding data read from a Prometous database in a local disk of the main node according to the first alarm strategy of the first configuration file. According to the embodiment of the invention, the configuration file for realizing the Prometous monitoring of the corresponding private cloud is arranged on the local disk of the master node and the slave node of the monitoring server of the monitoring service system through the monitoring account of the cloud management platform, and the high-availability monitoring of the private cloud is realized through the alarm strategy configured in the configuration file, so that the alarm can be generated in time when the related data of the private cloud is abnormal, and the effects of improving the high availability of the private cloud monitoring and facilitating the operation and maintenance of a user are ensured under the condition of not increasing the cost.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings needed to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the following description are some embodiments of the present invention, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.
Fig. 1 is a schematic flowchart of a Prometheus-based private cloud monitoring method according to an embodiment of the present invention;
fig. 1a is a schematic view of an application scenario of a Prometheus-based private cloud monitoring method according to an embodiment of the present invention;
fig. 2 is a schematic flowchart of a Prometheus-based private cloud monitoring method according to another embodiment of the present invention;
fig. 3 is a schematic flowchart of a Prometheus-based private cloud monitoring method according to another embodiment of the present invention;
fig. 4 is a schematic block diagram of a Prometheus-based private cloud monitoring apparatus according to an embodiment of the present invention;
fig. 5 is a schematic block diagram of a Prometheus-based private cloud monitoring apparatus according to another embodiment of the present invention;
fig. 6 is a schematic block diagram of a Prometheus-based private cloud monitoring apparatus according to another embodiment of the present invention
Fig. 7 is a schematic structural diagram of a computer device according to an embodiment of the present invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, not all, embodiments of the present invention. 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 invention.
It will be understood that the terms "comprises" and/or "comprising," when used in this specification and the appended claims, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
It is also to be understood that the terminology used in the description of the invention herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. As used in the specification of the present invention 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.
Referring to fig. 1 and fig. 1a, fig. 1 is a schematic flowchart of a Prometheus-based private cloud monitoring method provided in an embodiment of the present application, and fig. 1a is a scene schematic diagram of the Prometheus-based private cloud monitoring method in the embodiment of the present application. The Prometheus-based private cloud monitoring method is applied to a management server 10 in a monitoring service system. The management server 10 sets a configuration file for implementing Prometheus monitoring of the corresponding private cloud on a local disk of a master node and a slave node of the monitoring server 10 of the monitoring service system through a monitoring account of the cloud management platform 20 according to the Prometheus-based private cloud monitoring method, and implements high-availability monitoring of the private cloud through an alarm policy configured in the configuration file. The method can ensure that the monitoring service of Prometous is not interrupted, and an alarm can be generated in time when the related data of the private cloud has an abnormal problem, and improve the high availability of the private cloud monitoring and is convenient for the operation and maintenance of users under the condition of ensuring that the monitoring cost is not increased. The steps of the Prometheus-based private cloud monitoring method will be described in detail below from the perspective of the management server 10.
Referring to fig. 1, fig. 1 is a schematic flow chart of a Prometheus-based private cloud monitoring method according to an embodiment of the present invention. As shown in FIG. 1, the Prometheus-based private cloud monitoring method comprises steps S101 to S105.
Step S101, if a monitoring request initiated by a cloud management platform is received, a first connection request is initiated to a main node according to the monitoring request.
In this embodiment, the monitoring service system is configured to monitor related data information of the cloud management platform, and when a monitoring server of the monitoring service system receives a monitoring request initiated by the user cloud management platform, a first connection request may be initiated to a master node for monitoring in the monitoring service system according to the monitoring request.
Generally, the cloud management platform herein is a platform of a private cloud of a user for implementing management thereof, and the platform may include related servers or a server cluster or the like providing the private cloud. The monitoring service system can monitor related data information of the private cloud, and in order to achieve high availability of monitoring of the private cloud, the monitoring service system comprises a main node for monitoring and a slave node for backing up related information in the main node, wherein the main node is a main monitoring node, and when the main node is down or not connected, the slave node is started.
Step S102, if first response information returned by the main node in response to the first connection request is received within a preset time range, a first configuration file monitored by Prometous in a local disk of the main node is obtained, and the first configuration file comprises a first data acquisition strategy and a first alarm strategy.
In this embodiment, the preset time range may be set according to the requirement of the user. After receiving the first connection request, the master node may correspondingly want to return corresponding first response information to the monitoring server. If the monitoring server can receive the first response information returned by the main node within the preset time range, the fact that the monitoring server and the main node can be connected completely is indicated. The monitoring server can acquire a first configuration file monitored by Prometeus in a local disk of the main node, so as to complete specific monitoring according to the first configuration file.
Typically, the first configuration file is relevant information for configuration monitoring, so it may include a first data collection policy and a first alarm policy. Meanwhile, the first configuration file needs to be set in the local disk of the master node in advance according to user requirements, so that the user can conveniently add, delete and modify the first configuration file and synchronously update the change of the first configuration file to the slave node.
Step S103, analyzing the acquired first configuration file to acquire the first data acquisition strategy, and acquiring corresponding data according to the first data acquisition strategy.
In this embodiment, the monitoring server may analyze the acquired first configuration file, so as to acquire a first data acquisition policy and a first alarm policy. Here, after acquiring the first data acquisition strategy, acquisition of the corresponding data may be achieved according to the first data acquisition strategy. For example, for the private cloud, in order to perform real-time monitoring on the performance, security, and the like of the private cloud, data such as data traffic information, data storage information, and CPU occupation ratio of the server transmitted in the private cloud may be monitored and acquired, and monitoring, warning, and the like of the performance of the private cloud are implemented through subsequent comparative analysis.
Optionally, the first data collection strategy may be to collect and update the relevant data once every preset time.
And step S104, storing the acquired data into a Prometous database in a local disk of the main node.
In this embodiment, after the monitoring server collects corresponding data, in order to facilitate statistical analysis of the related data, the collected data may be stored in a Prometheus database in a local disk of the host node, and when alarm analysis is required, data is called from the Prometheus database, which not only facilitates management of the data, but also facilitates processing and analysis of the data by a user.
Step S105, performing alarm analysis on corresponding data read from the Prometheus database in the local disk of the master node according to the first alarm policy of the first configuration file.
In this embodiment, the monitoring server may read, according to the first alarm policy in the first configuration file, corresponding data from the Prometheus database in the local disk of the master node, and may perform alarm analysis processing on the read related data.
In an embodiment, the method may further comprise the steps of:
step S106, synchronously storing the data stored in the Prometous database in the local disk of the master node into the Prometous database in the local disk of the slave node according to a preset synchronization rule.
In this embodiment, in order to implement high availability of private cloud monitoring, a preset synchronization rule is usually adopted to synchronously store data stored in the promemeus database in the local disk of the master node into the promemeus database in the local disk of the slave node, so as to implement synchronous update of data of the master node and the slave node, so that when one node has a problem, another node can replace the location of the node in real time, thereby implementing monitoring on the private cloud uninterruptedly. Optionally, the preset synchronization rule may be an Rsync tool, and the Rsync tool is a data mirror backup tool, and can implement synchronization of files in different local paths, that is, implement operations such as addition, deletion, and modification of synchronization of local files.
In a further embodiment, the method may further comprise the steps of:
step S107, if a configuration file modification request sent by the cloud management platform is received, modifying the first configuration file in the local disk of the master node according to the configuration file modification request to obtain a new first configuration file.
If the monitoring server receives a configuration file modification request sent by the cloud management platform, the first configuration file in the local disk of the master node can be modified according to the configuration file modification request, and the modified first configuration file is a new first configuration file.
And step S108, synchronizing the new first configuration file in the local disk of the main node to the local disk of the slave node according to a preset synchronization rule so as to replace the original second configuration file, and taking the new second configuration file as a new second configuration file.
After the first configuration file in the master node is modified into a new first configuration file, the new first configuration file can be synchronized to the local disk of the slave node through a preset synchronization rule and used for replacing the original second configuration file, that is, the new first configuration file is used as a new second configuration file, and since the content in the local disk of the slave node is equivalent to the backup of the master node, the first configuration file and the second configuration file between the two are usually the same.
To sum up, in the embodiment of the present invention, a configuration file for implementing Prometheus monitoring of a corresponding private cloud is set on a local disk of a master node and a slave node of a monitoring server of a monitoring service system through a monitoring account of a cloud management platform, and high availability monitoring of the private cloud is implemented through an alarm policy configured in the configuration file, so that an alarm can be generated in time when an abnormal problem occurs in related data of the private cloud, and the effects of improving high availability of private cloud monitoring and facilitating operation and maintenance of a user are ensured without increasing cost.
Referring to fig. 2, fig. 2 is a schematic flow chart of a Prometheus-based private cloud monitoring method according to another embodiment of the present invention. As shown in fig. 2, the steps of the method include steps S201 to S205'. The explanation and detailed description of steps S201 to S205 and steps S101 to S105 in the above embodiment are not repeated herein, and the following detailed description is the added step in this embodiment.
Step S201, if a monitoring request initiated by a cloud management platform is received, initiating a first connection request to a host node according to the monitoring request.
Step S202, if first response information returned by the main node in response to the first connection request is received within a preset time range, a first configuration file monitored by Prometous in a local disk of the main node is obtained, and the first configuration file comprises a first data acquisition strategy and a first alarm strategy.
Step S203, analyzing the acquired first configuration file to acquire the first data acquisition policy, and performing corresponding data acquisition according to the first data acquisition policy.
Step S204, storing the collected data into a Prometous database in a local disk of the main node.
Step S205, performing alarm analysis on corresponding data read from the promemeus database in the local disk of the master node according to the first alarm policy of the first configuration file.
Step S202', if first response information returned by the master node in response to the first connection request is not received within a preset time range, a second connection request is initiated to the slave node according to the monitoring request.
In this embodiment, if the monitoring server does not receive the first response information returned by the master node in response to the first connection request within the preset time range, it indicates that the master node is down or cannot be connected to the cloud management platform, and at this time, a second connection request needs to be initiated to the slave node according to the monitoring request, so as to implement continuous monitoring on the cloud management platform. In general, the handover between the master node and the slave node can be realized by Keepalive, that is, the master node can be quickly handed over to the slave node.
Step S202 a', if second response information returned by the slave node in response to the second connection request is received within a preset time range, obtain a second configuration file monitored by Prometheus in the local disk of the slave node, where the second configuration file includes a second data collection policy and a second alarm policy.
In this embodiment, after the monitoring server performs master-slave switching, if the slave node receives the second connection request and responds to generate the second response information within the preset time range, the second response information can be returned to the monitoring server, and the monitoring server can establish connection with the slave node, so that the second configuration file monitored by Prometheus can be acquired from the local disk of the slave node. Since the slave node is a backup relative to the master node, the second configuration file is also the same as the first configuration file, i.e., the second configuration file also includes a second data collection policy and a second alarm policy.
Step S203', parsing the acquired second configuration file to acquire the second data acquisition policy, and performing corresponding data acquisition according to the second data acquisition policy.
In this embodiment, the monitoring server may analyze the obtained second configuration file, so as to obtain a second data acquisition policy and a second alarm policy. Here, after acquiring the second data acquisition strategy, acquisition of the corresponding data may be implemented according to the second data acquisition strategy. For example, for the private cloud, in order to perform real-time monitoring on the performance, security, and the like of the private cloud, data such as data traffic information, data storage information, and CPU occupation ratio of the server transmitted in the private cloud may be monitored and acquired, and monitoring, warning, and the like of the performance of the private cloud are implemented through subsequent comparative analysis. Alternatively, the related data may be collected and updated once every preset time.
Step S204', store the collected data in the Prometheus database in the local disk of the slave node.
In this embodiment, after the monitoring server collects the corresponding data, in order to facilitate statistical analysis of the related data, the collected data may be stored in the Prometheus database in the local disk of the slave node, and when alarm analysis is required, data is called from the Prometheus database, which not only facilitates management of the data, but also facilitates processing and analysis of the data by the user.
Step S205', perform alarm analysis on corresponding data read from the promemeus database in the local disk of the slave node according to the second alarm policy of the second configuration file.
In this embodiment, the monitoring server may read, according to the second alarm policy in the second configuration file, corresponding data from the Prometheus database in the local disk of the master node, and may perform alarm analysis processing on the read related data.
In an embodiment, the method may further comprise the steps of:
step S206', synchronously storing the data stored in the promemeus database in the local disk of the slave node into the promemeus database in the local disk of the master node according to a preset synchronization rule.
In this embodiment, in order to implement high availability of private cloud monitoring, a preset synchronization rule is usually adopted to synchronously store data stored in the promemeus database in the local disk of the slave node into the promemeus database in the local disk of the master node, so as to implement synchronous update of data of the master node and the slave node, so that when one node has a problem, another node can replace the location of the node in real time, thereby implementing monitoring on the private cloud uninterruptedly. Optionally, the preset synchronization rule may be an Rsync tool, and the Rsync tool is a data mirror backup tool, and can implement synchronization of files in different local paths, that is, implement operations such as addition, deletion, and modification of synchronization of local files.
Optionally, after the monitoring server returns to normal through monitoring, the monitoring server may reuse Prometheus monitoring in the master node through the reverse synchronization performance data and the monitoring configuration information data, so as to provide a high-availability monitoring scheme in a continuously available master-slave mode.
In a further embodiment, the method may further comprise the steps of:
step S207', if a configuration file modification request sent by the cloud management platform is received, modifying the configuration file in the local disk of the slave node according to the configuration file modification request to obtain a new configuration file.
In this embodiment, if the monitoring server receives a configuration file modification request sent by the cloud management platform, the monitoring server may modify the second configuration file in the local disk of the slave node according to the configuration file modification request, where the modified second configuration file is a new second configuration file.
And step S208', synchronizing the new configuration file in the local disk of the slave node to the local disk of the master node according to a preset synchronization rule to replace the original configuration file.
In this embodiment, after the second configuration file in the slave node is modified to become a new second configuration file, the new second configuration file may be synchronized to the local disk of the master node through a preset synchronization rule and used to replace the original first configuration file, that is, the new second configuration file is used as a new first configuration file, and since the content in the local disk of the slave node is equivalent to the backup of the master node, the first configuration file and the second configuration file between the two are generally the same.
Referring to fig. 3, fig. 3 is a schematic flowchart of a Prometheus-based private cloud monitoring method according to another embodiment of the present invention. As shown in fig. 3, the steps of the method include steps S301 a-S305. The related explanations and detailed descriptions of the steps similar to steps S101-S105 in the above embodiment are not repeated herein, and the following detailed descriptions are the added steps in this embodiment.
Step S301a, if a user monitoring login request sent by the cloud management platform is received, analyzing the user monitoring login request to obtain corresponding request information, where the request information includes a user account and a user password.
Step S301b, if the preset database includes the user account, determine whether the preset password associated with the user account matches the user password.
Step S301c, if the preset password associated with the user account matches the user password, the user monitors that the login is successful.
The user can register the monitoring management account on the cloud management platform according to the self requirement, the cloud management platform can be prevented from logging in, the user monitoring login request can be sent to the monitoring server, the monitoring server can analyze the user monitoring login request to obtain the user account and the user password, corresponding matching detection is carried out, if the matching is passed, the user monitoring login is successful, and the monitoring management system can realize comprehensive and sustainable high-availability monitoring on the cloud management platform of the private cloud.
Step S301, if a monitoring request initiated by a cloud management platform is received, a first connection request is initiated to a host node according to the monitoring request.
Step S302, if first response information returned by the master node in response to the first connection request is received within a preset time range, obtaining a first configuration file monitored by Prometheus in a local disk of the master node, where the first configuration file includes a first data acquisition policy and a first alarm policy.
Step S303, analyzing the acquired first configuration file to acquire the first data acquisition policy, and performing corresponding data acquisition according to the first data acquisition policy.
Step S304, storing the collected data in a Prometheus database in the local disk of the master node.
Step S305, performing alarm analysis on corresponding data read from the promemeus database in the local disk of the master node according to the first alarm policy of the first configuration file.
It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by a computer program, which can be stored in a computer-readable storage medium, and when executed, can include the processes of the embodiments of the methods described above. The storage medium may be a magnetic disk, an optical disk, a Read-Only Memory (ROM), or the like.
Referring to fig. 4, in response to the foregoing method for monitoring a private cloud based on Prometheus, an embodiment of the present invention further provides a device for monitoring a private cloud based on Prometheus, where the device 100 includes: a first requesting unit 101, a first obtaining unit 102, a first processing unit 103, a first storage unit 104, and a first analyzing unit 105.
The first request unit 101 is configured to, if a monitoring request initiated by a cloud management platform is received, initiate a first connection request to a host node according to the monitoring request.
In this embodiment, the monitoring service system is configured to monitor related data information of the cloud management platform, and when a monitoring server of the monitoring service system receives a monitoring request initiated by the user cloud management platform, a first connection request may be initiated to a master node for monitoring in the monitoring service system according to the monitoring request.
The first obtaining unit 102 is configured to obtain a first configuration file monitored by Prometheus in a local disk of the master node if first response information returned by the master node in response to the first connection request is received within a preset time range, where the first configuration file includes a first data acquisition policy and a first alarm policy.
In this embodiment, the preset time range may be set according to the requirement of the user. After receiving the first connection request, the master node may correspondingly want to return corresponding first response information to the monitoring server. If the monitoring server can receive the first response information returned by the main node within the preset time range, the fact that the monitoring server and the main node can be connected completely is indicated. The monitoring server can acquire a first configuration file monitored by Prometeus in a local disk of the main node, so as to complete specific monitoring according to the first configuration file.
The first processing unit 103 is configured to parse the acquired first configuration file to acquire the first data acquisition policy, and perform corresponding data acquisition according to the first data acquisition policy.
In this embodiment, the monitoring server may analyze the acquired first configuration file, so as to acquire a first data acquisition policy and a first alarm policy. Here, after acquiring the first data acquisition strategy, acquisition of the corresponding data may be achieved according to the first data acquisition strategy. For example, for the private cloud, in order to perform real-time monitoring on the performance, security, and the like of the private cloud, data such as data traffic information, data storage information, and CPU occupation ratio of the server transmitted in the private cloud may be monitored and acquired, and monitoring, warning, and the like of the performance of the private cloud are implemented through subsequent comparative analysis.
Optionally, the first data collection strategy may be to collect and update the relevant data once every preset time.
The first storage unit 104 is configured to store the acquired data in a Prometheus database in a local disk of the master node.
In this embodiment, after the monitoring server collects corresponding data, in order to facilitate statistical analysis of the related data, the collected data may be stored in a Prometheus database in a local disk of the host node, and when alarm analysis is required, data is called from the Prometheus database, which not only facilitates management of the data, but also facilitates processing and analysis of the data by a user.
The first analysis unit 105 is configured to perform alarm analysis on corresponding data read from a promemeus database in a local disk of the master node according to the first alarm policy of the first configuration file.
In this embodiment, the monitoring server may read, according to the first alarm policy in the first configuration file, corresponding data from the Prometheus database in the local disk of the master node, and may perform alarm analysis processing on the read related data.
In an embodiment, the apparatus 100 may further include the following units:
a first synchronization unit 106, configured to store data stored in the promemeus database in the local disk of the master node into the promemeus database in the local disk of the slave node synchronously according to a preset synchronization rule.
In this embodiment, in order to implement high availability of private cloud monitoring, a preset synchronization rule is usually adopted to synchronously store data stored in the promemeus database in the local disk of the master node into the promemeus database in the local disk of the slave node, so as to implement synchronous update of data of the master node and the slave node, so that when one node has a problem, another node can replace the location of the node in real time, thereby implementing monitoring on the private cloud uninterruptedly. Optionally, the preset synchronization rule may be an Rsync tool, and the Rsync tool is a data mirror backup tool, and can implement synchronization of files in different local paths, that is, implement operations such as addition, deletion, and modification of synchronization of local files.
In a further embodiment, the apparatus 100 may further include the following units:
a first modifying unit 107, configured to modify the first configuration file in the local disk of the master node according to the configuration file modification request to obtain a new first configuration file if the configuration file modification request sent by the cloud management platform is received.
If the monitoring server receives a configuration file modification request sent by the cloud management platform, the first configuration file in the local disk of the master node can be modified according to the configuration file modification request, and the modified first configuration file is a new first configuration file.
A first updating unit 108, configured to synchronize the new first configuration file in the local disk of the master node to the local disk of the slave node according to a preset synchronization rule to replace the original second configuration file, and use the new first configuration file as a new second configuration file.
After the first configuration file in the master node is modified into a new first configuration file, the new first configuration file can be synchronized to the local disk of the slave node through a preset synchronization rule and used for replacing the original second configuration file, that is, the new first configuration file is used as a new second configuration file, and since the content in the local disk of the slave node is equivalent to the backup of the master node, the first configuration file and the second configuration file between the two are usually the same.
Referring to fig. 5, in response to the foregoing method for monitoring a private cloud based on Prometheus, another embodiment of the present invention further provides a device for monitoring a private cloud based on Prometheus, where the device 200 includes: a first requesting unit 201, a first acquiring unit 202, a first processing unit 203, a first storage unit 204, a first analyzing unit 205, a second requesting unit 202 ', a second acquiring unit 202a ', a second processing unit 203 ', a second storage unit 204 ', and a second analyzing unit 205 '. The related explanations and detailed descriptions of the same units as the first requesting unit 101, the first obtaining unit 102, the first processing unit 103, the first storing unit 104, and the first analyzing unit 105 in the above embodiments are not repeated herein, and the following detailed descriptions are the added units in this embodiment.
The first request unit 201 is configured to, if a monitoring request initiated by a cloud management platform is received, initiate a first connection request to a host node according to the monitoring request.
The first obtaining unit 202 is configured to obtain a first configuration file monitored by Prometheus in a local disk of the master node if first response information returned by the master node in response to the first connection request is received within a preset time range, where the first configuration file includes a first data acquisition policy and a first alarm policy.
The first processing unit 203 is configured to parse the acquired first configuration file to acquire the first data acquisition policy, and perform corresponding data acquisition according to the first data acquisition policy.
The first storage unit 204 is configured to store the acquired data in a Prometheus database in a local disk of the master node.
The first analysis unit 205 is configured to perform alarm analysis on corresponding data read from a Prometheus database in a local disk of the master node according to the first alarm policy of the first configuration file.
The second request unit 202' is configured to initiate a second connection request to the slave node according to the monitoring request if first response information returned by the master node in response to the first connection request is not received within a preset time range.
In this embodiment, if the monitoring server does not receive the first response information returned by the master node in response to the first connection request within the preset time range, it indicates that the master node is down or cannot be connected to the cloud management platform, and at this time, a second connection request needs to be initiated to the slave node according to the monitoring request, so as to implement continuous monitoring on the cloud management platform. In general, the handover between the master node and the slave node can be realized by Keepalive, that is, the master node can be quickly handed over to the slave node.
The second obtaining unit 202 a' is configured to obtain a second configuration file monitored by Prometheus in a local disk of the slave node if second response information returned by the slave node in response to the second connection request is received within a preset time range, where the second configuration file includes a second data acquisition policy and a second alarm policy.
In this embodiment, after the monitoring server performs master-slave switching, if the slave node receives the second connection request and responds to generate the second response information within the preset time range, the second response information can be returned to the monitoring server, and the monitoring server can establish connection with the slave node, so that the second configuration file monitored by Prometheus can be acquired from the local disk of the slave node. Since the slave node is a backup relative to the master node, the second configuration file is also the same as the first configuration file, i.e., the second configuration file also includes a second data collection policy and a second alarm policy.
The second processing unit 203' is configured to parse the obtained second configuration file to obtain the second data acquisition policy, and perform corresponding data acquisition according to the second data acquisition policy.
In this embodiment, the monitoring server may analyze the obtained second configuration file, so as to obtain a second data acquisition policy and a second alarm policy. Here, after acquiring the second data acquisition strategy, acquisition of the corresponding data may be implemented according to the second data acquisition strategy. For example, for the private cloud, in order to perform real-time monitoring on the performance, security, and the like of the private cloud, data such as data traffic information, data storage information, and CPU occupation ratio of the server transmitted in the private cloud may be monitored and acquired, and monitoring, warning, and the like of the performance of the private cloud are implemented through subsequent comparative analysis. Alternatively, the related data may be collected and updated once every preset time.
The second storage unit 204' is configured to store the acquired data in a Prometheus database in a local disk of the slave node.
In this embodiment, after the monitoring server collects the corresponding data, in order to facilitate statistical analysis of the related data, the collected data may be stored in the Prometheus database in the local disk of the slave node, and when alarm analysis is required, data is called from the Prometheus database, which not only facilitates management of the data, but also facilitates processing and analysis of the data by the user.
The second analysis unit 205' is configured to perform alarm analysis on corresponding data read from the promemeus database in the local disk of the slave node according to the second alarm policy of the second configuration file.
In this embodiment, the monitoring server may read, according to the second alarm policy in the second configuration file, corresponding data from the Prometheus database in the local disk of the master node, and may perform alarm analysis processing on the read related data.
In an embodiment, the apparatus 200 may further include the following units:
the second synchronization unit 206' is configured to synchronously store data stored in the promemeus database in the local disk of the slave node into the promemeus database in the local disk of the master node according to a preset synchronization rule.
In this embodiment, in order to implement high availability of private cloud monitoring, a preset synchronization rule is usually adopted to synchronously store data stored in the promemeus database in the local disk of the slave node into the promemeus database in the local disk of the master node, so as to implement synchronous update of data of the master node and the slave node, so that when one node has a problem, another node can replace the location of the node in real time, thereby implementing monitoring on the private cloud uninterruptedly. Optionally, the preset synchronization rule may be an Rsync tool, and the Rsync tool is a data mirror backup tool, and can implement synchronization of files in different local paths, that is, implement operations such as addition, deletion, and modification of synchronization of local files.
Optionally, after the monitoring server returns to normal through monitoring, the monitoring server may reuse Prometheus monitoring in the master node through the reverse synchronization performance data and the monitoring configuration information data, so as to provide a high-availability monitoring scheme in a continuously available master-slave mode.
In a further embodiment, the apparatus 200 may further include the following units:
the second modifying unit 207' is configured to, if a configuration file modification request sent by the cloud management platform is received, modify the configuration file in the local disk of the slave node according to the configuration file modification request to obtain a new configuration file.
In this embodiment, if the monitoring server receives a configuration file modification request sent by the cloud management platform, the monitoring server may modify the second configuration file in the local disk of the slave node according to the configuration file modification request, where the modified second configuration file is a new second configuration file.
The second updating unit 208' is configured to synchronize the new configuration file in the local disk of the slave node to the local disk of the master node according to a preset synchronization rule to replace the original configuration file.
In this embodiment, after the second configuration file in the slave node is modified to become a new second configuration file, the new second configuration file may be synchronized to the local disk of the master node through a preset synchronization rule and used to replace the original first configuration file, that is, the new second configuration file is used as a new first configuration file, and since the content in the local disk of the slave node is equivalent to the backup of the master node, the first configuration file and the second configuration file between the two are generally the same.
Referring to fig. 6, in response to the method for monitoring a private cloud based on Prometheus, another embodiment of the present invention further provides a device for monitoring a private cloud based on Prometheus, where the device 300 includes: a requesting unit 301a, a judging unit 301b, a logging unit 301c, a first requesting unit 301, a first obtaining unit 302, a first processing unit 303, a first storing unit 304, and a first analyzing unit 305. The related explanations and detailed descriptions of the same units as the first requesting unit 101, the first obtaining unit 102, the first processing unit 103, the first storing unit 104, and the first analyzing unit 105 in the above embodiments are not repeated herein, and the following detailed descriptions are the added units in this embodiment.
The requesting unit 301a is configured to, if a user monitoring login request sent by a cloud management platform is received, analyze the user monitoring login request to obtain corresponding request information, where the request information includes a user account and a user password.
The determining unit 301b is configured to determine whether a preset password associated with the user account matches the user password if the preset database includes the user account.
The login unit 301c is configured to monitor that login is successful if the preset password associated with the user account matches the user password.
The user can register the monitoring management account on the cloud management platform according to the self requirement, the cloud management platform can be prevented from logging in, the user monitoring login request can be sent to the monitoring server, the monitoring server can analyze the user monitoring login request to obtain the user account and the user password, corresponding matching detection is carried out, if the matching is passed, the user monitoring login is successful, and the monitoring management system can realize comprehensive and sustainable high-availability monitoring on the cloud management platform of the private cloud.
The first request unit 301 is configured to, if a monitoring request initiated by a cloud management platform is received, initiate a first connection request to a host node according to the monitoring request.
A first obtaining unit 302, configured to obtain a first configuration file monitored by Prometheus in a local disk of a host node if first response information returned by the host node in response to the first connection request is received within a preset time range, where the first configuration file includes a first data acquisition policy and a first alarm policy.
The first processing unit 303 is configured to parse the acquired first configuration file to acquire the first data acquisition policy, and perform corresponding data acquisition according to the first data acquisition policy.
A first storage unit 304, configured to store the acquired data in a promemeus database in a local disk of the master node.
A first analysis unit 305, configured to perform alarm analysis on corresponding data read from a Prometheus database in a local disk of the master node according to a first alarm policy of the first configuration file.
It should be noted that, as can be clearly understood by those skilled in the art, for the specific implementation process of the foregoing Prometheus-based private cloud monitoring apparatus 100 and each unit, reference may be made to the corresponding description in the foregoing method embodiment, and for convenience and brevity of description, no further description is provided herein.
As can be seen from the above, in terms of hardware implementation, the above first requesting unit 101, the first obtaining unit 102, the first processing unit 103, the first storage unit 104, the first analyzing unit 105, and the like may be embedded in a hardware form or independent of the Prometheus-based private cloud monitoring apparatus, or may be stored in a software form in a memory of the Prometheus-based private cloud monitoring apparatus, so that the processor calls to execute operations corresponding to the above units. The processor can be a Central Processing Unit (CPU), a microprocessor, a singlechip and the like.
The Prometheus-based private cloud monitoring apparatus may be implemented in the form of a computer program, which may run on a computer device as shown in fig. 7.
FIG. 7 is a schematic diagram of a computer device according to the present invention. The device may be a server, where the server may be an independent server or a server cluster composed of a plurality of servers.
Referring to fig. 7, the computer device 400 includes a processor 402, a memory, an internal memory 404, and a network interface 405 connected by a system bus 401, wherein the memory may include a nonvolatile storage medium 403 and the internal memory 404.
The non-volatile storage medium 403 may store an operating system 4031 and a computer program 4032, which when executed, may cause the processor 402 to perform a Prometheus-based private cloud monitoring method.
The processor 402 is used to provide computing and control capabilities that support the operation of the overall computer device 400.
The memory 404 provides an environment for running the computer program 4032 in the non-volatile storage medium 403, and when the computer program 4032 is executed by the processor 402, the processor 402 can be caused to execute a Prometheus-based private cloud monitoring method.
The network interface 405 is used for network communication with other devices. Those skilled in the art will appreciate that the architecture shown in fig. 7 is merely a block diagram of some of the structures associated with the disclosed aspects and is not intended to limit the computing device 400 to which the disclosed aspects apply, as a particular computing device 400 may include more or less components than those shown, or may combine certain components, or have a different arrangement of components.
The processor 402 is configured to run the computer program 4032 stored in the memory to implement the steps of the Prometheus-based private cloud monitoring method in the above embodiments.
It should be understood that in the embodiment of the present Application, the Processor 402 may be a Central Processing Unit (CPU), and the Processor 402 may also be other general-purpose processors, Digital Signal Processors (DSPs), Application Specific Integrated Circuits (ASICs), Field-Programmable gate arrays (FPGAs) or other Programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, and the like. Wherein a general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
It will be understood by those skilled in the art that all or part of the flow of the method implementing the above embodiments may be implemented by a computer program instructing associated hardware. The computer program may be stored in a storage medium, which is a computer-readable storage medium. The computer program is executed by at least one processor in the computer system to implement the flow steps of the embodiments of the method described above.
Accordingly, the present invention also provides a storage medium. The storage medium may be a computer-readable storage medium. The storage medium stores a computer program that, when executed by a processor, causes the processor to perform the steps of the Prometheus-based private cloud monitoring method in the above-described embodiments.
The storage medium is an entity and non-transitory storage medium, and may be various entity storage media capable of storing program codes, such as a usb disk, a removable hard disk, a Read-only memory (ROM), a magnetic disk, or an optical disk.
Those of ordinary skill in the art will appreciate that the elements and algorithm steps of the examples described in connection with the embodiments disclosed herein may be embodied in electronic hardware, computer software, or combinations of both, and that the components and steps of the examples have been described in a functional general in the foregoing description for the purpose of illustrating clearly the interchangeability of hardware and software. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.
In the embodiments provided in the present invention, it should be understood that the disclosed apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative. For example, the division of each unit is only one logic function division, and there may be another division manner in actual implementation. For example, various elements or components may be combined or may be integrated into another system, or some features may be omitted, or not implemented.
The steps in the method of the embodiment of the invention can be sequentially adjusted, combined and deleted according to actual needs. The units in the device of the embodiment of the invention can be merged, divided and deleted according to actual needs. In addition, functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit.
The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a storage medium. Based on such understanding, the technical solution of the present invention essentially or partially contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a terminal, or a network device) to execute all or part of the steps of the method according to the embodiments of the present invention.
While the invention has been described with reference to specific embodiments, the invention is not limited thereto, and various equivalent modifications and substitutions can be easily made by those skilled in the art within the technical scope of the invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the claims.
Claims (10)
1. A Prometous-based private cloud monitoring method is characterized by comprising the following steps:
if a monitoring request initiated by a cloud management platform is received, initiating a first connection request to a main node according to the monitoring request;
if first response information returned by the main node in response to the first connection request is received within a preset time range, acquiring a first configuration file monitored by Prometous in a local disk of the main node, wherein the first configuration file comprises a first data acquisition strategy and a first alarm strategy;
analyzing the acquired first configuration file to acquire the first data acquisition strategy, and acquiring corresponding data according to the first data acquisition strategy;
storing the acquired data into a Prometous database in a local disk of the main node;
and performing alarm analysis on corresponding data read from a Prometous database in a local disk of the main node according to the first alarm strategy of the first configuration file.
2. The method of claim 1, wherein the method further comprises:
and synchronously storing the data stored in the Prometous database in the local disk of the master node into the Prometous database in the local disk of the slave node according to a preset synchronization rule.
3. The method of claim 1, wherein the method further comprises:
if a configuration file modification request sent by a cloud management platform is received, modifying a first configuration file in a local disk of the main node according to the configuration file modification request to obtain a new first configuration file;
and synchronizing the new first configuration file in the local disk of the main node to the local disk of the slave node according to a preset synchronization rule to replace the original second configuration file, wherein the new first configuration file is used as a new second configuration file.
4. The method of claim 1, wherein after the step of initiating the first connection request to the master node according to the monitoring request if the monitoring request initiated by the cloud management platform is received, the method further comprises:
if first response information returned by the main node in response to the first connection request is not received within a preset time range, a second connection request is initiated to the slave node according to the monitoring request;
if second response information returned by the slave node in response to the second connection request is received within a preset time range, acquiring a second configuration file monitored by Prometous in a local disk of the slave node, wherein the second configuration file comprises a second data acquisition strategy and a second alarm strategy;
analyzing the obtained second configuration file to obtain the second data acquisition strategy, and performing corresponding data acquisition according to the second data acquisition strategy;
storing the collected data into a Prometous database in a local disk of the slave node;
and performing alarm analysis on corresponding data read from a Prometous database in a local disk of the slave node according to a second alarm strategy of the second configuration file.
5. The method of claim 4, wherein the method further comprises:
and synchronously storing the data stored in the Prometous database in the local disk of the slave node into the Prometous database in the local disk of the master node according to a preset synchronization rule.
6. The method of claim 4, wherein the method further comprises:
if a configuration file modification request sent by a cloud management platform is received, modifying a configuration file in a local disk of the slave node according to the configuration file modification request to obtain a new configuration file;
and synchronizing the new configuration file in the local disk of the slave node to the local disk of the master node according to a preset synchronization rule to replace the original configuration file.
7. The method of claim 1, wherein before the step of initiating the first connection request to the master node according to the monitoring request if the monitoring request initiated by the cloud management platform is received, the method further comprises:
if a user monitoring login request sent by a cloud management platform is received, analyzing the user monitoring login request to obtain corresponding request information, wherein the request information comprises a user account and a user password;
if the preset database comprises the user account, judging whether a preset password associated with the user account is matched with the user password;
and if the preset password associated with the user account is matched with the user password, the user monitors that the login is successful.
8. A Prometheus-based private cloud monitoring apparatus, the apparatus comprising:
the cloud management platform comprises a first request unit and a second request unit, wherein the first request unit is used for initiating a first connection request to a main node according to a monitoring request initiated by a cloud management platform if the monitoring request is received;
a first obtaining unit, configured to obtain a first configuration file monitored by Prometheus in a local disk of a host node if first response information returned by the host node in response to the first connection request is received within a preset time range, where the first configuration file includes a first data acquisition policy and a first alarm policy;
the first processing unit is used for analyzing the acquired first configuration file to acquire the first data acquisition strategy and carrying out corresponding data acquisition according to the first data acquisition strategy;
the first storage unit is used for storing the acquired data into a Prometous database in a local disk of the main node;
and the first analysis unit is used for performing alarm analysis on corresponding data read from a Prometous database in a local disk of the main node according to the first alarm strategy of the first configuration file.
9. A computer arrangement, characterized in that the computer arrangement comprises a memory having stored thereon a computer program and a processor implementing the method according to any of claims 1-7 when executing the computer program.
10. A computer-readable storage medium, characterized in that the storage medium stores a computer program which, when executed by a processor, causes the processor to carry out the method according to any one of claims 1-7.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010189434.6A CN111459749A (en) | 2020-03-18 | 2020-03-18 | Prometous-based private cloud monitoring method and device, computer equipment and storage medium |
| PCT/CN2020/099190 WO2021184587A1 (en) | 2020-03-18 | 2020-06-30 | Prometheus-based private cloud monitoring method and apparatus, and computer device and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010189434.6A CN111459749A (en) | 2020-03-18 | 2020-03-18 | Prometous-based private cloud monitoring method and device, computer equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111459749A true CN111459749A (en) | 2020-07-28 |
Family
ID=71683202
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010189434.6A Pending CN111459749A (en) | 2020-03-18 | 2020-03-18 | Prometous-based private cloud monitoring method and device, computer equipment and storage medium |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN111459749A (en) |
| WO (1) | WO2021184587A1 (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112511339A (en) * | 2020-11-09 | 2021-03-16 | 宝付网络科技（上海）有限公司 | Container monitoring alarm method, system, equipment and storage medium based on multiple clusters |
| CN112650644A (en) * | 2020-12-22 | 2021-04-13 | 南方电网深圳数字电网研究院有限公司 | Monitoring method and system based on prometheus |
| CN114666249A (en) * | 2020-12-03 | 2022-06-24 | 腾讯科技（深圳）有限公司 | Traffic collection method and device on cloud platform and computer-readable storage medium |
Families Citing this family (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114553740B (en) * | 2022-03-11 | 2023-11-10 | 以萨技术股份有限公司 | Method, system, readable storage medium and device for cross-network monitoring |
| CN114866551A (en) * | 2022-06-06 | 2022-08-05 | 中国工商银行股份有限公司 | Prometous cluster processing method, device, equipment and storage medium |
| CN116737514B (en) * | 2023-08-15 | 2023-12-22 | 南京国睿信维软件有限公司 | Automatic operation and maintenance method based on log and probe analysis |
Family Cites Families (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104486445B (en) * | 2014-12-30 | 2017-03-22 | 北京天云融创软件技术有限公司 | Distributed extendable resource monitoring system based on cloud platform |
| CN109245931B (en) * | 2018-09-19 | 2021-04-16 | 四川虹微技术有限公司 | Log management and monitoring alarm realization method of container cloud platform based on kubernets |
| KR102062576B1 (en) * | 2018-10-10 | 2020-01-06 | 숭실대학교산학협력단 | Vnf monitoring system for monitoring both virtual network function based on virtual machine and virtual network function based on container |
| CN109586999B (en) * | 2018-11-12 | 2021-03-23 | 深圳先进技术研究院 | Container cloud platform state monitoring and early warning system and method and electronic equipment |
| CN110247810B (en) * | 2019-07-09 | 2023-03-28 | 浪潮云信息技术股份公司 | System and method for collecting container service monitoring data |
| CN110659109B (en) * | 2019-09-26 | 2023-07-04 | 上海仪电（集团）有限公司中央研究院 | System and method for monitoring openstack virtual machine |
-
2020
- 2020-03-18 CN CN202010189434.6A patent/CN111459749A/en active Pending
- 2020-06-30 WO PCT/CN2020/099190 patent/WO2021184587A1/en active Application Filing
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112511339A (en) * | 2020-11-09 | 2021-03-16 | 宝付网络科技（上海）有限公司 | Container monitoring alarm method, system, equipment and storage medium based on multiple clusters |
| CN114666249A (en) * | 2020-12-03 | 2022-06-24 | 腾讯科技（深圳）有限公司 | Traffic collection method and device on cloud platform and computer-readable storage medium |
| CN114666249B (en) * | 2020-12-03 | 2023-07-07 | 腾讯科技（深圳）有限公司 | Traffic collection method and equipment on cloud platform and computer readable storage medium |
| CN112650644A (en) * | 2020-12-22 | 2021-04-13 | 南方电网深圳数字电网研究院有限公司 | Monitoring method and system based on prometheus |
Also Published As
| Publication number | Publication date |
|---|---|
| WO2021184587A1 (en) | 2021-09-23 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111459749A (en) | Prometous-based private cloud monitoring method and device, computer equipment and storage medium | |
| CN106331098B (en) | Server cluster system | |
| US9405757B2 (en) | File storage system, apparatus, and file access method | |
| US10044551B2 (en) | Secure cloud management agent | |
| CN111459750A (en) | Private cloud monitoring method and device based on non-flat network, computer equipment and storage medium | |
| AU2011282755B2 (en) | Dynamic migration within a network storage system | |
| CN107819891B (en) | Data processing method, data processing device, computer equipment and storage medium | |
| CN111800443B (en) | Data processing system and method, device and electronic equipment | |
| WO2021227677A1 (en) | Scene pushing method, scene executing method, scene pushing device, scene executing device, terminal, server, and system | |
| CN114500521A (en) | Computing power scheduling method, device, scheduling equipment, system and storage medium | |
| CN107666493B (en) | Database configuration method and equipment thereof | |
| CN109586969A (en) | Content distributing network disaster recovery method, device, computer equipment and storage medium | |
| CN111800285B (en) | Instance migration method and device and electronic equipment | |
| CN106452836B (en) | main node setting method and device | |
| CN103716384A (en) | Method and device for realizing cloud storage data synchronization in cross-data-center manner | |
| CN110534136B (en) | Recording method and device | |
| CN111342986A (en) | Distributed node management method and device, distributed system and storage medium | |
| CN113489149A (en) | Power grid monitoring system service master node selection method based on real-time state perception | |
| US11153173B1 (en) | Dynamically updating compute node location information in a distributed computing environment | |
| WO2018010603A1 (en) | Storage mode upgrade method, apparatus and system based on video cloud storage system | |
| CN106453118B (en) | Flow control method and flow control system | |
| CN114745413A (en) | Access control method and device for server, computer equipment and storage medium | |
| CN115174596A (en) | Equipment remote copying method, device and medium | |
| CN112199176A (en) | Service processing method, device and related equipment | |
| CN109474694A (en) | A kind of management-control method and device of the NAS cluster based on SAN storage array |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| REG | Reference to a national code |
Ref country code: HK Ref legal event code: DE Ref document number: 40032036 Country of ref document: HK |
|
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |