Operation and maintenance monitoring processing methods, devices, equipment and media

Abstract

The present application provides an operation and maintenance monitoring processing method, apparatus, computer equipment and storage medium. The method comprises: obtaining the collected data reported when the collection instance corresponding to the entity is executed, the collection instance being a script file corresponding to the collection model that is pre-issued to the entity, obtaining the entity endpoint list corresponding to the collection model token in the cache module, adding the entity endpoint to the entity endpoint list if the entity endpoint contained in the collection data is not contained in the entity endpoint list, obtaining the alarm policy corresponding to the collection model token, adding the entity to the entity data corresponding to the alarm policy, configuring the collection model token for the collection model, dynamically managing the entity endpoint list corresponding to the collection model token according to the collection data reported by the collection instance, and then establishing an association relationship between the entity and the alarm policy, thereby improving the accuracy and flexibility of determining the entity corresponding to the alarm policy.

Description

Technical Field

[0001] The present application relates to the field of operation and maintenance monitoring technology, and in particular to an operation and maintenance monitoring processing method, apparatus, computer equipment and storage medium. Background Art

[0002] In operations monitoring, it's often necessary to match alert policies to corresponding entities. This allows you to confirm whether alert conditions are triggered when subsequent monitoring events are reported, thereby issuing alerts. Operations monitoring involves a variety of different monitoring entities, and the operations monitoring server must determine the specific entity to which the alert policy corresponds when configuring it.

[0003] In current technology, an operation and maintenance monitoring server usually pre-configures a correspondence between an alarm strategy and a monitoring entity. When a monitoring entity undergoes dynamic changes, the accuracy of the monitoring entity corresponding to the alarm strategy is affected. Summary of the Invention

[0004] Based on this, it is necessary to provide an operation and maintenance monitoring processing method, device, computer equipment and storage medium to address the technical problem of low accuracy in determining the monitoring entity corresponding to the alarm strategy in the current technology.

[0005] An operation and maintenance monitoring processing method, applied to an operation and maintenance monitoring server, the method comprising:

[0006] Acquire the collected data reported when the collection instance is executed; the collection instance is a script file corresponding to the collection model that is pre-issued to the entity; the collected data includes the entity endpoint and the collection model token;

[0007] Obtaining an entity endpoint list corresponding to the acquisition model token in a cache module, and if the entity endpoint is not included in the entity endpoint list, adding the entity endpoint to the entity endpoint list;

[0008] Obtain the alarm strategy corresponding to the acquisition model token, and add the entity to the entity data corresponding to the alarm strategy; the alarm strategy is associated with the acquisition model through the acquisition model token, and the alarm strategy is used to be triggered by the entity event corresponding to the entity to issue an alarm.

[0009] In one embodiment, before obtaining the collected data reported when the collection instance is executed, the method further includes:

[0010] Register the acquisition model and obtain an acquisition model token corresponding to the acquisition model;

[0011] The acquisition model token is written into the corresponding acquisition instance, and the acquisition instance is sent to the corresponding entity.

[0012] In one embodiment, the method further comprises:

[0013] If the entity endpoint is included in the entity endpoint list, update the entity endpoint list and the data expiration time corresponding to the entity endpoint.

[0014] In one embodiment, the method further comprises:

[0015] Querying the cache module for the entity endpoint list corresponding to the acquisition model token, and the data expiration time corresponding to each entity endpoint in the entity endpoint list;

[0016] If the data expiration time corresponding to any entity endpoint exceeds the preset expiration time, the entity endpoint will be deleted from the entity endpoint list, and the entity will be deleted from the entity data corresponding to the alarm strategy corresponding to the collection model token.

[0017] In one embodiment, the method further comprises:

[0018] Control the host corresponding to the entity to delete the collection instance.

[0019] In one embodiment, the method further comprises:

[0020] Get the component-host configuration type corresponding to the target host;

[0021] If the component-host configuration type is a deployment service, obtaining the service change operation of the host on the entity and updating the alarm policy corresponding to the host;

[0022] If the component-host configuration type is an interface service, obtain the target cluster's add / delete operation on the host, query the target cluster's interface service list, and update the alarm policy corresponding to the cluster's interface service list.

[0023] In one embodiment, the collected data further includes a collection instance token, and the method further includes:

[0024] Obtaining the entity endpoint list corresponding to the collection instance token in the cache module, and adding the entity endpoint to the entity endpoint list corresponding to the collection instance token;

[0025] Obtain the alarm policy corresponding to the collection instance token, and add the entity to the entity data corresponding to the alarm policy.

[0026] An operation and maintenance monitoring processing device, comprising:

[0027] Applied to an operation and maintenance monitoring server, the device includes:

[0028] A collection data acquisition module is used to acquire the collection data reported when the collection instance is executed; the collection instance is a script file corresponding to the collection model that is pre-issued to the entity; the collection data includes the entity endpoint and the collection model token;

[0029] An entity endpoint association module is used to obtain an entity endpoint list corresponding to the acquisition model token in a cache module, and if the entity endpoint is not included in the entity endpoint list, add the entity endpoint to the entity endpoint list;

[0030] An alarm strategy association module is used to obtain the alarm strategy corresponding to the acquisition model token and add the entity to the entity data corresponding to the alarm strategy; the alarm strategy is associated with the acquisition model through the acquisition model token, and the alarm strategy is used to be triggered by the entity event corresponding to the entity to issue an alarm.

[0031] A computer device includes a memory and a processor, wherein the memory stores a computer program, and when the processor executes the computer program, the steps of the operation and maintenance monitoring processing method in any of the above embodiments are implemented.

[0032] A computer-readable storage medium stores a computer program, which, when executed by a processor, implements the steps of the operation and maintenance monitoring processing method in any of the above embodiments.

[0033] The above-mentioned operation and maintenance monitoring processing method, device, computer equipment and storage medium obtain the collection data reported when the collection instance corresponding to the entity is executed. The collection instance is a script file corresponding to the collection model that is pre-issued to the entity, and obtains the entity endpoint list corresponding to the collection model token in the cache module. If the entity endpoint contained in the collection data is not included in the entity endpoint list, the entity endpoint is added to the entity endpoint list, the alarm strategy corresponding to the collection model token is obtained, and the entity is added to the entity data corresponding to the alarm strategy. By configuring the collection model token for the collection model, the entity endpoint list corresponding to the collection model token is dynamically managed according to the collection data reported by the collection instance, and then the association relationship between the entity and the alarm strategy is established, thereby improving the accuracy and flexibility of determining the entity corresponding to the alarm strategy. BRIEF DESCRIPTION OF THE DRAWINGS

[0034] Figure 1 Schematic diagram of a process flow of an operation and maintenance monitoring method in one embodiment;

[0035] Figure 2 A flowchart of an operation and maintenance monitoring processing method in another embodiment;

[0036] Figure 3A flowchart of an operation and maintenance monitoring processing method in another embodiment;

[0037] Figure 4 This is a structural block diagram of an operation and maintenance monitoring processing device in one embodiment;

[0038] Figure 5 FIG. 1 is a diagram showing the internal structure of a computer device in one embodiment. DETAILED DESCRIPTION

[0039] In order to make the purpose, technical solutions and advantages of this application more clear, the following further describes this application in detail with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain this application and are not intended to limit this application.

[0040] In one embodiment, Figure 1 As shown, an operation and maintenance monitoring processing method is provided. This embodiment uses the method applied to an operation and maintenance monitoring server as an example. In this embodiment, the method includes the following steps:

[0041] Step S101: Acquire the collected data reported when the collection instance is executed.

[0042] Among them, the collection instance can be a script file that is pre-distributed to the entity and corresponds to the collection model. The collection instance can be executed to report the collection data; the collection data may include the entity endpoint and the collection model token. The entity can refer to a specific service or service-role on the machine. The service or service-role can be deployed, expanded, reduced or uninstalled on the host. The entity endpoint can be the entity endpoint, which can include cluster name, service name, service role name, host IP and other information. The collection model token can be a unique token generated by the operation and maintenance monitoring server for each collection model. The operation and maintenance monitoring server can write the collection model token into the collection instance when sending the collection instance to the entity.

[0043] In a specific implementation, the operation and maintenance monitoring server obtains the collection data reported when the collection instance is executed in the entity, and obtains the entity endpoint and collection model token corresponding to the collection instance from it.

[0044] Step S202: Obtain an entity endpoint list corresponding to the acquisition model token in the cache module. If the entity endpoint is not included in the entity endpoint list, add the entity endpoint to the entity endpoint list.

[0045] The collection instances corresponding to the collection model can be distributed to multiple entities. Each entity has a corresponding entity endpoint. Therefore, the same collection model can correspond to multiple entity endpoints. This can be stored in the cache module as an entity endpoint list. The operation and maintenance monitoring server can query the entity endpoint list corresponding to the collection model using the collection model token. The entity endpoint corresponding to the collection model token can be added or deleted.

[0046] In the specific implementation, the operation and maintenance monitoring server can query the entity endpoint list corresponding to the collection model token in the cache module based on the collection model token contained in the collected data. If the entity endpoint is not included in the entity endpoint list corresponding to the collection model token, the entity endpoint can be added to the corresponding entity endpoint list.

[0047] Step S203: Obtain the alarm policy corresponding to the acquisition model token, and add the entity to the entity data corresponding to the alarm policy.

[0048] The alarm policy can be associated with the collection model through the collection model token. The alarm policy can be used to trigger the entity event corresponding to the entity to issue an alarm, such as sending a text message notification to the terminal. The operation and maintenance monitoring server can configure the corresponding alarm policy for the collection model, and the alarm policy can establish an association relationship with the entity, thereby enabling monitoring of the associated entity.

[0049] In a specific implementation, the operation and maintenance monitoring server can obtain the pre-configured alarm strategy according to the collection model token, and add the entity to the entity data corresponding to the alarm strategy, establish an association relationship between the entity and the alarm strategy, and realize monitoring of the entity.

[0050] In the above-mentioned operation and maintenance monitoring processing method, the collection data reported when the collection instance corresponding to the entity is executed is obtained. The collection instance is a script file corresponding to the collection model that is pre-sent to the entity, and the entity endpoint list corresponding to the collection model token in the cache module is obtained. If the entity endpoint contained in the collection data is not included in the entity endpoint list, the entity endpoint is added to the entity endpoint list, and the alarm strategy corresponding to the collection model token is obtained. The entity is added to the entity data corresponding to the alarm strategy. By configuring the collection model token for the collection model, the entity endpoint list corresponding to the collection model token is dynamically managed according to the collection data reported by the collection instance, and then the association relationship between the entity and the alarm strategy is established, thereby improving the accuracy and flexibility of determining the entity corresponding to the alarm strategy.

[0051] In one embodiment, the steps before determining in step S101 to obtain the collected data reported when the collection instance is executed include:

[0052] Register the collection model and obtain the collection model token corresponding to the collection model; write the collection model token to the corresponding collection instance and send the collection instance to the corresponding entity.

[0053] In this embodiment, the operation and maintenance monitoring server registers the collection model and generates a unique token for the collection model using a Universally Unique Identifier (UUID). Based on this collection model token, the operation and maintenance monitoring server can establish an association between the collection model and the alarm policy. The operation and maintenance monitoring server can write the collection model token to the corresponding collection instance and distribute the collection instance to the corresponding entity.

[0054] In some embodiments, the collection model may include a public collection model, a plug-in collection model, and an autonomous reporting model. Among them, for the public collection model, the operation and maintenance monitoring server can send the collection instance to the host of the service cluster, and the collection instance reports the corresponding collection data when it is executed. For the plug-in collection model, the operation and maintenance monitoring server can send the collection instance to a specific machine. The collection instance corresponding to the autonomous reporting model autonomously reports data according to its own preset rules. The operation and maintenance monitoring server can send the collection instance to each collection model, and establish an association relationship between the collection model token and the entity endpoint based on the collection model token and the entity endpoint contained in the reported collection data, and then establish an association relationship between the alarm strategy and the entity based on the association relationship between the collection model token and the alarm strategy, and confirm the monitoring entity of the alarm strategy.

[0055] In some embodiments, the operation and maintenance monitoring server may send the corresponding collection instance to the corresponding entity according to the monitoring requirements of the entity.

[0056] The solution of the above embodiment, by configuring the collection model token corresponding to the collection model and writing it into the collection instance corresponding to the collection model, can establish an association relationship between the collection model token and the collection instance through the reported collection data, thereby improving the efficiency of determining the monitoring entity.

[0057] In one embodiment, the method further includes:

[0058] If the entity endpoint is included in the entity endpoint list, update the data expiration time corresponding to the entity endpoint in the entity endpoint list.

[0059] In this embodiment, the entity endpoint list may include an expiration date for the collected data corresponding to the entity. The operation and maintenance monitoring server can configure a preset data expiration period, during which all collected data reported within this period will be saved. For example, the preset data expiration period may be 7 days. If an entity endpoint generates reported data within the expiration period, the operation and maintenance monitoring server may update the data expiration date corresponding to the entity endpoint to improve the timeliness of data updates.

[0060] In some embodiments, the above method further comprises:

[0061] In the query cache module, the entity endpoint list corresponding to the collection model token and the data expiration time corresponding to each entity endpoint in the entity endpoint list are obtained; if the data expiration time corresponding to any entity endpoint exceeds the preset expiration time, the entity endpoint will be deleted from the entity endpoint list, and the entity will be deleted from the entity data corresponding to the alarm strategy corresponding to the collection model token.

[0062] In this embodiment, the operation and maintenance monitoring server can regularly update the entity endpoint list in the cache module and delete the entity endpoints corresponding to the data that has exceeded the expiration time. Specifically, the operation and maintenance monitoring server can regularly query the expiration time of the data corresponding to the entity endpoint in the entity endpoint list in the cache module. If the expiration time is exceeded, the entity endpoint will be deleted from the corresponding entity endpoint list. The operation and maintenance monitoring server can also query the entity data corresponding to the corresponding alarm strategy based on the acquisition model token and delete the entity from the corresponding entity data. The dynamic update of the association relationship between the alarm strategy and the entity is realized to ensure the accuracy of the monitoring entity associated with the alarm strategy.

[0063] In one embodiment, the method further includes:

[0064] The host corresponding to the control entity deletes the collection instance.

[0065] In this embodiment, after deleting the entity endpoint in the cache module, the operation and maintenance monitoring server can send a blueprint operation to the corresponding host to control the host to stop running the corresponding collection instance, delete the collection instance, and delete the association between the alarm policy and the entity.

[0066] In one embodiment, Figure 2 As shown, when the host is scaling down the service, uninstalling the service-role, or deleting the service, the operation and maintenance monitoring server can control the collection instance corresponding to the plug-in collection model to stop reporting data, and delete the entity endpoint corresponding to the collection model token in the cache. According to the collection model ID or collection model token, the alarm policy list is queried and the entity is deleted from the corresponding entity data in the alarm policy list.

[0067] In one embodiment, Figure 2As shown, when a host uninstalls a service, the operations and maintenance monitoring server can control the collection instance corresponding to the public collection model to stop reporting data, delete the alarm policy deployed for the service on the host during service deployment, and remove the alarm policy from the alarm policy list. If the service is imported into a cluster, the operations and maintenance monitoring server can delete the alarm policy from the association between the cluster and the alarm policy. After deleting the alarm policy, the existing alarm data triggered by the alarm policy can be displayed normally in the alarm list, and the operations and maintenance monitoring server can configure corresponding prompts for the alarm policy, such as indicating that the alarm policy has expired.

[0068] In one embodiment, the method further includes:

[0069] Get the component-host configuration type corresponding to the target host; if the component-host configuration type is a deployment service, get the host's service change operation on the entity and update the host's corresponding alarm policy; if the component-host configuration type is an interface service, get the target cluster's add / delete operation on the host, query the target cluster's interface service list, and update the cluster's interface service list corresponding alarm policy.

[0070] In this embodiment, Figure 2 As shown, the operations monitoring server can determine how to configure and change the alarm policy for a host or host cluster based on the target's corresponding component-host configuration type. Component-host configuration types can include deployment-based services and interface-based services. A component can be a specific version of a service that can be installed on a host.

[0071] For deployed services, the operations and maintenance monitoring server can record host data corresponding to each entity. Service change operations can include deploying new services on a host, scaling services or service-roles, and uninstalling them. Each service or service-role, as a monitoring entity, can be configured with an alarm policy. When a host is configured with multiple services or service-roles, the host can be associated with an alarm policy. Therefore, when a service is deployed on a host or an existing service is added to the monitoring scope, the operations and maintenance monitoring server can create a corresponding alarm policy based on the alarm policy template and establish an association between the host and the alarm policy. Based on the host monitoring policy, the operation and maintenance monitoring server can issue the corresponding collection instance for that service to collect data. When a host scales up a service, the operations and maintenance monitoring server can also update the association between the host and the alarm policy based on the expanded services. When a service is scaled down or a service role is uninstalled or deleted, the operations and maintenance monitoring server can control the collection instance corresponding to the plug-in collection model on the host to stop reporting data and update the association between the host and the alarm policy. When a service is uninstalled or deleted, the operation and maintenance monitoring server can control the collection instance corresponding to the public collection model on the host to stop reporting data and update the association between the host and the alarm policy. While updating the association between the host and the alarm policy, the operation and maintenance monitoring server can also update the entities associated with the host, such as adding or deleting associated entities.

[0072] For interface-type services, the service can be imported into the cluster through the interface, and the operation and maintenance monitoring server can weakly associate the service with the cluster to which it belongs. When the cluster adds / deletes a host, the operation and maintenance monitoring server can search the list of all interface-type services in the cluster, traverse the list of all interface-type services, query the services contained therein, and update the corresponding alarm policy for the cluster. When a new host is added to the target cluster, the operation and maintenance monitoring server can create a corresponding alarm policy according to the alarm policy template based on the monitoring requirements for the host, and update the corresponding relationship between the interface-type service list and the alarm policy of the target cluster; when a host is deleted from the target cluster, the operation and maintenance monitoring server can update the corresponding relationship between the interface-type service list and the alarm policy of the target cluster.

[0073] The solution of the above embodiment improves the accuracy of confirming the association between the alarm policy and the host by obtaining the component-host configuration type and determining the update method of the alarm policy corresponding to different component-host configuration types.

[0074] In one embodiment, the collected data may further include a collection instance token, and the above method may further include:

[0075] Get the entity endpoint list corresponding to the collection instance token in the cache module, and add the entity endpoint to the entity endpoint list corresponding to the collection instance token; get the alarm strategy corresponding to the collection instance token, and add the entity to the entity data corresponding to the alarm strategy.

[0076] In this embodiment, the collection instance token can be a unique identification token dynamically generated by the operation and maintenance monitoring server when the collection instance is sent to the entity. When the collection instance is executed, the reported collection data can include the collection instance token and the entity endpoint. Furthermore, an association between the collection instance token and the entity endpoint is established in the cache module, and a correspondence between the alarm policy and the collection instance token is further established. This strengthens the association between the alarm policy and the entity, refines the scope of entities corresponding to the alarm policy, and reduces the occurrence of dirty data and false alarms.

[0077] In some embodiments, the operation and maintenance monitoring server may write the collection instance token into the collection instance when downloading the collection instance, and set more detailed collection instance tokens for various collection models to improve the efficiency of dynamic entity changes.

[0078] The solution of the above embodiment improves the accuracy of confirming the entity corresponding to the alarm policy by establishing an association relationship between the collection instance token and the entity endpoint.

[0079] In one embodiment, Figure 3 As shown, an operation and maintenance monitoring processing method is provided, the method comprising:

[0080] Step S301: The operation and maintenance monitoring server periodically queries the cache module for a list of entity endpoints corresponding to the acquisition model token, and the data expiration time corresponding to each entity endpoint in the entity endpoint list.

[0081] Step S302: If the data expiration time corresponding to any entity endpoint exceeds the preset expiration time, the entity endpoint is deleted from the entity endpoint list of the cache module, and the entity is deleted from the entity data corresponding to the alarm strategy corresponding to the collection model token.

[0082] Step S303: The host corresponding to the control entity deletes the collection instance.

[0083] In the above embodiment, by regularly querying the cache module, the entity endpoint list corresponding to each collection model token and the data expiration time corresponding to each entity endpoint, the entity endpoint whose data expiration time exceeds the preset expiration time is deleted from the corresponding entity endpoint list, and the entity is deleted from the entity data of the alarm strategy corresponding to the collection model token, and the host corresponding to the control entity deletes the collection instance, thereby realizing the deletion operation of the collection instance with expired data, which is conducive to reducing dirty data and improving the effectiveness of the alarm strategy.

[0084] It should be understood that although Figure 1-3 The steps in the flowchart are shown in sequence as indicated by the arrows, but these steps are not necessarily executed in the order indicated by the arrows. Unless otherwise specified in this document, there is no strict order restriction for the execution of these steps, and these steps can be executed in other orders. In addition, Figure 1-3 At least part of the steps may include multiple steps or multiple stages. These steps or stages are not necessarily performed at the same time, but can be performed at different times. The order of execution of these steps or stages is not necessarily one by one, but can be performed in turn or alternately with other steps or at least part of the steps or stages in other steps.

[0085] In one embodiment, Figure 4 As shown, an operation and maintenance monitoring processing device is provided, and the device 40 includes:

[0086] The collected data acquisition module 401 is used to obtain the collected data reported when the collection instance is executed; the collection instance is a script file corresponding to the collection model that is pre-issued to the entity; the collected data includes the entity endpoint and the collection model token;

[0087] The entity endpoint association module 402 is used to obtain the entity endpoint list corresponding to the acquisition model token in the cache module, and if the entity endpoint is not included in the entity endpoint list, add the entity endpoint to the entity endpoint list;

[0088] The alarm strategy association module 403 is used to obtain the alarm strategy corresponding to the acquisition model token and add the entity to the entity data corresponding to the alarm strategy; the alarm strategy is associated with the acquisition model through the acquisition model token, and the alarm strategy is used to be triggered by the entity event corresponding to the entity to issue an alarm.

[0089] In one embodiment, the collected data acquisition module 401 includes a collection instance issuing unit for registering a collection model and obtaining a collection model token corresponding to the collection model; writing the collection model token to the corresponding collection instance and issuing the collection instance to the corresponding entity.

[0090] In one embodiment, the apparatus 400 further includes: an expiration time updating unit, configured to update the expiration time of data corresponding to the entity endpoint in the entity endpoint list if the entity endpoint is included in the entity endpoint list.

[0091] In one embodiment, the above-mentioned device 400 also includes: a deletion unit, which is used to query the entity endpoint list corresponding to the collection model token in the cache module, and the data expiration time corresponding to each entity endpoint in the entity endpoint list; if the data expiration time corresponding to any entity endpoint exceeds the preset expiration period, the entity endpoint is deleted from the entity endpoint list, and the entity is deleted from the entity data corresponding to the alarm policy corresponding to the collection model token.

[0092] In one embodiment, the deleting unit is further configured to control a host corresponding to the entity to delete the collection instance.

[0093] In one embodiment, the above-mentioned device 400 also includes: a component host unit, which is used to obtain the component-host configuration type corresponding to the target host; if the component-host configuration type is a deployment type service, obtain the host's service change operation on the entity, and update the alarm policy corresponding to the host; if the component-host configuration type is an interface type service, obtain the target cluster's add / delete operation on the host, query the target cluster's interface service list, and update the alarm policy corresponding to the cluster's interface service list.

[0094] In one embodiment, the collection data acquisition module 401 also includes: a collection instance token unit, which is used to obtain the entity endpoint list corresponding to the collection instance token in the cache module, and add the entity endpoint to the entity endpoint list corresponding to the collection instance token; obtain the alarm policy corresponding to the collection instance token, and add the entity to the entity data corresponding to the alarm policy.

[0095] The specific definition of the operation and maintenance monitoring processing device can be found in the definition of the operation and maintenance monitoring processing method above and will not be repeated here. Each module in the above-mentioned operation and maintenance monitoring processing device can be implemented in whole or in part through software, hardware, or a combination thereof. Each of the above-mentioned modules can be embedded in or independent of the processor in the computer device in hardware form, or can be stored in the memory of the computer device in software form, so that the processor can call and execute the corresponding operations of each of the above modules.

[0096] The operation and maintenance monitoring processing method provided by this application can be applied to a computer device, which can be a server, and its internal structure diagram can be as follows: Figure 5As shown. The computer device includes a processor, a memory, and a network interface connected via a system bus. The processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program, and a database. The internal memory provides an environment for the operation of the operating system and computer program in the non-volatile storage medium. The database of the computer device is used to store collected data, alarm strategy data, etc. The network interface of the computer device is used to communicate with an external terminal via a network connection. When the computer program is executed by the processor, an operation and maintenance monitoring processing method is implemented.

[0097] Those skilled in the art will understand that Figure 5 The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than shown in the figure, or combine certain components, or have a different component arrangement.

[0098] In one embodiment, a computer device is provided, including a memory and a processor. The memory stores a computer program, and the processor implements the steps in the above method embodiments when executing the computer program.

[0099] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the steps in the above-mentioned method embodiments are implemented.

[0100] Those skilled in the art will appreciate that all or part of the processes in the above-mentioned embodiment methods can be implemented by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to memory, storage, database or other media used in the embodiments provided in this application may include at least one of non-volatile and volatile memory. Non-volatile memory may include read-only memory (ROM), magnetic tape, floppy disk, flash memory or optical memory, etc. Volatile memory may include random access memory (RAM) or external cache memory. As an illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM).

[0101] The technical features of the above embodiments can be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0102] The above-described embodiments merely represent several implementation methods of the present application. While the descriptions are relatively specific and detailed, they should not be construed as limiting the scope of the present invention. It should be noted that a person skilled in the art could make various modifications and improvements without departing from the spirit of the present application, all of which fall within the scope of protection of the present application. Therefore, the scope of protection of the present patent application shall be determined by the appended claims.

Claims

1. A method for operation and maintenance monitoring, characterized in that: Applied to an operation and maintenance monitoring server, the method includes: Acquire the collected data reported when the collection instance is executed; the collection instance is a script file corresponding to the collection model that is pre-issued to the entity; the collected data includes the entity endpoint and the collection model token; the entity includes a specific service or service-role deployed on the host, the entity endpoint includes at least one of the cluster name, service name, service role name, and host IP address of the corresponding entity, the collection model is registered with the operation and maintenance monitoring server, and each collection model token is a unique identification token generated by the operation and maintenance monitoring server for each collection model; Obtaining a list of entity endpoints corresponding to the acquisition model token in a cache module, and if the entity endpoint is not included in the entity endpoint list, adding the entity endpoint to the entity endpoint list; the entity endpoint list stored in the cache module is used to represent the correspondence between the same acquisition model and multiple entity endpoints; Obtain the alarm strategy corresponding to the acquisition model token, and add the entity to the entity data corresponding to the alarm strategy; the alarm strategy is associated with the acquisition model through the acquisition model token, and the alarm strategy is used to be triggered by the entity event corresponding to the entity to issue an alarm.

2. The method according to claim 1, characterized in that Before obtaining the collected data reported when the collection instance is executed, the method further includes: Register the acquisition model and obtain an acquisition model token corresponding to the acquisition model; The acquisition model token is written into the corresponding acquisition instance, and the acquisition instance is sent to the corresponding entity.

3. The method according to claim 1, characterized in that The method further comprises: If the entity endpoint is included in the entity endpoint list, update the entity endpoint list and the data expiration time corresponding to the entity endpoint.

4. The method according to claim 1, wherein The method further comprises: Querying the cache module for the entity endpoint list corresponding to the acquisition model token, and the data expiration time corresponding to each entity endpoint in the entity endpoint list; If the data expiration time corresponding to any entity endpoint exceeds the preset expiration time, the entity endpoint will be deleted from the entity endpoint list, and the entity will be deleted from the entity data corresponding to the alarm strategy corresponding to the collection model token.

5. The method according to claim 4, characterized in that The method further comprises: Control the host corresponding to the entity to delete the collection instance.

6. The method according to any one of claims 1 to 5, characterized in that The method further comprises: Get the component-host configuration type corresponding to the target host; If the component-host configuration type is a deployment service, obtaining the service change operation of the host on the entity and updating the alarm policy corresponding to the host; If the component-host configuration type is an interface service, obtain the target cluster's add / delete operation on the host, query the target cluster's interface service list, and update the alarm policy corresponding to the cluster's interface service list.

7. The method according to claim 1, characterized in that The collected data also includes a collection instance token, and the method further includes: Obtaining the entity endpoint list corresponding to the collection instance token in the cache module, and adding the entity endpoint to the entity endpoint list corresponding to the collection instance token; Obtain the alarm policy corresponding to the collection instance token, and add the entity to the entity data corresponding to the alarm policy.

8. An operation and maintenance monitoring processing device, characterized in that: Applied to an operation and maintenance monitoring server, the device includes: A collection data acquisition module is configured to acquire the collected data reported when a collection instance is executed; the collection instance is a script file corresponding to a collection model and pre-issued to an entity; the collected data includes an entity endpoint and a collection model token; the entity includes a specific service or service-role deployed on a host, the entity endpoint includes at least one of the corresponding entity's cluster name, service name, service role name, and host IP address; the collection model is registered with the operation and maintenance monitoring server, and each collection model token is a unique identification token generated by the operation and maintenance monitoring server for each collection model; An entity endpoint association module is configured to obtain a list of entity endpoints corresponding to the acquisition model token from a cache module, and if the entity endpoint is not included in the entity endpoint list, add the entity endpoint to the entity endpoint list; the entity endpoint list stored in the cache module is used to represent the correspondence between the same acquisition model and multiple entity endpoints; An alarm strategy association module is used to obtain the alarm strategy corresponding to the acquisition model token and add the entity to the entity data corresponding to the alarm strategy; the alarm strategy is associated with the acquisition model through the acquisition model token, and the alarm strategy is used to be triggered by the entity event corresponding to the entity to issue an alarm.

9. A computer device comprising a memory and a processor, wherein the memory stores a computer program, wherein: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 7 are implemented.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 7 are implemented.

Images