Unified monitoring data acquisition method and system, electronic equipment and storage medium

Abstract

The invention belongs to the technical field of operation and maintenance monitoring, and discloses a unified monitoring data collection method and system, electronic equipment and a storage medium, and the method comprises the steps: registering a monitoring object at a server side, pushing the configuration information of the monitoring object to a configuration center, initiating a configuration information request to the configuration center by a unified collector, and reading the configuration information of the configuration center; the unified collector collects, analyzes, formats and cleans the monitoring data based on the configuration information through a user-defined plug-in to obtain index data in a format required by Prometheus, and pushes the index data to a router of the unified collector; and the router of the unified collector performs exposure processing on the index data after routing grouping according to a preset rule, and the index data is acquired and analyzed by the monitoring database to generate an alarm event and a notification. Intelligent configuration management can be realized, the system toughness is improved through hierarchical shake resistance, and the security of the system is ensured through an encryption mechanism.

Description

Technical Field

[0001] The present invention belongs to the technical field of operation and maintenance monitoring, and specifically relates to a unified monitoring data acquisition method and system, electronic equipment, and storage medium. Background Art

[0002] In the current mainstream Prometheus monitoring ecosystem, different types of monitoring objects need to deploy different collectors to implement Prometheus monitoring, which has high delivery and maintenance costs and occupies a large amount of server resources. The industry is actively evolving from multiple collectors to unified collectors, unifying collectors according to different dimensions, but there are still problems such as difficulty in configuration and complex configuration management; no downgrade design, insufficient system resilience; interruption of monitoring data under jitter; and direct exposure of sensitive information. Summary of the invention

[0003] Aiming at the deficiencies of the prior art, the present invention discloses a unified monitoring data acquisition method and system, electronic equipment and storage medium.

[0004] The present invention is achieved through the following technical solutions:

[0005] In a first aspect, a unified monitoring data collection method includes:

[0006] Register the monitoring object on the server side, push the configuration information of the monitoring object to the configuration center, and the unified collector initiates a configuration information request to the configuration center to read the configuration information of the configuration center;

[0007] The unified collector collects, parses, formats, and cleans monitoring data based on configuration information through custom plug-ins, obtains indicator data in the format required by Prometheus, and pushes it to the router of the unified collector;

[0008] The router of the unified collector routes and groups the indicator data according to preset rules and then performs exposure processing, which is acquired and analyzed by the monitoring database to generate alarm events and notifications.

[0009] In some embodiments, the configuration center automatically discovers and remotely reads configuration information, and the steps include:

[0010] The server registers the monitored object, generates a kv name according to the type and IP of the monitored object, and then pushes the configuration information of the monitored object to the configuration center according to the naming rules agreed with the unified collector;

[0011] The configuration center receives a configuration write request from the server-side server, distinguishes files by kv name and writes relevant configuration information;

[0012] The unified collector specifies the service address of the configuration center, and when the unified collector is started, it queries and obtains the configuration information of the kv from the configuration center according to the agreed naming rules, and does not need to restart the service for hot update;

[0013] The unified collector initiates configuration acquisition requests at random seconds within the interval period to avoid a sudden increase in the query rate per second at a certain point in time;

[0014] After obtaining the configuration information, the unified collector determines whether there is a difference based on the tag version number, and then updates the local configuration file synchronously.

[0015] In some embodiments, the configuration center includes Consul, Nacos, Apollo, and Etcd distributed coordination services.

[0016] In some embodiments, the unified collector compares the acquired configuration information with the local configuration information, and if there is a difference, reloads the configuration to update the local file.

[0017] In some embodiments, it is determined whether the configuration information of the configuration center is normal. If normal, the unified collector will give priority to reading the latest configuration information from the configuration center for collection. If abnormal, the hierarchical downgrade mechanism will be triggered to read the local configuration file to reload the updated configuration file.

[0018] In some embodiments, the hierarchical degradation mechanism dynamically adjusts system functions, and the steps include:

[0019] The unified collector initiates a configuration read request through a custom plug-in. After obtaining the configuration information from the configuration center, if the configuration center is in normal state, the configuration center is triggered to continuously provide the latest configuration information to the configuration module of the unified collector.

[0020] In the configuration module of the unified collector, each time you try to read the configuration information of the configuration center, you will determine whether the reading of the configuration center status is normal;

[0021] If the reading of the configuration center status is normal, the configuration of the configuration center is read through http and then pushed to the custom plug-in of the unified collector. If it is abnormal, the configuration module of the unified collector will automatically switch to the mode of reading the local configuration file according to the pre-set hierarchical degradation strategy, and push the read local configuration file to the custom plug-in of the unified collector.

[0022] In some embodiments, anti-jitter technology is also included, which dynamically adjusts the data acquisition frequency and accuracy based on an adaptive data sampling rate adjustment algorithm to fully record and accurately restore key indicator data.

[0023] In some embodiments, the unified collector uses a custom plug-in to define the data source, collector frequency and authentication information through the configuration information.

[0024] In some embodiments, the router of the unified collector classifies the acquired monitoring indicator data according to the type of the monitored object, and generates a status page through different HTTP endpoint exposures.

[0025] In some embodiments, security is also included:

[0026] Use a two-factor authentication mechanism to encrypt sensitive information;

[0027] Manage the signature keys of the unified collector and server;

[0028] The double authentication mechanism uses cryptography including AES and RSA;

[0029] The sensitive information includes the password and user identity credential transmission of the monitored object.

[0030] In a second aspect, a unified monitoring data collection system includes:

[0031] The configuration center module is used to register the monitoring object on the server side, push the configuration information of the monitoring object to the configuration center, and the unified collector initiates a configuration information request to the configuration center, and compares the configuration information obtained by the unified collector with the local configuration information. If there is a difference, the local file is reloaded and updated. If there is no difference, the configuration information of the configuration center is read;

[0032] The hierarchical anti-shake module is used to determine whether the configuration of the configuration center is normal. If it is normal, the unified collector will first read the latest configuration information from the configuration center for collection. If it is abnormal, the hierarchical degradation mechanism will be triggered to read the local configuration file to reload the updated configuration file;

[0033] A custom plug-in module is used to collect, parse, format, and clean monitoring data according to the configuration information, obtain indicator data in the format required by Prometheus, and push it to the router of the unified collector;

[0034] The indicator exposure module is used to expose the indicator data by routing groups through the router of the unified collector, and the monitoring database obtains and analyzes the indicator data to generate alarm events and notifications.

[0035] In some embodiments, it also includes a hierarchical anti-shake module, which is used to determine whether the configuration of the configuration center is normal. If it is normal, the unified collector will give priority to reading the latest configuration information from the configuration center for collection. If it is abnormal, the hierarchical downgrade mechanism will be triggered to read the local configuration file to reload the updated one.

[0036] In some embodiments, it also includes a security assurance module for ensuring the security of sensitive information during storage and transmission by adopting measures including a double verification mechanism, selecting a suitable encryption algorithm, and strictly managing signature keys.

[0037] In a third aspect, a computer-readable storage medium is provided, characterized in that one or more programs are stored therein, and when the one or more programs are executed, the above method can be implemented.

[0038] In a fourth aspect, a device comprises a processor, a communication interface, a memory and a communication bus; the processor, the communication interface and the memory communicate with each other via the communication bus; and the processor is used to execute a program stored in the above-mentioned computer-readable storage medium.

[0039] Compared with the prior art, the present invention has the following advantages:

[0040] 1. The cloud-based dynamic configuration management system can easily realize the instant delivery and real-time monitoring of remote batch configuration, greatly improving the operation and maintenance efficiency and response speed;

[0041] 2. Intelligent hierarchical degradation strategy ensures the continuous operation of key data collection functions. Through flexible degradation strategy, the impact of failures on business continuity is reduced, providing users with a more stable and reliable service experience;

[0042] 3. Anti-jitter data processing technology can intelligently sense the system load condition and dynamically adjust the data collection frequency and accuracy to ensure that key indicator data can be fully recorded and accurately restored under high system load. It not only reduces the impact of data loss and abnormal fluctuations, but also improves the quality and reliability of data, providing more solid support for data analysis and decision-making.

[0043] Other features and advantages of the present invention will be described in the following description, and partly become apparent from the description, or be understood by implementing the present use information. The purpose and other advantages of the present invention can be realized and obtained by the structures pointed out in the description, claims and drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0044] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0045] Figure 1This is a schematic diagram of a unified monitoring data collection method flow in this embodiment.

[0046] Figure 2 This is a schematic diagram of the Consul cluster configuration center and automatic discovery process of this embodiment.

[0047] Figure 3 It is a schematic diagram of the Config hierarchical degradation mechanism flow of this embodiment.

[0048] Figure 4 This is a schematic diagram of the data processing flow of the Input custom plug-in of this embodiment.

[0049] Figure 5 The figure is a schematic diagram of the Router indicator grouping and exposure process in this embodiment.

[0050] Figure 6 It is a schematic diagram of the overall architecture of a unified monitoring data collection method of this embodiment.

[0051] Figure 7 This is a schematic diagram of the relationship between the Consul and Config components of this embodiment.

[0052] Figure 8 It is a schematic diagram of the Agent-Config component of this embodiment.

[0053] Fig. 9 It is a schematic diagram of the Agent-Input component of this embodiment.

[0054] Fig.10 It is a schematic diagram of the Agent-Router component of this embodiment.

[0055] Fig.11 This is a schematic diagram of a unified monitoring data collection system of this embodiment.

[0056] Fig.12 It is a schematic diagram of an electronic device of this embodiment. DETAILED DESCRIPTION

[0057] The drawings are only for illustrative purposes and cannot be construed as limiting the present invention. To better illustrate the present embodiment, some parts of the drawings may be omitted, enlarged, or reduced, and do not represent the size of the actual product. For those skilled in the art, it is understandable that some well-known structures and their descriptions may be omitted in the drawings. The positional relationships described in the drawings are only for illustrative purposes and cannot be construed as limiting the present invention.

[0058] In some embodiments, Figure 1 A unified monitoring data collection method shown includes the following steps:

[0059] S1. Register the monitored object on the server side, push the configuration information of the monitored object to the configuration center, and the unified collector initiates a configuration information request to the configuration center to read the configuration information of the configuration center;

[0060] S2. The unified collector collects, parses, formats, and cleans monitoring data based on configuration information through custom plug-ins, obtains indicator data in the format required by Prometheus, and pushes it to the router of the unified collector;

[0061] S3. The router of the unified collector routes and groups the indicator data according to preset rules and then performs exposure processing, which is acquired and analyzed by the monitoring database to generate alarm events and notifications.

[0062] Furthermore, the unified collector compares the acquired configuration information with the local configuration information, and if there is a difference, reloads the configuration to update the local file.

[0063] Specifically, in some embodiments, the configuration center used is Consul as an example, the unified collector is the Agent end, the custom plug-in is the Input module, the router module is the Router module, the server end is the Server end, the configuration module is the Config module, and the monitoring database is Prometheus-VM.

[0064] Specifically, the configuration center uses the Consul cluster to automatically discover and remotely read configuration information, ensuring centralized management and automatic synchronization of configurations, and improving the flexibility and maintainability of the system. The specific process is as follows: Figure 2 As shown, including:

[0065] (1) The server registers the monitored object, generates a kv name according to the type and IP of the monitored object, and then pushes the configuration information of the monitored object to Consul according to the naming rules agreed with the agent. The kv name is a key-value pair (Key-Value) stored in the configuration center in the form of configuration information, such as "username": "root";

[0066] (2) The Consul cluster receives a configuration write request from the server, distinguishes files by kv name and writes relevant configuration information;

[0067] (3) Specify the Consul service address on the Agent side, and query and obtain the kv configuration information from the Consul cluster according to the agreed naming rules when the Agent side is started, without restarting the service for hot update;

[0068] (4) The Agent initiates a configuration acquisition request at a random number of seconds within the interval period to avoid a sudden increase in QPS (Queries Per Second) at a certain point in time;

[0069] (5) After obtaining the configuration information, the Agent will determine whether there is a difference based on the tag version number, and then synchronously update the local configuration file Config file.

[0070] Furthermore, the configuration center also includes Nacos, Apollo and Etcd distributed coordination services, which replace the Consul configuration center to perform remote batch configuration delivery.

[0071] Furthermore, through the hierarchical degradation mechanism of configuration information reading, the system functions are dynamically adjusted to ensure that the core functions can operate normally when the system fails, and the anti-jitter effect of the system is achieved. The specific process is as follows Figure 3 As shown, the following steps are included:

[0072] (1) The Input module on the Agent side initiates a configuration read request. After obtaining the configuration information from the Consul cluster, if the Consul configuration center is in normal status, the Consul cluster is triggered to continuously provide the latest configuration information to the Config module on the Agent side.

[0073] (2) The Config module on the Agent side will determine whether the reading of the Consul configuration center status is normal each time it attempts to read the Consul cluster configuration;

[0074] (3) If the reading of the Consul configuration center status is normal, the Consul configuration is read through http and then pushed to the Input module on the Agent side. If it is abnormal, the Config module on the Agent side will automatically switch to the mode of reading the local configuration file according to the pre-set hierarchical degradation strategy, and push the read local configuration file config file to the Input module on the Agent side.

[0075] Specifically, during the downgrade process, the details and status of the downgrade operation are recorded for subsequent analysis and optimization. When the status of the Consul configuration center returns to normal, the downgraded functions are gradually restored to ensure the full recovery of the system functions. In addition, the downgrade process is evaluated, and the data jitter and loss problems that may occur when the system is under high load are addressed. The adaptive data sampling rate adjustment algorithm is used to intelligently perceive the system load status and dynamically adjust the data collection frequency and accuracy to ensure that the key indicator data can be fully recorded and accurately restored under high system load, thereby improving the overall anti-shake capability of the system.

[0076] Furthermore, the Input module of the Agent seamlessly supports the integration of various plug-ins, which defines the data source, collector frequency and authentication information based on the obtained configuration information, and realizes the collection, analysis, formatting and cleaning of monitoring data. Figure 4 As shown, the following steps are included:

[0077] (1) Based on the configuration information obtained by the Config module of the Agent, define the data source (targets), collector frequency (scrape interval) and authentication information (encrypted storage);

[0078] (2) After the Input module of the Agent obtains the configuration information of the Config module, the Input custom plug-in reads the configuration file and performs initialization at startup, including setting connection parameters and preparing the data capture environment;

[0079] (3) regularly initiating data crawling requests to the data source, including HTTP requests, reading local files, and executing database queries;

[0080] (4) The collected raw data needs to be processed and converted, including data parsing, formatting and cleaning, and the data is converted into the metrics format required by Prometheus, and the processed metric data is pushed to the Router module on the Agent side;

[0081] (5) Record the error information that may occur during the monitoring data collection and processing in the form of a log for subsequent debugging and analysis;

[0082] (6) When the custom plug-in is stopped or reconfigured, it is necessary to clean up and close the data source link and release resources including memory and file statements.

[0083] Furthermore, after the indicator data processed by the Input module of the Agent is pushed to the Router module of the Agent, it is routed and grouped according to the agreed naming rules, and the indicators of different monitoring object types are exposed to different HTTP endpoints for collection by the Prometheus-VM cluster. The specific process is as follows: Figure 5 As shown, the following steps are included:

[0084] (1) The Agent-side Input module pushes the processed monitoring data to the Agent-side Router module in a unified metrics format;

[0085] (2) The Router module classifies the acquired monitoring indicator data according to the type of monitored object and generates a status page through different HTTP endpoints;

[0086] (3) Provide a user identity credential verification algorithm for accessing HTTP endpoints to avoid leakage of exposed metrics;

[0087] (4) The Prometheus-VM cluster carries the encrypted user identity credentials and requests the HTTP endpoint exposed by the Router module on the Agent side. After the user identity is confirmed, the monitoring indicator data is obtained.

[0088] Specifically, in this embodiment, the Prometheus-VM cluster is a monitoring solution and time series database of Prometheus. Through the query engine of Prometheus, the acquired monitoring indicator data is deeply analyzed and mined to identify potential performance bottlenecks and predict system load trends. In addition, when analyzing and processing the monitoring indicator data, if it is found that the monitoring data indicator exceeds the preset threshold or an abnormal situation occurs, the Prometheus-VM cluster generates an alarm event according to preset rules and strategies, and notifies relevant operation and maintenance personnel or other personnel who are concerned about the system operation status through multiple channels including email, SMS and Slack, to ensure that potential problems can be responded to and handled in a timely manner, so as to achieve the ultimate goal of the monitoring system to ensure stable business operation.

[0089] In some embodiments, the unified monitoring data collection method further includes a security assurance process:

[0090] The password of the monitored object is encrypted, stored and transmitted using the AES high-strength encryption algorithm, and is decrypted and used after strict verification by the Agent.

[0091] The user identity credentials for accessing HTTP endpoints use the RSA asymmetric encryption algorithm, with the user's public key encryption and the server's private key decryption. A double verification mechanism is used, with AES encrypting large amounts of data and RSA encrypting keys or short data, which improves the system's ability to resist attacks and avoids the leakage of user identity credentials (such as user names and passwords, API keys), which are important bases for verifying user identities and authorizing access to system resources.

[0092] Double verification is performed through AES and RSA encryption algorithms, and different algorithms are used to complement each other's strengths to improve the system's anti-attack capabilities;

[0093] Before establishing a connection between the Agent and the Server, the signing key is agreed upon through a secure channel. Both parties securely store the key, including physical isolation, access control, and encrypted storage. The key is replaced regularly and its entire life cycle is strictly managed.

[0094] In some embodiments, the unified monitoring data collection method is implemented as follows: Figure 6As shown in the figure, the Agent is a unified collector deployed on the Honghu intelligent operation and maintenance management platform. It performs convergence and integration based on the Prometheus multi-collector ecosystem, and implements remote reading configuration and circuit breaker degradation construction to form a unified collection tool, which includes Input module, Config module and Router module.

[0095] Furthermore, Consul is an open source tool launched by HashiCorp for implementing service discovery and configuration of distributed systems, such as Figure 7 As shown in the figure, multiple Consul nodes form a Consul cluster, which accepts configuration acquisition requests initiated by the Config module on the Agent side at random seconds within the set interval period.

[0096] Further, such as Figure 8 As shown in the figure, the Config module on the Agent side obtains configuration information from Consul via http. If it is compared with the local configuration file config file, if there is a difference, the configuration reload is triggered and written to the local configuration file config file.

[0097] Further, such as Fig. 9 As shown in the figure, the Input module on the Agent side can seamlessly support the integration of various plug-ins, including native plug-ins of Prometheus such as Exporter, widely used open source third-party plug-ins such as telegraf, and self-developed plug-ins customized for specific needs, so as to simplify the integration process and ensure that after the data is captured, it is converted into a unified and standardized format, and the output and sharing of digital display data is easy, thereby improving the overall efficiency and flexibility of the monitoring system.

[0098] Furthermore, the Router module on the Agent side is as follows Fig.10 As shown, the Input module on the Agent side pushes the processed monitoring data to the Router module on the Agent side in a unified metrics format and exposes it, while the Prometheus-VM cluster carries the encrypted user identity credentials and requests the HTTP endpoint exposed by the Router module on the Agent side.

[0099] In some embodiments, Fig.11 A unified monitoring data collection system shown includes:

[0100] The Consul cluster configuration module is used to register the monitoring object on the server side, push the configuration information of the monitoring object to the Consul cluster, and the Agent side initiates a configuration information request to the Consul cluster, and compares the configuration information obtained by the Agent side with the local configuration information. If there is a difference, the local file is reloaded to update the configuration. If there is no difference, the Consul configuration is read;

[0101] The Input custom plug-in module is used to collect, parse, format and clean monitoring data according to the configuration information, obtain the indicator data in the metrics format required by Prometheus, and push it to the Router module on the Agent side;

[0102] The Router indicator exposure module is used to expose the indicator data after grouping them by route, which is acquired and analyzed by the Prometheus-VM cluster to generate alarm events and notifications.

[0103] Furthermore, the unified monitoring data collection system also includes:

[0104] The hierarchical anti-shake module is used to determine whether the Consul configuration is normal. If it is normal, the Agent side will give priority to reading the latest configuration from the Consul cluster for collection. If it is abnormal, the hierarchical downgrade mechanism will be triggered to read the local configuration file to reload the updated one.

[0105] Furthermore, the unified monitoring data collection system also includes:

[0106] The security assurance module is used to ensure the security of sensitive information during storage and transmission by adopting measures including double verification mechanism, selection of appropriate encryption algorithm and strict management of signature keys.

[0107] like Fig.12 As shown, an embodiment of the present disclosure further provides an electronic device, including a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory communicate with each other via the communication bus.

[0108] The memory is a computer-readable storage medium for storing one or more programs.

[0109] The processor is used to execute the program stored in the computer-readable storage medium.

[0110] The computer-readable storage medium may be included in the device / apparatus described in the above embodiments; or may exist independently without being assembled into the device / apparatus.

[0111] Although the present invention has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent substitutions for some of the technical features therein; and these modifications or substitutions do not make the essence of the corresponding technical solutions deviate from the spirit and scope of the technical solutions of the embodiments of the present invention.

Claims

1. A unified monitoring data collection method, characterized in that: include: Register the monitoring object on the server side, push the configuration information of the monitoring object to the configuration center, and the unified collector initiates a configuration information request to the configuration center to read the configuration information of the configuration center; The unified collector collects, parses, formats, and cleans monitoring data based on configuration information through custom plug-ins, obtains indicator data in the format required by Prometheus, and pushes it to the router of the unified collector; The router of the unified collector routes and groups the indicator data according to preset rules and then performs exposure processing, which is acquired and analyzed by the monitoring database to generate alarm events and notifications.

2. A unified monitoring data collection method according to claim 1, characterized in that: The configuration information is automatically discovered and remotely read by the configuration center, and the steps include: The server registers the monitored object, generates a kv name according to the type and IP of the monitored object, and then pushes the configuration information of the monitored object to the configuration center according to the naming rules agreed with the unified collector; The configuration center receives a configuration write request from the server-side server, distinguishes files by kv name and writes relevant configuration information; The unified collector specifies the service address of the configuration center, and when the unified collector is started, it queries and obtains the configuration information of the kv from the configuration center according to the agreed naming rules.

3. A unified monitoring data collection method according to claim 1, characterized in that: The configuration center includes Consul, Nacos, Apollo and Etcd distributed coordination services.

4. The unified monitoring data collection method according to claim 1, characterized in that: The unified collector compares the acquired configuration information with the local configuration information, and if there is a difference, reloads the configuration to update the local file.

5. A unified monitoring data collection method according to claim 1, characterized in that: Reading the configuration information of the configuration center also includes: Determine whether the configuration information of the configuration center is normal. If normal, the unified collector will give priority to reading the latest configuration information from the configuration center for collection. If abnormal, the hierarchical downgrade mechanism will be triggered to read the local configuration file to reload the updated configuration file.

6. A unified monitoring data collection method according to claim 5, characterized in that: The hierarchical degradation mechanism dynamically adjusts system functions, and its steps include: The unified collector initiates a configuration read request through a custom plug-in. After obtaining the configuration information from the configuration center, if the configuration center is in normal state, the configuration center is triggered to continuously provide the latest configuration information to the configuration module of the unified collector. In the configuration module of the unified collector, each time you try to read the configuration information of the configuration center, you will determine whether the reading of the configuration center status is normal; If the reading of the configuration center status is normal, the configuration of the configuration center is read through http and then pushed to the custom plug-in of the unified collector. If it is abnormal, the configuration module of the unified collector will automatically switch to the mode of reading the local configuration file according to the pre-set hierarchical degradation strategy, and push the read local configuration file to the custom plug-in of the unified collector.

7. A unified monitoring data collection method according to claim 1, characterized in that: Also includes anti-jitter technology, Based on the adaptive data sampling rate adjustment algorithm, the data collection frequency and accuracy are dynamically adjusted to fully record and accurately restore key indicator data.

8. A unified monitoring data collection method according to claim 1, characterized in that: The unified collector uses a custom plug-in to define the data source, collector frequency and authentication information through the configuration information.

9. A unified monitoring data collection method according to claim 1, characterized in that: The router of the unified collector classifies the acquired monitoring indicator data according to the type of the monitored object, and generates a status page through different HTTP endpoint exposure.

10. A unified monitoring data collection method according to claim 1, characterized in that: Also includes, security: Use a two-factor authentication mechanism to encrypt sensitive information; Manage the signature keys of the unified collector and server; The double authentication mechanism uses cryptography including AES and RSA; The sensitive information includes the password and user identity credential transmission of the monitored object.

11. A unified monitoring data acquisition system, characterized in that: include: The configuration center module is used to register the monitoring object on the server side, push the configuration information of the monitoring object to the configuration center, and the unified collector initiates a configuration information request to the configuration center, and then reads the configuration information of the configuration center; A custom plug-in module is used to collect, parse, format, and clean monitoring data according to the configuration information, obtain indicator data in the format required by Prometheus, and push it to the router of the unified collector; The indicator exposure module is used to expose the indicator data by routing groups through the router of the unified collector, and the monitoring database obtains and analyzes the indicator data to generate alarm events and notifications.

12. A unified monitoring data acquisition system according to claim 11, characterized in that: Also includes, The hierarchical anti-shake module is used to determine whether the configuration of the configuration center is normal. If it is normal, the unified collector will give priority to reading the latest configuration information from the configuration center for collection. If it is abnormal, the hierarchical downgrade mechanism will be triggered to read the local configuration file to reload the updated one.

13. A unified monitoring data acquisition system according to claim 11, characterized in that: Also includes, The security assurance module is used to ensure the security of sensitive information during storage and transmission by adopting measures including double verification mechanism, selection of appropriate encryption algorithm and strict management of signature keys.

14. A computer-readable storage medium, characterized in that: One or more programs are stored, and when the one or more programs are executed, the methods described in claims 1-10 can be implemented.

15. A device comprising a processor, a communication interface, a memory and a communication bus; the processor, the communication interface and the memory communicate with each other via the communication bus; characterized in that: The processor is used to execute the program stored in the computer-readable storage medium according to claim 14.

Images