Processing system for index data acquisition based on Promisius probe

By introducing a Prometheus-based probe indicator data acquisition and processing system in the Prometheus system, the indicator acquisition configuration and data release are automated, which solves the problem of inflexible deployment and configuration in the existing technology, and improves monitoring expansion Efficiency and flexibility.

CN118939512AInactive Publication Date: 2024-11-12HUNAN VOCATIONAL COLLEGE OF SCI & TECH
View PDF 4 Cites 0 Cited by

Patent Information

Application Number
CN202411428118.4
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-10-14
Publication Date
2024-11-12
Estimated Expiration
Not applicable · inactive patent

AI Technical Summary

Technical Problem

The existing custom script expansion using probes is not flexible enough in cloud-native and distributed system architectures, which requires manual script release and update, and the monitoring and scaling efficiency in cluster environments is inefficient.

Method used

Provide a Prometheus-based probe indicator data acquisition and processing system, including server and client. By configuring service modules, synchronization service modules, execution modules and storage modules, automated indicator collection configuration and data release are eliminated. Manually upgrade complexity and improve monitoring and scaling efficiency.

Benefits of technology

It realizes flexible configuration and rapid expansion of metric data, automates script release and scheduling, improves monitoring efficiency and flexibility in cluster environments, and reduces the complexity of manual operations.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118939512A_ABST
    Figure CN118939512A_ABST
Patent Text Reader

Abstract

The invention provides a processing system for index data acquisition based on a probe in Promise, and belongs to the field of data processing. The system comprises a server and a client, a configuration service module of the server is used for acquiring index configuration information, label configuration information and environment variable configuration information, generating index acquisition configuration information based on the index configuration information, the label configuration information and the environment variable configuration information, and issuing the index acquisition configuration information; the synchronization service module of the client is used for synchronizing the released index acquisition configuration information from the configuration service module; an execution module of the client is used for calling a probe to execute index acquisition configuration information and generating corresponding index data; the storage module of the client is used for storing the synchronized index acquisition configuration information and index data; and the data acquisition module of the server is used for acquiring the index data from the storage module. According to the invention, the efficiency of monitoring expansion in the cluster environment is improved.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the field of data processing, and more specifically, to a processing system for collecting indicator data based on probes in Prometheus. Background Art

[0002] In modern cloud-native and distributed system architectures, the importance of monitoring systems is self-evident. As an open source monitoring and alerting toolkit, Prometheus has been widely used in various environments, including cloud computing, containerized deployment, and microservice architecture, due to its powerful data collection, efficient query language, and flexible alert system.

[0003] Probes (Exporters) are components in the Prometheus ecosystem that are used to expose monitoring indicators. They are responsible for collecting indicators from various data sources and exposing them in a format that Prometheus can understand (usually an HTTP-based protocol). There are many probe components in Prometheus. Using different probe components to perform custom script extensions can achieve the collection of multiple indicator data. For example, node_exporter is an Exporter specifically used for Linux system monitoring, which can collect and expose multiple system performance indicators including CPU, memory, disk, and network.

[0004] However, the existing use of probes for custom script extension still has one or more of the following defects: 1) The release and update of the script needs to be handled manually, or other tools need to be deployed uniformly; 2) The execution of the script needs to be configured in the crontab on each monitored operating system; 3) The environment variables required by the script also need to be configured separately on each server, or the environment variables need to be added to the startup script; 4) If the file is being written when the node_exporter is collecting, it may cause problems with the file; 5) If there is a need to release a new script, upgrade, or if the already released script needs to be stopped and deleted, it cannot be managed well. Summary of the invention

[0005] In view of this, it is necessary to provide a processing system for collecting indicator data based on probes in Prometheus to solve at least one of the above technical problems.

[0006] In one of the embodiments, a processing system for collecting indicator data based on a probe in Prometheus is provided, the system comprising: a server and at least one client connected to the server via a network, the server comprising a configuration service module and a data collection module, the client comprising a synchronization service module, an execution module, and a storage module; The configuration service module is used to obtain indicator configuration information, label configuration information and environment variable configuration information, generate indicator collection configuration information based on the indicator configuration information, label configuration information and environment variable configuration information, and publish the indicator collection configuration information; The synchronization service module is used to synchronize the published indicator collection configuration information from the configuration service module; The execution module is used to call the probe to execute the indicator collection configuration information and generate corresponding indicator data; The storage module is used to store the synchronized indicator collection configuration information and the indicator data; The data acquisition module is used to obtain the indicator data from the storage module.

[0007] In one of the embodiments, the execution module is also used to call the probe, execute the indicator collection configuration information according to the execution cycle and environment variable configuration information in the indicator collection configuration information, and convert the output data after execution so that the generated indicator data is indicator data that can be recognized by Prometheus.

[0008] In one of the embodiments, the storage module is further used to expose the stored indicator data to the outside according to a pre-registered unified port; The data collection module is also used to call the unified port to obtain the exposed indicator data.

[0009] In one of the embodiments, the configuration service module is further used to generate a version number for the indicator collection configuration information, and associate the version number with one or more client identifiers in the client list; The synchronization service module is further used to synchronize the published indicator collection configuration information from the configuration service module according to the client identifier.

[0010] In one of the embodiments, the synchronization service module is further used to obtain a client identifier of the client according to the connection between the client and the server, and maintain the client list based on the obtained client identifier.

[0011] In one of the embodiments, the storage module is further used to update the stored indicator collection configuration information according to the version number, and delete the indicator collection configuration information with a version number inconsistent with that published in the configuration service module.

[0012] In one of the embodiments, the configuration service module is also used to generate a corresponding version number when the indicator configuration information and label configuration information are created, obtain a selection instruction for the client identifier, trigger an indicator collection configuration information release instruction based on the selection instruction, and write the indicator collection configuration information, the selected client identifier and the version number into a version release table.

[0013] In one of the embodiments, the synchronization service module is also used to query the target version number associated with the client's own client identifier from the version release table, and detect whether the target version number is consistent with the version number present in the storage module. If inconsistent, the indicator collection configuration information corresponding to the target version number is obtained, and the indicator collection configuration information corresponding to the inconsistent version number is deleted.

[0014] In one of the embodiments, the execution module is further used to call the probe to execute the indicator collection configuration information according to a preset scheduling period, and the execution period is an integer multiple of the scheduling period.

[0015] In one of the embodiments, when the environment variable value in the environment variable configuration information is a null value, a corresponding default value is used to replace the null value.

[0016] The processing system for collecting indicator data by the probe in Prometheus disclosed in the present application is used to expand the function of the probe Exporter customized by the Prometheus system by building a unified platform framework. It allows users to write and configure parameters such as indicators, tags, and environment variables, thereby realizing the monitoring and collection configuration of indicator data, and improving the flexibility of indicator data configuration. And by setting a synchronization service module on the server side, users can publish indicator collection configuration information to the specified client, thereby realizing the rapid expansion of monitoring indicators. Users only need to focus on writing scripts for data collection. Since the system can automatically publish these scripts, the complexity of manually upgrading the collection code is eliminated. In addition, because the scripts are called by the platform itself, users do not need to schedule these scripts by themselves, which greatly improves the efficiency and flexibility of monitoring expansion in a cluster environment. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required for use in the embodiments will be briefly introduced below. It should be understood that the following drawings only show certain embodiments of the present application and therefore should not be regarded as limiting the scope of the present application.

[0018] Figure 1 The figure is a schematic diagram of the structure of a processing system for collecting indicator data based on probes in Prometheus in one embodiment. DETAILED DESCRIPTION

[0019] Hereinafter, embodiments of the present application will be described with reference to the accompanying drawings. However, it should be understood that these descriptions are exemplary only and are not intended to limit the scope of the present application. In addition, in the following description, descriptions of well-known structures and technologies are omitted to avoid unnecessary confusion of the concepts of the present application.

[0020] The terms used herein are only for describing specific embodiments and are not intended to limit the present application. The words "a", "an (kind)" and "the" used herein should also include the meanings of "multiple" and "multiple", unless the context clearly indicates otherwise. In addition, the terms "including", "comprising" and the like used herein indicate the existence of corresponding features, steps, operations and / or components, but do not exclude the existence or addition of one or more other features, steps, operations or components.

[0021] It should be noted that the terms "first", "second", etc. in the specification and claims of this application are only used to distinguish and describe similar objects, rather than to describe a specific order or sequence, and cannot be understood as indicating or implying relative importance.

[0022] All terms (including technical and scientific terms) used herein have the meanings commonly understood by those skilled in the art unless otherwise defined. It should be noted that the terms used herein should be interpreted as having a meaning consistent with the context of this specification and should not be interpreted in an idealized or overly rigid manner.

[0023] As mentioned above, in the prior art, when using a probe (Exporter) in a Prometheus system to collect indicator data, corresponding codes are written for the specific indicator data to be collected, and the code is directly published to the corresponding client device for execution, which has the defect of inflexible deployment and configuration.

[0024] In this application, combined Figure 1 As shown, a processing system for collecting indicator data based on the probe in Prometheus is provided, and the system includes: a server 100 and at least one client, such as the client 200-1 and the client 200-2 shown in the figure. Among them, the server 100 and each client are deployed with the Prometheus system, and each client can communicate with the server 100 through the network, so that the indicator collection configuration information can be obtained from the server, and the indicator collection configuration information can be executed to generate corresponding indicator data, and the server 100 can obtain the indicator data generated by each client, so as to complete the corresponding analysis and monitoring of each client according to the indicator data. The server 100 can be a server or a server cluster, and the client can be any terminal or server device such as a mobile phone, a computer or a tablet computer.

[0025] Among them, the indicator data refers to data that can reflect a certain operating performance or operating status of the client, such as the startup time of MySQL on the client, the number of database connections, the current operating status of the MySQL instance, such as the number of slow queries, etc. It can also include the total memory size of the host, the size of the unused memory of the host, the amount of available memory of the host, the total size of the disk file system, the available space of the file system, the disk I / O time, the total number of bytes received / sent by the network interface, the CPU usage time in various modes, the average load of the system in the recent period, the number of currently running processes, the temperature of the CPU and other hardware, and any other appropriate indicator data related to the client performance. The user can write any indicator data that needs to be monitored on the server as needed to form indicator data collection information to provide to the client for execution.

[0026] like Figure 1 As shown, the server 100 includes a UI interface module 110, a configuration service module 120 and a data collection module 130, and the client includes a synchronization service module 210, an execution module 220 and a storage module 230. The configuration service module is used to obtain indicator configuration information, label configuration information and environment variable configuration information, generate indicator collection configuration information based on the indicator configuration information, label configuration information and environment variable configuration information, and publish the indicator collection configuration information.

[0027] The indicator configuration information represents the configuration for the above indicator information, which defines the specific metrics or indicators that need to be collected from the target client (such as client 200-1) or application. These indicators can be system resource usage (such as CPU, memory, disk, network, etc.), process status, service response time, etc.

[0028] The tag configuration information indicates the identifier or dimension of the target client or application corresponding to the indicator information to be extracted, and is used to add additional identifiers or dimensions to the collected indicator data. These tags can help users clearly identify the target clients or target applications for which indicator data should be collected, so that indicator data can be better classified, filtered and aggregated for more in-depth analysis and monitoring.

[0029] The environment variable configuration information defines the environment variables related to the operation of the probe. These environment variables may be used to specify the behavior, connection parameters, authentication information, etc. of the probe. For example, the environment variable information is the host name of the server, the host IP, or the network address and port that the probe listens on, and the data source name (DSN) used to connect to the MySQL database, which includes the database user name, password, host name, port, and database name.

[0030] Specifically, the user can edit one or more of the above-mentioned indicator configuration information, label configuration information and environment variable configuration information through the UI interface module 110. The UI interface module 110 receives the user's input information and passes the information to the configuration service module 120, thereby forming the indicator collection configuration information. Furthermore, the above-mentioned several configuration information can also be read from other configuration files. The configuration service module generates the indicator collection configuration information based on this information and publishes the configuration information.

[0031] There can be multiple indicator collection configuration information. After the indicator collection configuration information is generated, a user can receive a publishing instruction for one or more generated indicator collection configuration information, and determine which indicator collection configuration information needs to be published according to the publishing instruction. The publishing method can be pushed to the client or actively pulled by the client.

[0032] In one embodiment, when the environment variable value in the environment variable configuration information is a null value, a corresponding default value is used to replace the null value.

[0033] In this embodiment, the environment variable configuration information usually configures the value of one or more environment variables. When the environment variable configuration is performed, if the environment variable value is not set for each configured environment variable, that is, the indicator collection configuration information generation instruction is triggered, the server can detect whether each environment variable configured in the environment variable configuration information has a corresponding variable value set. When a specific variable value is not set for one or more environment variables, that is, when the value is empty, the server can fill the empty value according to the system default value. By replacing the environment variables that have not been set with variable values ​​with default values, the successful generation of the indicator collection configuration information is ensured.

[0034] The client includes a synchronization service module 210 , an execution module 220 , and a storage module 230 .

[0035] The synchronization service module 210 is used to actively pull the published indicator collection configuration information from the configuration service module 120, and store the indicator collection configuration information in the storage module 230. The execution module 220 executes the stored indicator collection configuration information to generate corresponding indicator data, and the storage module 230 further stores the indicator data.

[0036] Specifically, the execution module is also used to call the probe, execute the indicator collection configuration information according to the execution cycle and environment variable configuration information in the indicator collection configuration information, and convert the output data after execution so that the generated indicator data can be identified by Prometheus.

[0037] It is understandable that for these indicators that need to be collected, the collection is usually not completed only once, but will be repeated regularly and continuously to achieve real-time monitoring of the indicator. For different indicators, the corresponding execution cycle may be different. For example, for some indicators, the preset execution cycle may be executed once every 30 seconds, once every 35 seconds, or once every 1 minute, etc.

[0038] Optionally, the execution cycle of the indicator can be set in the corresponding indicator collection configuration information, and the corresponding execution cycle can be pre-configured therein before the indicator collection configuration information is generated. In addition, the service module 120 can also be configured to uniformly set a matching execution cycle for each indicator to form an indicator execution cycle table. The execution cycle corresponding to each different indicator can be set in the indicator execution cycle table. When the configured execution cycle does not exist in the indicator collection configuration information, the execution cycle corresponding to the executed indicator can be queried from the execution cycle table. If the corresponding execution cycle is not set in the indicator execution cycle table, it is executed according to the default execution cycle. For example, the default execution cycle can be set to execute once every 30 seconds. Among them, the indicator execution cycle table can be stored in the storage module 230 of each client, and can be obtained from the server through the synchronization service module 210.

[0039] The execution module is further used to call the probe to execute the indicator collection configuration information according to a preset scheduling period, and the execution period is an integer multiple of the scheduling period.

[0040] Among them, the scheduling cycle of the execution module is the minimum execution scheduling cycle. According to the scheduling cycle, each indicator collection configuration information to be executed in the storage module is regularly scanned, and it is determined whether the corresponding indicator collection configuration information needs to be executed at the current moment. If it needs to be executed, the environment variable information in the corresponding indicator configuration information will be input and the corresponding indicator collection configuration information will be executed.

[0041] Optionally, each indicator collection configuration information and the preset default execution period can be an integer multiple of the minimum execution scheduling period. For example, the minimum execution scheduling period and the default execution period are both 30 seconds.

[0042] In one embodiment, when there is a conflict between the execution cycle configured in the indicator collection configuration information and the corresponding execution cycle in the indicator execution cycle table, the execution is performed periodically according to the execution cycle configured in the indicator collection configuration information.

[0043] The execution module converts the indicator data (intermediate indicator data) output by the execution indicator collection configuration information into Prometheus indicator data using the parsing tool expfmt.TextParser in Prometheus, and finally writes it into the storage module, thus completing the scheduling. The time period for writing the indicator data into the storage module is the scheduling time interval of the indicator collection configuration information.

[0044] With respect to the stored indicator data, the data collection module 130 of the server side may obtain the indicator data stored in the storage module according to a preset collection frequency, so as to analyze the indicator data.

[0045] In one embodiment, the indicator data collected by the data collection module 130 may be the indicator intermediate data directly output by the execution module and not converted. For this data, the server may also call expfmt.TextParser to convert it into the indicator data of Prometheus, thereby obtaining the indicator data that can be analyzed and used.

[0046] In one embodiment, the storage module specifically includes a file storage unit and a cache unit. Among them, the indicator collection configuration information and the indicator execution period table synchronized from the server are stored in the file storage unit, and the generated indicator data is stored in the cache unit. In this way, when the server collects indicator data from the cache unit, it will not affect the data stored in the file storage unit.

[0047] The processing system for collecting indicator data by the probe in Prometheus in this application is used to expand the function of the probe Exporter customized by the Prometheus system by building a unified platform framework. It allows users to write and configure parameters such as indicators, tags, and environment variables, thereby realizing the monitoring and collection configuration of indicator data, and improving the flexibility of indicator data configuration. And by setting up a synchronization service module on the server side, users can publish indicator collection configuration information to specified clients, thereby realizing the rapid expansion of monitoring indicators. Users only need to focus on writing scripts for data collection. Since the system can automatically publish these scripts, the complexity of manually upgrading the collection code is eliminated. In addition, because the scripts are called by the platform itself, users do not need to schedule these scripts by themselves, which greatly improves the efficiency of monitoring expansion in a cluster environment.

[0048] In addition, the client actively synchronizes the published indicator collection configuration information, so that scripts can be remotely configured and executed on the client, so that the indicators being collected can be dynamically updated and upgraded without restarting the application.

[0049] In one embodiment, the storage module is further used to expose the stored indicator data to the outside according to a pre-registered unified port; the data collection module is further used to call the unified port to obtain the exposed indicator data.

[0050] In this embodiment, each client pre-sets a separate port for providing to the server to collect indicator data. In this way, when the server collects indicator data from each client, it only needs to call the corresponding port to obtain the indicator data updated and generated by the client. Among them, the unified port can be, for example, port 9090 using the HTTP protocol, and the unified port is used to expose the stored indicator data to the external system in the Prometheus format. When the external system (server) needs to obtain indicator data, they only need to send a request to the unified port to realize the collection of the indicator data. Among them, the ports used by each client can be the same port or different ports.

[0051] Compared with the traditional multi-port, multi-protocol solution, this solution has the following advantages: Simplified configuration: Administrators only need to configure one port to access all indicator data. There is no need to configure a port for each data source or application separately, which reduces the configuration of the collected endpoints.

[0052] Reduced risk: Reduced system reliance on ports reduces the risk of problems due to port conflicts or misconfigurations.

[0053] Easy to integrate: For external systems that use tools such as Prometheus, only one port is needed to easily integrate the indicator data of this system.

[0054] Easy to manage: Using a unified port can reduce the workload of system management and maintenance, and improve system reliability and availability.

[0055] In one embodiment, the configuration service module is also used to generate a version number for the indicator collection configuration information, and associate the version number with one or more client identifiers in the client list; the synchronization service module is also used to synchronize the published indicator collection configuration information from the configuration service module according to the client identifier.

[0056] In this embodiment, each indicator collection configuration information is set with a corresponding version number. When the published indicator collection configuration information is modified and published, a version number different from the version number before the modification will be generated for the modified indicator collection configuration information, so that the specific version of the indicator collection configuration information can be known according to the version number. It can be understood that the content of the indicator collection configuration information corresponding to different version numbers is different.

[0057] For each client connected to the server, the server can record the client ID of the corresponding client and store the client ID in the corresponding client list, and the client ID is used to uniquely identify the corresponding client. The client ID in the client list can be automatically collected and updated after the client connects to the server, or can be actively entered or modified by the user.

[0058] Specifically, the synchronization service module is further used to obtain the client identifier of the client according to the connection between the client and the server, and maintain the client list based on the obtained client identifier.

[0059] For the indicator collection configuration information to be released, after the version number is generated, the server can receive the user's selection of at least one version number and at least one client identifier through the UI interface module, and in response to the triggered version number and client identifier association instruction, associate the selected version number with the client identifier based on the association instruction. The client identifier and version number with an associated relationship indicate that the corresponding client needs to execute the indicator collection configuration information corresponding to the version number.

[0060] Optionally, before synchronizing the indicator collection configuration information from the server, the client's synchronization module queries the client list for the version number associated with its own client identifier, and then obtains the indicator collection configuration information of the corresponding version number, thereby avoiding obtaining indicator collection configuration information that does not need to be called for execution.

[0061] In one embodiment, the configuration service module is also used to generate a corresponding version number when the indicator configuration information and label configuration information are created, obtain a selection instruction for the client identifier, trigger an indicator collection configuration information release instruction based on the selection instruction, and write the indicator collection configuration information, the selected client identifier and the version number into a version release table.

[0062] In this embodiment, when it is detected that both the indicator configuration information and the label configuration information are created, a corresponding version number can be generated, and the environment variable configuration information can be configured before or after the version number is generated.

[0063] After the version number is created, when the indicator collection configuration information is published, it is detected whether the variable value in the environment variable configuration information is empty. If it exists, it is replaced with the corresponding default value, and the indicator collection configuration information is generated and published. When publishing, the user is further received to establish an association relationship between the version number and the client, so as to associate the client identifier selected by the user with the version number, and write the associated client identifier and version number into the version release table.

[0064] The version release table is used to store each associated client identifier and version number.

[0065] Before synchronizing the indicator collection configuration information, the client first queries the version number corresponding to its own client identifier from the version release table, and obtains the corresponding indicator collection configuration information according to the version number.

[0066] Specifically, the synchronization service module is also used to query the target version number associated with the client's own client identifier from the version release table, and detect whether the target version number is consistent with the version number present in the storage module. If inconsistent, obtain the indicator collection configuration information corresponding to the target version number, and delete the indicator collection configuration information corresponding to the inconsistent version number.

[0067] Among them, the client itself has already obtained the indicator collection configuration information from the server before the current synchronization time, and stored the version number of the corresponding synchronized indicator collection configuration information. Therefore, when starting the synchronization configuration this time, first obtain all the target version numbers (i.e., the target version number set) associated with its own client identifier from the version release table of the server. Compare the target version number with the existing version number of the stored indicator collection configuration information to detect whether the two are consistent. If they are completely consistent, there is no need to synchronize the indicator collection configuration information therein, so that the saved indicator collection configuration information can be executed according to the update frequency. Among them, completely consistent means that the stored existing version number set is exactly the same as the version number in the target version number set. For example, the difference set of the two can be calculated, and the difference set of the two is empty. If the difference set is not empty, it means that the two are inconsistent. At this time, if there are one or more first version numbers in the difference set that belong to the existing version number set (that is, the version number that is inconsistent with the target version number), the indicator collection configuration information corresponding to the first version number stored locally will be deleted; if there are one or more second version numbers in the difference set that belong to the target version number set, the indicator collection configuration information corresponding to the second version number will be synchronized from the server, and the configuration information will be saved in the target collection storage module.

[0068] Among them, after the synchronization of the indicator collection configuration information is completed, the synchronized target version number becomes the existing version number, and the client updates its own saved set of existing version numbers for recycling during the next synchronization.

[0069] The client can synchronize the indicator collection configuration information cyclically according to a predetermined synchronization cycle. The duration of the synchronization cycle can be the same as the above-mentioned scheduling cycle, or the duration of the scheduling cycle is an integer multiple of the synchronization cycle. For example, the duration of the synchronization cycle is 10 seconds, that is, the synchronization of the indicator collection configuration information is performed once every 10 seconds. By cyclically synchronizing the indicator collection information, the client can obtain the indicator collection configuration information in a timely and smooth manner.

[0070] Although example embodiments have been described, it will be apparent to those skilled in the art that various changes and modifications may be made without departing from the spirit and scope of the inventive concept. Therefore, it should be understood that the above example embodiments are not restrictive, but illustrative.

Claims

1. A processing system for collecting indicator data based on probes in Prometheus, characterized in that: The system comprises: a server and at least one client connected to the server via a network, the server comprising a configuration service module and a data acquisition module, the client comprising a synchronization service module, an execution module, and a storage module; The configuration service module is used to obtain indicator configuration information, label configuration information and environment variable configuration information, generate indicator collection configuration information based on the indicator configuration information, label configuration information and environment variable configuration information, and publish the indicator collection configuration information; The synchronization service module is used to synchronize the published indicator collection configuration information from the configuration service module; The execution module is used to call the probe to execute the indicator collection configuration information and generate corresponding indicator data; The storage module is used to store the synchronized indicator collection configuration information and the indicator data; The data acquisition module is used to obtain the indicator data from the storage module.

2. The system according to claim 1, characterized in that The execution module is also used to call the probe, execute the indicator collection configuration information according to the execution cycle and environment variable configuration information in the indicator collection configuration information, and convert the output data after execution so that the generated indicator data is the indicator data recognized by Prometheus.

3. The system according to claim 1, characterized in that The storage module is also used to expose the stored indicator data to the outside according to a pre-registered unified port; The data collection module is also used to call the unified port to obtain the exposed indicator data.

4. The system according to claim 1, characterized in that The configuration service module is further used to generate a version number for the indicator collection configuration information, and associate the version number with one or more client identifiers in the client list; The synchronization service module is further used to synchronize the published indicator collection configuration information from the configuration service module according to the client identifier.

5. The system according to claim 4, characterized in that The synchronization service module is further used to obtain a client identifier of the client according to the connection between the client and the server, and maintain the client list based on the obtained client identifier.

6. The system according to claim 4, characterized in that The storage module is also used to update the stored indicator collection configuration information according to the version number, and delete the indicator collection configuration information with a version number inconsistent with that published in the configuration service module.

7. The system according to claim 4, characterized in that The configuration service module is also used to generate a corresponding version number when the indicator configuration information and label configuration information are created, obtain a selection instruction for the client identifier, trigger an indicator collection configuration information release instruction based on the selection instruction, and write the indicator collection configuration information, the selected client identifier and the version number into a version release table.

8. The system according to claim 7, characterized in that The synchronization service module is also used to query the target version number associated with the client's own client identifier from the version release table, and detect whether the target version number is consistent with the version number present in the storage module. If inconsistent, obtain the indicator collection configuration information corresponding to the target version number, and delete the indicator collection configuration information corresponding to the inconsistent version number.

9. The system according to claim 2, characterized in that The execution module is further used to call the probe to execute the indicator collection configuration information according to a preset scheduling period, and the execution period is an integer multiple of the scheduling period.

10. The system according to claim 1, characterized in that When the environment variable value in the environment variable configuration information is a null value, a corresponding default value is used to replace the null value.

Citation Information

Patent Citations

  • Method of pushing and receiving configuration information, server and client

    CN106487842A

  • Index acquisition method, index acquisition system and computing equipment

    CN116431434A

  • Distributed index acquisition method and acquisition system for heterogeneous database and server

    CN116680150A

  • Application index monitoring method and device, computer equipment and computer readable storage medium

    CN117539714A