Monitoring index acquisition method, device and system, electronic equipment and readable storage medium
By configuring the database and backend components to automatically deploy the indicator collection components, the problem of time-consuming and labor-intensive manual configuration is solved, achieving efficient and real-time monitoring indicator collection and reducing the risk of data loss.
Patent Information
- Application Number
- CN202411025961.8
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-07-29
- Publication Date
- 2024-11-15
AI Technical Summary
Existing methods for collecting monitoring metrics rely on manual configuration and deployment, resulting in high manpower consumption, long time consumption, inability to achieve real-time metric collection, and easy loss of metric data.
By configuring a database to store information about monitored objects and metric collection components, the metric collection components are automatically deployed using a backend component deployment device, and Prometheus collects monitoring metrics, thus achieving an automated metric collection process.
Significantly reduce manpower and time costs, improve the efficiency of indicator collection, reduce the possibility of indicator data loss, and ensure real-time monitoring of indicator collection.
Smart Images

Figure CN118964158A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of electronic information, and in particular to a monitoring indicator collection method and device, a system, an electronic device, and a readable storage medium. Background Art
[0002] System observability is crucial to ensuring system stability, performance optimization, and troubleshooting. By monitoring and collecting key indicators, we can understand the operating status of the system in real time, discover potential problems in advance, and make corresponding optimizations and adjustments.
[0003] Currently, a common method to achieve observability is to collect various monitoring indicators. Taking the business system used by the enterprise as an example, the monitoring indicators may include system resource usage indicators, application performance indicators, and network traffic statistics indicators. By monitoring and analyzing these indicators, the enterprise can obtain information about the system operation status and performance, and take timely measures to ensure the stability and reliability of the system.
[0004] There is still room for improvement in the current monitoring indicator collection function. Summary of the invention
[0005] The present application provides a monitoring indicator collection method and device, a system, an electronic device, and a readable storage medium, the purpose of which is to solve the problem of how to improve the monitoring indicator collection function.
[0006] In order to achieve the above objectives, this application provides the following technical solutions:
[0007] The first aspect of the present application provides a monitoring indicator collection method, comprising:
[0008] Query configuration information, the configuration information including: information of the monitored object and information of the indicator collection component corresponding to the monitored object;
[0009] Based on the configuration information, an indicator collection component is deployed in the monitored object, and the indicator collection component is used to collect indicators of the monitored object.
[0010] A second aspect of the present application provides a monitoring indicator collection application, including:
[0011] The back-end component deployment device is used to implement the indicator collection method provided in the first aspect of this application.
[0012] The third aspect of the present application provides a monitoring indicator collection system, including:
[0013] A configuration database, used to store configuration information, the configuration information including: information of a monitored object and information of an indicator collection component corresponding to the monitored object;
[0014] The second aspect of this application provides an indicator collection application;
[0015] A collection device is used to collect the indicators of the monitored object based on the indicator collection component deployed by the indicator collection application.
[0016] A fourth aspect of the present application provides an electronic device, including:
[0017] Memory and processor;
[0018] The memory is used to store a computer program, and the processor is used to run the computer program to implement the monitoring indicator collection method provided in the first aspect of the present application.
[0019] The fifth aspect of the present application provides a readable storage medium. When the instructions in the readable storage medium are executed by a processor of an electronic device, the electronic device can execute the monitoring indicator collection method provided by the first aspect of the present application.
[0020] The sixth aspect of the present application provides a computer program product, including a computer program / instruction, which, when executed by a processor, implements the monitoring indicator collection method provided in the first aspect of the present application.
[0021] The monitoring indicator collection function method and device, system, electronic device, and readable storage medium provided in the present application automatically deploy indicator collection components in the monitored object based on configuration information, which can not only reduce manpower consumption, but also improve indicator collection efficiency and reduce the possibility of indicator omission, thereby achieving effective improvement in the monitoring indicator collection function. BRIEF DESCRIPTION OF THE DRAWINGS
[0022] The above and other features, advantages and aspects of the embodiments of the present disclosure will become more apparent with reference to the following detailed description in conjunction with the accompanying drawings. Throughout the accompanying drawings, the same or similar reference numerals represent the same or similar elements. It should be understood that the drawings are schematic and the originals and elements are not necessarily drawn to scale.
[0023] Figure 1 A schematic diagram of the indicator collection process that relies on manually deployed indicator collection components;
[0024] Figure 2 A schematic diagram of the structure of a monitoring indicator collection system provided in an embodiment of the present application;
[0025] Figure 3 A flowchart of a monitoring indicator collection method provided in an embodiment of the present application;
[0026] Figure 4 A flowchart of another monitoring indicator collection method provided in an embodiment of the present application;
[0027] Figure 5 A flowchart of another monitoring indicator collection method provided in an embodiment of the present application;
[0028] Figure 6 A flowchart of a query monitoring indicator collection task provided in an embodiment of the present application;
[0029] Figure 7 A flowchart of another query monitoring indicator collection task provided in an embodiment of the present application;
[0030] Figure 8 A flowchart of redeploying an unhealthy indicator collection task provided by an embodiment of the present application;
[0031] Fig. 9 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION
[0032] Embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. Although certain embodiments of the present disclosure are shown in the accompanying drawings, it should be understood that the present disclosure can be implemented in various forms and should not be construed as being limited to the embodiments described herein, which are instead provided for a more thorough and complete understanding of the present disclosure. It should be understood that the drawings and embodiments of the present disclosure are only for exemplary purposes and are not intended to limit the scope of protection of the present disclosure.
[0033] The term "including" and its variations used herein are open inclusions, i.e., "including but not limited to". The term "based on" means "based at least in part on". The term "one embodiment" means "at least one embodiment"; the term "another embodiment" means "at least one additional embodiment"; the term "some embodiments" means "at least some embodiments". The relevant definitions of other terms will be given in the following description.
[0034] It should be noted that the concepts such as "first" and "second" mentioned in the present disclosure are only used to distinguish different devices, modules or units, and are not used to limit the order or interdependence of the functions performed by these devices, modules or units.
[0035] It should be noted that the modifications of "one" and "plurality" mentioned in the present disclosure are illustrative rather than restrictive, and those skilled in the art should understand that unless otherwise clearly indicated in the context, it should be understood as "one or more".
[0036] Figure 1 It is a collection process of monitoring indicators. Figure 1 The following steps are included:
[0037] 1. Manually configure the indicator collection file to obtain the indicator collection configuration file.
[0038] 2. Manually deploy indicator collection components.
[0039] Figure 1 In the example, the monitoring objects include hosts, applications and middleware. Different objects to be collected need to be configured with matching indicator collection components.
[0040] exist Figure 1 In the process shown, the indicator collection component relies on manual deployment.
[0041] After completing the above configuration, perform the following indicator collection steps.
[0042] 3. Prometheus reads the indicator collection configuration information from the indicator collection configuration file.
[0043] Prometheus is a widely used indicator collection solution. Prometheus provides a flexible and scalable way to collect various monitoring indicators and provides powerful query and alarm functions.
[0044] 4. Prometheus collects indicators from various indicator collection components based on indicator collection configuration information.
[0045] from Figure 1 It can be seen that the indicator collection components of various monitoring objects rely on manual configuration. The inventors found in the process of research that not only in the initial configuration stage, it is necessary to manually configure the indicator collection components in each monitoring object one by one, but also when the monitoring objects in the system change, such as adding new monitoring objects or updating existing monitoring objects, it is also necessary to manually configure the indicator collection components for the changed monitoring objects.
[0046] Therefore, not only does it require a lot of manpower, but more importantly, manual deployment takes a long time and cannot achieve real-time indicator collection, which may result in the loss of indicator data.
[0047] So, Figure 1 There is still room for improvement in the indicator collection process for example.
[0048] Figure 2 A monitoring indicator collection system disclosed in an embodiment of the present application includes: a configuration database, an indicator collection application, and a collection device.
[0049] The configuration database is used to store configuration information, which includes information about monitoring objects in the system and information about indicator collection components corresponding to each monitoring object.
[0050] The operation and maintenance personnel store the configuration information in the configuration database. In some implementations, the configuration information includes fields and field values. An example of the configuration information is shown in Table 1.
[0051] Table 1
[0052] Field Name Field Value Resource Type Host / Application / Middleware Host IP 10.0.0.1 Application Name microservice-gateway Environment Development / Testing / Production Is it necessary to collect indicators? yes Metrics Collection Protocol http / https Index collection port 9100 Indicator collection path / metrics Resource Status Running / Stopped Host authentication information <Username> / <Password> Middleware authentication information <Username> / <Password>
[0053] Among them, taking the monitoring object as a host as an example, the resource type, host IP, and the environment to which it belongs are examples of information of the monitoring object, and the indicator collection protocol, indicator collection port, and indicator collection path are examples of information of the indicator collection component.
[0054] In some implementations, the configuration database is a Configuration Management Database (CMDB).
[0055] The indicator collection application includes a front-end page and a back-end component deployment device. The front-end page provides display and query functions, which will be explained in conjunction with subsequent processes.
[0056] The back-end component deployment device communicates with the configuration database through a corresponding interface. The back-end component deployment device reads the configuration information in the configuration database through the interface, and deploys the indicator collection component in the monitoring object based on the configuration information.
[0057] The collection device is used to collect indicators based on the indicator collection components in each monitoring object. In some implementations, the collection device is Prometheus.
[0058] The functions described above herein may be performed at least in part by one or more hardware logic components. For example, without limitation, exemplary types of hardware logic components that may be used include: field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), systems on chips (SOCs), complex programmable logic devices (CPLDs), and the like.
[0059] Figure 3 for Figure 2 The example diagram of the process of monitoring indicator collection by the monitoring indicator collection system shown in the figure assumes that the information of the host, application, middleware and the corresponding indicator collection component has been pre-configured in the CMDB. Taking Table 1 as an example, in this case, the following steps are performed:
[0060] S31. The backend component deployment device reads the configuration information in the configuration database at a preset period, and deploys the indicator collection component to each monitoring object based on the configuration information.
[0061] After reading the configuration information in the configuration database, the backend component deployment device also converts the configuration information into indicator collection task information. The indicator collection task information converted based on Table 1 is taken as an example in Table 2.
[0062] Table 2
[0063]
[0064]
[0065] S32. Prometheus periodically queries the indicator collection task information from the backend component deployment device and automatically generates the local indicator collection configuration.
[0066] S33. Prometheus collects monitoring indicators (referred to as collection indicators for short) from each indicator collection component based on the indicator collection task information.
[0067] Combination Figure 2 and Figure 3 It can be seen that the monitoring indicator collection system and method provided by the present application automatically deploys the indicator collection components to each monitoring object by the back-end component deployment device, thereby saving a lot of manpower, deployment time and labor costs.
[0068] And, correspondingly, the back-end component deployment device also provides the collection device with indicator collection task information, which is conducive to further improving the indicator collection efficiency.
[0069] The following will Figure 2 The monitoring indicator collection process implemented by the monitoring indicator collection system shown is described in more detail.
[0070] Figure 4 Another monitoring indicator collection process disclosed in the embodiment of the present application, it can be understood that the configuration information has been stored in the CMDB, that is, the CMDB has the function of providing deployment information of the host, application and middleware.
[0071] Figure 4 The following steps are included:
[0072] S41. The backend component deployment device queries the CMDB for configuration information of the host, application and middleware regularly through interface calls, and records the query results.
[0073] In some implementations, the timed query is performed at a preset query period.
[0074] S42. The backend component deployment device deploys the indicator collection component to each monitoring object based on the configuration information.
[0075] In this embodiment, deploying the indicator collection component specifically includes the following steps:
[0076] S421. Determine the type of the monitored object.
[0077] If the monitored object type is a host, execute S422-S423.
[0078] If the monitored object type is application, execute S424-S426.
[0079] If the monitored object type is middleware, execute S427-S429.
[0080] S422. The backend component deployment device uploads the host indicator collection component to the host that is the monitored object.
[0081] S423. The backend component deployment device starts the host indicator collection component.
[0082] S424. The backend component deployment device uploads the application indicator collection component to the host where the application to be monitored is located.
[0083] S425. The backend component deployment device configures startup parameters related to the application indicator collection component to the application.
[0084] It is understandable that after configuring the indicator collection component in the application, the application startup parameters need to be reconfigured, and the reconfigured application startup parameters are related to the indicator collection component deployed in the application (ie, the application indicator collection component).
[0085] For example, the startup parameters of the original application are: java-jar app.jar. After the indicator collection component is deployed, the startup parameters of the application should be modified to (app-javaagent.jar is the indicator collection component): java-jar-javaagent:app-javaagent.jar app.jar.
[0086] S426. The backend component deployment device starts or restarts the application for the first time.
[0087] S427: The backend component deployment device uploads the middleware indicator collection component to the host where the middleware to be monitored is located.
[0088] S428. The backend component deployment device configures the middleware connection and authentication information.
[0089] S429. The backend component deployment device starts the middleware indicator collection component.
[0090] It can be seen that the backend component deployment device automatically deploys the indicator collection component for each monitoring object based on the type of monitoring object obtained from the configuration information, without manually configuring the indicator collection component one by one. It can be understood that the deployment method described in this embodiment is a non-invasive deployment, that is, there is no need to perform an intrusive operation on the host.
[0091] After completing the deployment process of the indicator collection component, proceed to the next step.
[0092] S43. The backend component deployment device determines whether the deployment is successful. If yes, execute S45 and subsequent steps. If not, execute S44.
[0093] In some implementations, the backend component deployment device determines whether the deployment is successful by periodically querying the deployment results in the deployment log.
[0094] S44. The backend component deployment device issues an alarm notification.
[0095] The alarm notification includes the cause of the error. The deployment log generated in the case of deployment failure includes the cause of the error. In some implementations, when it is determined that the deployment has failed, the cause of the error is extracted from the deployment log. An example of the cause of the error is "there is currently no operation permission for the host." In some implementations, the subsequent component deployment device transmits the alarm notification to the front-end page, and the front-end page displays the alarm notification.
[0096] Alarm notifications are helpful for operation and maintenance personnel to intervene and make improvements to ensure that the indicator collection component can be successfully deployed on the monitored object so that the monitoring indicators can be collected.
[0097] S45. The backend component deployment device generates indicator collection task information based on the configuration information.
[0098] S46. Prometheus periodically queries the indicator collection task information from the backend component deployment device.
[0099] In some implementations, Prometheus implements the query of indicator collection task information by periodically calling the interface of the backend component deployment device. The periodic query can be understood as querying at a preset query cycle.
[0100] S47. Prometheus generates local indicator collection configuration based on indicator collection task information.
[0101] S48, Prometheus collects monitoring indicators from various indicator collection components based on local indicator collection configuration.
[0102] from Figure 4 As can be seen from the process shown, personnel can automatically deploy different indicator collection components and configure Prometheus indicator collection based on the host, application, and middleware deployment information maintained by CMDB, thereby greatly reducing the operation and maintenance workload while ensuring the quality of operation and maintenance.
[0103] Figure 5 Another monitoring indicator collection method disclosed in the embodiment of the present application is Figure 4The difference compared to the process shown in the figure is that it highlights the automatic deployment and collection process after the configuration information is changed.
[0104] Figure 5 The following steps are included:
[0105] S51. CMDB receives updated configuration information.
[0106] The updated configuration information includes at least one of configuration information of a host, an application, and middleware.
[0107] S52. The backend component deployment device queries the CMDB for deployment information of the host, application and middleware regularly through interface calls, and records the query results.
[0108] S53. The backend component deployment device calculates the changed configuration information based on the uploaded query result and the current query result.
[0109] The calculated changed configuration information may be understood as incremental configuration information. That is, in order to save resources, the indicator collection component may be redeployed based only on the incremental configuration information, ie, the changed configuration information.
[0110] S54. The backend component deployment device deploys the indicator collection component to the monitored object based on the changed configuration information.
[0111] It is understandable that if the configuration information of a monitored object is not updated, there is no need to repeatedly deploy the indicator collection component in order to save resources.
[0112] If the configuration information of a monitored object is updated, that is, the updated configuration information includes the configuration information of the first monitored object, the indicator collection component is redeployed to the first monitored object. The specific deployment method can be found in S421-S429, which will not be repeated here.
[0113] S55. The backend component deployment device determines whether the deployment is successful. If yes, execute S57 and subsequent steps. If not, execute S56.
[0114] S56. The backend component deployment device issues an alarm notification.
[0115] S57, Prometheus periodically queries the indicator collection task information from the backend component deployment device.
[0116] S58. Prometheus generates local indicator collection configuration based on indicator collection task information.
[0117] S59, Prometheus collects monitoring indicators from various indicator collection components based on local indicator collection configuration.
[0118] from Figure 5 It can be seen from the process shown that when personnel update the configuration information, the indicator collection component can be automatically redeployed based on the updated configuration information, without the need for personnel to modify the configured indicator collection components one by one. This can not only reduce the operation and maintenance workload to ensure the quality of operation and maintenance, but also greatly reduce the time for reconfiguring the indicator collection component, which is conducive to the continuous collection of real-time indicators and reduces the possibility of indicator data loss.
[0119] Figure 6 The process of querying indicator collection data for users based on indicator collection applications includes the following steps:
[0120] S61. The front-end page receives an operation of querying the number of indicator collection tasks.
[0121] In some implementations, the front-end page displays an indicator collection task data query button, and the user clicks the indicator collection task data query button to query the number of indicator collection tasks.
[0122] S62. The front-end page sends an indicator collection task number query message (referred to as data query message) to the back-end component deployment device.
[0123] S63. The backend component deployment device calls Prometheus to query the number of indicator collection tasks.
[0124] In some implementations, the indicator collection task number query message indicates querying the number of indicator collection tasks in different states. Different states include healthy states and unhealthy states. A healthy state is a state in which monitoring indicators can be collected normally, and an unhealthy state is a state in which monitoring indicators cannot be collected normally.
[0125] S64. Prometheus queries the number of indicator collection tasks, and the backend component deployment device sends the number of indicator collection tasks.
[0126] In some implementations, the number of indicator collection tasks includes the number of healthy and unhealthy indicator collection tasks.
[0127] S65. The backend component deployment device sends the number of indicator collection tasks to the frontend page.
[0128] S66. The front-end interface displays the number of indicator collection tasks.
[0129] In addition to being able to provide a query function for the number of indicator collection tasks, the indicator collection application can also provide a query function for the health of the indicator collection tasks.
[0130] The health of the indicator collection task indicates whether the indicator collection task can successfully collect the indicator. If it can be successfully collected, the task is healthy, and if it cannot be successfully collected, the task is unhealthy. In some implementations, the health is a first value or a second value, the first value indicates that the indicator collection task is successful, and the second value indicates that the indicator collection task is unsuccessful. In other implementations, the health is a value indicating the probability of success of the indicator collection task.
[0131] The process of querying the health of the indicator collection task is similar to the process of querying the number of indicator collection tasks, such as Figure 7 As shown, no further description is given here.
[0132] In addition to being able to perform queries in response to user query operations, the indicator collection application can also provide an automatic scheduled query function to redeploy unhealthy indicator collection tasks.
[0133] Figure 8 The process of querying and redeploying unhealthy indicator collection tasks for the indicator collection application includes the following steps:
[0134] S81. The backend component deployment device periodically queries Prometheus for information about unhealthy indicator collection tasks.
[0135] S82. The backend component deployment device redeploys the indicator collection component for the unhealthy indicator collection task.
[0136] It is understandable that in case of unsuccessful deployment, the backend component deployment device issues an alarm notification.
[0137] From the above process, it can be seen that the indicator collection application provided by this application can not only automatically deploy indicator collection components to the monitored objects, but also provide queries for indicator collection tasks, and, when the indicator collection tasks are unhealthy, redeploy the indicator collection components to ensure the successful collection of monitoring indicators.
[0138] The flow chart and block diagram in the accompanying drawings illustrate the possible architecture, function and operation of the system, method and computer program product according to various embodiments of the present disclosure. In this regard, each square box in the flow chart or block diagram can represent a module, a program segment or a part of a code, and the module, the program segment or a part of the code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some implementations as replacements, the functions marked in the square box can also occur in a sequence different from that marked in the accompanying drawings. For example, two square boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each square box in the block diagram and / or flow chart, and the combination of the square boxes in the block diagram and / or flow chart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.
[0139] The names of the messages or information exchanged between multiple devices in the embodiments of the present disclosure are only used for illustrative purposes and are not used to limit the scope of these messages or information.
[0140] Although operations are depicted in a particular order, this should not be understood as requiring that the operations be performed in the particular order shown or in a sequential order.Multitasking and parallel processing may be advantageous under certain circumstances.
[0141] It should be understood that the various steps described in the method embodiments of the present disclosure may be performed in different orders and / or in parallel. In addition, the method embodiments may include additional steps and / or omit the steps shown. The scope of the present disclosure is not limited in this respect.
[0142] Computer program code for performing the operations of the present disclosure may be written in one or more programming languages or a combination thereof, including, but not limited to, object-oriented programming languages, such as Java, Smalltalk, C++, and conventional procedural programming languages, such as "C" or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, as a separate software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving a remote computer, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., through the Internet using an Internet service provider).
[0143] An embodiment of the present application further discloses an electronic device, including: a memory and a processor.
[0144] The memory is used to store a computer program, and the processor is used to run the computer program to implement the above Figure 3-Figure 8 The process shown is used as an example of a method for collecting monitoring indicators.
[0145] It is understandable that the electronic device may be a server. Fig. 9 For example, in addition to a memory and a processor, an electronic device also includes an input device such as a keyboard, an output device such as a display, and a communication module. The input device, the output device, and the communication module communicate with the processor through an I / O interface (i.e., an input / output interface).
[0146] The embodiment of the present application also discloses a readable storage medium. When the instructions in the readable storage medium are executed by the processor of the electronic device, the electronic device can execute the following Figure 3-Figure 8 The monitoring indicator collection method shown in the figure.
[0147] In the context of the present disclosure, a readable storage medium may be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, device, or equipment. A readable storage medium may be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, device, or equipment, or any suitable combination of the foregoing. A more specific example of a machine-readable storage medium may include an electrical connection based on one or more lines, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
[0148] It should be noted that the above-mentioned readable medium of the present disclosure may be a computer-readable signal medium or a computer-readable storage medium or any combination of the above two. The computer-readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present disclosure, a computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in combination with an instruction execution system, device or device. In the present disclosure, a computer-readable signal medium may include a data signal propagated in a baseband or as part of a carrier wave, in which a computer-readable program code is carried. This propagated data signal may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. The computer readable signal medium may also be any computer readable medium other than a computer readable storage medium, which may send, propagate or transmit a program for use by or in conjunction with an instruction execution system, apparatus or device. The program code contained on the computer readable medium may be transmitted using any suitable medium, including but not limited to: wires, optical cables, RF (radio frequency), etc., or any suitable combination of the above. The above computer readable medium may be contained in the above electronic device; or it may exist alone without being assembled into the electronic device.
[0149] In particular, according to an embodiment of the present disclosure, the process described above with reference to the flowchart can be implemented as a computer software program. For example, an embodiment of the present disclosure includes a computer program product, which includes a computer program carried on a non-transitory computer-readable medium, and the computer program contains a program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from a network through a communication device, or installed from a storage device, or installed from a ROM. When the computer program is executed by a processing device, the above-mentioned functions defined in the method of the embodiment of the present disclosure are executed.
[0150] According to one or more embodiments of the present application, the present application discloses a monitoring indicator collection method, including:
[0151] Query configuration information, the configuration information including: information of the monitored object and information of the indicator collection component corresponding to the monitored object;
[0152] Based on the configuration information, an indicator collection component is deployed in the monitored object, and the indicator collection component is used to collect indicators of the monitored object.
[0153] In some implementations, deploying an indicator collection component in the monitored object based on the configuration information includes:
[0154] Based on the type of the monitored object indicated by the configuration information, an indicator collection component is deployed in the monitored object.
[0155] In some implementations, the deploying of an indicator collection component in the monitored object based on the type of the monitored object indicated by the configuration information includes at least one of the following methods:
[0156] The monitoring object type is a host, uploading a host indicator collection component to the host as the monitoring object, and starting the host indicator collection component;
[0157] The monitoring object type is an application, uploading an application indicator collection component to a host where the application as the monitoring object is located, configuring startup parameters related to the application indicator collection component to the application, and starting the application;
[0158] The monitoring object type is middleware. A middleware indicator collection component is uploaded to the host where the middleware serving as the monitoring object is located, middleware connection and authentication information is configured, and the middleware indicator collection component is started.
[0159] According to one or more embodiments of the present application, the present application also discloses a monitoring indicator collection application, including:
[0160] The back-end component deployment device is used to implement the aforementioned indicator collection method.
[0161] In some implementations, the method further includes:
[0162] The front-end page is used to receive query operations for indicator collection tasks;
[0163] The backend component deployment device is also used to: in response to the query operation, obtain the query result of the indicator collection task;
[0164] The front-end page is also used to display the query results.
[0165] In some implementations, the backend component deployment device is further used to:
[0166] The indicator collection task that cannot normally collect monitoring indicators is queried as a target task, and the indicator collection component in the target monitoring object is redeployed, and the target monitoring object is the monitoring object in the target task.
[0167] In some implementations, the backend component deployment device is further used to:
[0168] If the redeployment of the indicator collection component in the target monitoring object fails, an alarm notification is issued.
[0169] According to one or more embodiments of the present application, the present application also discloses a monitoring indicator collection system, including:
[0170] A configuration database, used to store configuration information, the configuration information including: information of a monitored object and information of an indicator collection component corresponding to the monitored object;
[0171] The aforementioned indicator collection application;
[0172] A collection device is used to collect the indicators of the monitored object based on the indicator collection component deployed by the indicator collection application.
[0173] According to one or more embodiments of the present application, the present application further discloses an electronic device, including:
[0174] Memory and processor;
[0175] The memory is used to store a computer program, and the processor is used to run the computer program to implement the monitoring indicator collection method disclosed in the present application.
[0176] According to one or more embodiments of the present application, the present application also discloses a readable storage medium. When the instructions in the readable storage medium are executed by a processor of an electronic device, the electronic device can execute the monitoring indicator collection method disclosed in the present application.
[0177] Although the subject matter has been described in language specific to structural features and / or methodological logical actions, it should be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or actions described above. On the contrary, the specific features and actions described above are merely example forms of implementing the claims.
[0178] Although several specific implementation details are included in the above discussion, these should not be interpreted as limiting the scope of the present disclosure. Certain features described in the context of a separate embodiment can also be implemented in a single embodiment in combination. On the contrary, the various features described in the context of a single embodiment can also be implemented in multiple embodiments individually or in any suitable sub-combination.
[0179] The above description is only a preferred embodiment of the present disclosure and an explanation of the technical principles used. Those skilled in the art should understand that the scope of disclosure involved in the present disclosure is not limited to the technical solutions formed by a specific combination of the above technical features, but should also cover other technical solutions formed by any combination of the above technical features or their equivalent features without departing from the above disclosed concept. For example, the above features are replaced with the technical features with similar functions disclosed in the present disclosure (but not limited to) by each other to form a technical solution.
Claims
1. A monitoring indicator collection method, characterized in that: include: Query configuration information, the configuration information including: information of the monitored object and information of the indicator collection component corresponding to the monitored object; Based on the configuration information, an indicator collection component is deployed in the monitored object, and the indicator collection component is used to collect indicators of the monitored object.
2. The indicator collection method according to claim 1, characterized in that: The deploying the indicator collection component in the monitoring object based on the configuration information includes: Based on the type of the monitored object indicated by the configuration information, an indicator collection component is deployed in the monitored object.
3. The indicator collection method according to claim 1, characterized in that: The deploying of the indicator collection component in the monitored object based on the type of the monitored object indicated by the configuration information includes at least one of the following methods: The monitoring object type is a host, uploading a host indicator collection component to the host as the monitoring object, and starting the host indicator collection component; The monitoring object type is an application, uploading an application indicator collection component to a host where the application as the monitoring object is located, configuring startup parameters related to the application indicator collection component to the application, and starting the application; The monitoring object type is middleware. A middleware indicator collection component is uploaded to the host where the middleware serving as the monitoring object is located, middleware connection and authentication information is configured, and the middleware indicator collection component is started.
4. A monitoring indicator collection application, characterized in that: include: A back-end component deployment device, used to implement the indicator collection method described in any one of claims 1-3.
5. The indicator collection application according to claim 4, characterized in that: Also includes: The front-end page is used to receive query operations for indicator collection tasks; The backend component deployment device is also used to: in response to the query operation, obtain the query result of the indicator collection task; The front-end page is also used to display the query results.
6. The indicator collection application according to claim 4 or 5, characterized in that: The backend component deployment device is also used for: The indicator collection task that cannot normally collect monitoring indicators is queried as a target task, and the indicator collection component in the target monitoring object is redeployed, and the target monitoring object is the monitoring object in the target task.
7. The indicator collection application according to claim 4 or 5, characterized in that: The backend component deployment device is also used for: If the redeployment of the indicator collection component in the target monitoring object fails, an alarm notification is issued.
8. A monitoring index collection system, characterized in that: include: A configuration database, used to store configuration information, the configuration information including: information of a monitored object and information of an indicator collection component corresponding to the monitored object; The indicator collection application according to any one of claims 4 to 7; A collection device is used to collect the indicators of the monitored object based on the indicator collection component deployed by the indicator collection application.
9. An electronic device, characterized in that: include: Memory and processor; The memory is used to store a computer program, and the processor is used to run the computer program to implement the monitoring indicator collection method according to any one of claims 1 to 3.
10. A readable storage medium, when the instructions in the readable storage medium are executed by a processor of an electronic device, the electronic device can execute the monitoring indicator collection method according to any one of claims 1 to 3.
