Management method and system of index monitoring system, equipment and storage medium

Abstract

The embodiment of the invention discloses a management method and system of an index monitoring system, equipment and a storage medium. The management method comprises the following steps: acquiring an operation and maintenance trigger event of the index monitoring system in a preset mode; determining an event type of the operation and maintenance trigger event; and executing operation and maintenance processing corresponding to the event type of the operation and maintenance trigger event on the index monitoring system. According to the embodiment of the invention, daily operation and maintenance management is automatically carried out on the index monitoring system through the operation and maintenance management platform, operation and maintenance personnel do not need to manually carry out operation and maintenance management on the index monitoring system, the transparency and normalization of operation are remarkably improved, and the operation and maintenance cost is reduced.

Description

Technical Field

[0001] The present disclosure relates to the field of data processing technology, and in particular to a management method, system, device and storage medium of an indicator monitoring system. Background Art

[0002] In related technologies, in scenarios where network equipment, machine status, and service indicators need to be monitored, the VictoriaMetrics system is usually used as a time series database for the indicator monitoring system, and the core services of the VictoriaMetrics system are deployed on physical machines. System resources are shared between services, and the system architecture is single. Therefore, the operating cost of operating and maintaining the indicator monitoring system and changing it is high, and it is easy for the indicator monitoring system to operate abnormally due to operational errors by operation and maintenance personnel, resulting in poor stability and reliability of the indicator monitoring system.

[0003] Therefore, how to effectively deploy and operate the indicator monitoring system is a technical issue worthy of attention. Summary of the invention

[0004] In order to solve the above technical problems, embodiments of the present disclosure provide a management method, system, device and storage medium for an indicator monitoring system.

[0005] According to one aspect of an embodiment of the present disclosure, a management method for an indicator monitoring system is provided, including: obtaining an operation and maintenance trigger event of the indicator monitoring system in a preset manner; determining an event type of the operation and maintenance trigger event; and performing operation and maintenance processing corresponding to the event type of the operation and maintenance trigger event on the indicator monitoring system.

[0006] According to another aspect of the embodiments of the present disclosure, there is provided a management device for an indicator monitoring system, comprising: an event acquisition module, used to acquire an operation and maintenance triggering event of the indicator monitoring system in a preset manner; a type determination module, used to determine the event type of the operation and maintenance triggering event; and an operation and maintenance processing module, used to perform operation and maintenance processing on the indicator monitoring system corresponding to the event type of the operation and maintenance triggering event.

[0007] According to another aspect of the embodiments of the present disclosure, a management system of an indicator monitoring system is provided, comprising: an indicator monitoring system, and an operation and maintenance management platform for executing the management method of the indicator monitoring system;

[0008] Among them, the indicator monitoring system includes: at least one data writing end, at least one data storage end and a traffic forwarding gateway; a management device of the indicator system, used to obtain the operation and maintenance triggering event of the indicator monitoring system in a preset manner; determine the event type of the operation and maintenance triggering event; and perform operation and maintenance processing corresponding to the operation and maintenance triggering event on the indicator monitoring system.

[0009] According to another aspect of the embodiments of the present disclosure, a computer-readable storage medium is provided, wherein the storage medium stores a computer program, and the computer program is used to execute the above method.

[0010] According to another aspect of the embodiments of the present disclosure, an electronic device is provided, the electronic device comprising:

[0011] processor;

[0012] a memory for storing instructions executable by the processor;

[0013] The processor is used to read the executable instructions from the memory and execute the instructions to implement the above method.

[0014] According to another aspect of the embodiments of the present disclosure, a computer program product is provided, including computer program instructions, and when the computer program instructions are executed by a processor, the above method is implemented.

[0015] Based on the above embodiments of the present disclosure, an operation and maintenance management platform is provided for the indicator monitoring system, and the operation and maintenance management platform obtains the operation and maintenance triggering events of the indicator monitoring system in a preset manner; based on the event type of the operation and maintenance triggering event, the operation and maintenance corresponding to the event type of the indicator monitoring system is processed. Therefore, the technical solution of the present disclosure can automatically perform daily operation and maintenance management of the indicator monitoring system through the operation and maintenance management platform, without the need for operation and maintenance personnel to manually perform operation and maintenance management of the indicator monitoring system, which significantly improves the transparency and standardization of operations, reduces operation and maintenance costs, and improves the security and stability of the indicator monitoring system, which helps to achieve efficient indicator monitoring effects.

[0016] The technical solution of the present disclosure is further described in detail below through the accompanying drawings and embodiments. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] The above and other purposes, features and advantages of the present disclosure will become more apparent by describing the embodiments of the present disclosure in more detail in conjunction with the accompanying drawings. The accompanying drawings are used to provide a further understanding of the embodiments of the present disclosure and constitute a part of the specification. Together with the embodiments of the present disclosure, they are used to explain the present disclosure and do not constitute a limitation of the present disclosure. In the drawings, the same reference numerals generally represent the same components or steps.

[0018] The present disclosure may be more clearly understood from the following detailed description with reference to the accompanying drawings, in which:

[0019] Figure 1 A schematic diagram of the architecture of the management system of the indicator monitoring system disclosed in the present invention;

[0020] Figure 2 A schematic diagram of the architecture of the operation and maintenance management platform of the indicator monitoring system disclosed in the present invention;

[0021] Figure 3 A flowchart of an embodiment of a management method of an indicator monitoring system disclosed in the present invention;

[0022] Figure 4 A flowchart of another embodiment of the management method of the indicator monitoring system disclosed in the present invention;

[0023] Figure 5 A flowchart of another embodiment of the management method of the indicator monitoring system disclosed in the present invention;

[0024] Figure 6 A flowchart of another embodiment of the management method of the indicator monitoring system disclosed in the present invention;

[0025] Figure 7 A schematic diagram of the structure of an embodiment of a management device of an indicator monitoring system disclosed in the present invention;

[0026] Figure 8 A structural diagram of another embodiment of the management device of the indicator monitoring system disclosed in the present invention;

[0027] Fig. 9 A structural diagram of an electronic device provided for an exemplary embodiment of the present disclosure. DETAILED DESCRIPTION

[0028] Below, the exemplary embodiments according to the present disclosure will be described in detail with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of the present disclosure, rather than all the embodiments of the present disclosure, and it should be understood that the present disclosure is not limited to the exemplary embodiments described here.

[0029] It should be noted that the relative arrangement of components and steps, the numerical expressions and numerical values ​​set forth in these embodiments do not limit the scope of the present disclosure unless specifically stated otherwise.

[0030] Those skilled in the art can understand that the terms "first" and "second" in the embodiments of the present disclosure are only used to distinguish different steps, devices or modules, etc., and neither represent any specific technical meaning nor indicate the necessary functional module order between them.

[0031] It should also be understood that in the embodiments of the present disclosure, “plurality” may refer to two or more than two, and “at least one” may refer to one, two, or more than two.

[0032] It should also be understood that any component, data or structure mentioned in the embodiments of the present disclosure can generally be understood as one or more, unless explicitly limited or otherwise indicated in the context.

[0033] In addition, the term "and / or" in the present disclosure is only a description of the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in the present disclosure generally indicates that the associated objects before and after are in an "or" relationship.

[0034] It should also be understood that the description of the various embodiments in the present disclosure focuses on the differences between the various embodiments, and the same or similar aspects thereof can be referenced to each other, and for the sake of brevity, they will not be described one by one.

[0035] At the same time, it should be understood that for the convenience of description, the sizes of the various parts shown in the drawings are not drawn according to the actual proportional relationship.

[0036] The following description of at least one exemplary embodiment is merely illustrative in nature and is in no way intended to limit the present disclosure, its application, or uses.

[0037] Technologies, methods, and equipment known to ordinary technicians in the relevant art may not be discussed in detail, but where appropriate, the technologies, methods, and equipment should be considered as part of the specification.

[0038] It should be noted that like reference numerals and letters refer to similar items in the following figures, and therefore, once an item is defined in one figure, it need not be further discussed in subsequent figures.

[0039] The disclosed embodiments can be applied to electronic devices such as terminal devices, computer systems, servers, etc., which can operate with many other general or special computing system environments or configurations. Examples of well-known terminal devices, computing systems, environments and / or configurations suitable for use with electronic devices such as terminal devices, computer systems, servers, etc. include, but are not limited to: personal computer systems, server computer systems, thin clients, thick clients, handheld or laptop devices, microprocessor-based systems, set-top boxes, programmable consumer electronics, network personal computers, small computer systems, large computer systems, and distributed cloud computing technology environments including any of the above systems, etc.

[0040] Electronic devices such as terminal devices, computer systems, servers, etc. can be described in the general context of computer system executable instructions (such as program modules) executed by computer systems. In general, program modules can include routines, programs, target programs, components, functional modules, data structures, etc., which perform specific tasks or implement specific abstract data types. Computer systems / servers can be implemented in a distributed cloud computing environment, where tasks are performed by remote processing devices linked through a communication network. In a distributed cloud computing environment, program modules can be located on local or remote computing system storage media including storage devices.

[0041] SUMMARY OF THE DISCLOSURE

[0042] The technical solution provided by the embodiments of the present disclosure is used in scenarios where VictoriaMetrics (a fast, efficient, economical and scalable monitoring solution and time series database) is used for efficient monitoring and time series data management. The operation and maintenance cost of the indicator monitoring system based on VictoriaMetrics is high, and it is easy to cause abnormalities in the indicator monitoring system when facing problem troubleshooting, service restart or capacity expansion.

[0043] The disclosed technical solution can automatically monitor the indicators of the system for daily operation and maintenance, which is simple to operate and highly efficient.

[0044] Exemplary Systems

[0045] Figure 1 This is a schematic diagram of the architecture of the management system of the indicator monitoring system disclosed in the present invention; the system architecture is a schematic diagram of the architecture of managing the indicator monitoring system through an operation and maintenance management platform.

[0046] like Figure 1 As shown, the management system of the indicator monitoring system includes an operation and maintenance management platform 101 and an indicator monitoring system 102. The indicator monitoring system 102 includes monitoring components: a writing end 121, a forwarding end 122, and a storage end 123. Among them, the present disclosure uses a containerized deployment of the writing end 121, the forwarding end 122, and the storage end 123 through a container orchestration system (such as Kubernetes, referred to as K8s). The operation and maintenance management platform 101 monitors each monitoring component in the indicator monitoring system, deploys resources, etc. by calling the K8s interface.

[0047] Among them, the indicator data capture component (such as VictoriaMetricsAgent, referred to as VMAgent) in the write end 121 of the indicator monitoring system 102 dynamically discovers and manages monitoring tasks through the Consul cluster. After the various monitoring components in the indicator monitoring system 102 are deployed in containers, the indicator data capture component VMAgent can be grouped according to the capture time interval, and each group of indicator data capture components is used to capture the indicator data, service data, etc. of the devices in different monitoring cycles. Containerization and group deployment of the write end 121 help to avoid the performance bottleneck caused by a single large cluster, achieve more flexible parameter configuration, and reduce the scope of influence of the failure, and improve the stability and scalability of the system. When an indicator data capture component fails or the traffic is too high, the operation and maintenance management platform 101 can switch the data capture task to other available VMAgents, thereby improving the high availability and fault tolerance of the indicator monitoring system 102.

[0048] The forwarding end 122 in the indicator monitoring system 102 is a traffic forwarding gateway that supports custom traffic forwarding strategies and flexibly controls the writing end 121 to write the indicator monitoring data into the corresponding VM cluster of the storage end 123. When the indicator monitoring system adds a task to monitor the equipment in a new computer room and creates a corresponding VM cluster to store the monitoring data, the operation and maintenance management platform 101 can adjust the traffic forwarding strategy and add a forwarding strategy for writing to the newly created VM cluster; or when load balancing is required, the operation and maintenance management platform 101 can adjust the traffic forwarding strategy. For example, if the traffic of a VM cluster 1 increases sharply, the operation and maintenance management platform 101 can change part of the data originally to be written to VM cluster 1 to be written to VM cluster 2.

[0049] The storage end 123 in the indicator monitoring system 102 is used to store monitoring data. When the traffic increases rapidly, the memory release (Out of Memory Kill, referred to as OOM Kill) phenomenon is prone to occur, resulting in instability or even collapse of the VM cluster. The operation and maintenance management platform 101 can regularly detect the processor and memory usage of the running instance of the indicator data storage component or other monitoring components (indicator data insertion component, indicator data query component). When the resource usage exceeds the set threshold, the operation and maintenance management platform 101 automatically triggers the expansion operation, dynamically increases the number of copies of the running instance, effectively responds to sudden high-traffic write scenarios, and significantly improves the stability of the VM cluster.

[0050] The operation and maintenance management platform 101 implements containerized deployment and daily operation and maintenance processing of the indicator monitoring system 102 by calling the K8s interface. It can quickly locate the problem and take operation and maintenance processing operations when the indicator monitoring system 102 fails or the load increases, effectively improving the reliability and stability of the indicator monitoring system.

[0051] Figure 2 The schematic diagram of the architecture of the operation and maintenance management platform of the indicator monitoring system disclosed in the present invention shows the above Figure 1 Schematic diagram of the architecture of the operation and maintenance management platform 101. The operation and maintenance management platform includes a front-end interactive interface, a service routing module, a business service module, a basic service module, a database, and an operating environment.

[0052] Among them, the front-end interactive interface is a visual operation interface of the operation and maintenance management platform. Through this front-end interactive interface, the deployment, management and daily operation and maintenance processing of each monitoring component in the indicator monitoring system can be efficiently completed, the operation and maintenance efficiency is high, the risk of operational errors is reduced, and potential problems can be quickly located and timely measures can be taken. For example, when a host machine of a monitoring component in the indicator monitoring system fails, the alarm information can be displayed on the front-end interactive interface in time, and an operation and maintenance processing interface can be provided. Therefore, the operation and maintenance personnel can set the status of the host machine to unschedulable through the operation and maintenance processing interface, and promptly migrate the monitoring tasks performed by the faulty host machine to other host machines for execution.

[0053] The service routing module is used to call the services in the corresponding business service module through the interface based on the operations received by the front-end interactive interface to complete the corresponding processing.

[0054] The business service module is used to provide monitoring component management services, traffic forwarding gateway (configure traffic forwarding policies) services, fault migration services and automatic capacity expansion services. The corresponding services can be used to perform corresponding management operations on the indicator monitoring system during daily operation and maintenance or monitoring component deployment.

[0055] The basic service module is used to provide services such as user login, audit log and monitoring. After the operation and maintenance personnel log in to the operation and maintenance management platform, they can view the operation log through the audit log and monitor the performance of each monitoring component in the indicator monitoring system through the monitoring service.

[0056] The database is mainly used to record the configuration information (container interface, container resource allocation information), fault records, maintenance records, etc. of each monitoring component in the indicator monitoring system.

[0057] The operation and maintenance management platform can run in the cloud host. The operation and maintenance personnel can perform daily operation and maintenance management of the indicator monitoring system by logging into the operation and maintenance management platform, which improves the transparency and standardization of operations and reduces the cost of operation and maintenance management. The operation and maintenance management log information can be recorded in real time on the operation and maintenance management platform. Through the operation and maintenance management log, the change operations of the indicator monitoring system can be traceable, which facilitates the maintenance of the stability of the indicator monitoring system.

[0058] In the present disclosure, the operation and maintenance management platform obtains the operation and maintenance trigger events of the indicator monitoring system in a preset manner; based on the operation and maintenance trigger events, the corresponding operation and maintenance processing is automatically performed on the indicator monitoring system, thereby realizing effective operation and maintenance management of the indicator monitoring system, with low operation and maintenance and change management costs, which helps to ensure the stability and reliability of the indicator monitoring system.

[0059] Exemplary Methods

[0060] Figure 3 Flow chart of an embodiment of the management method of the indicator monitoring system disclosed in the present invention; the management method of the indicator monitoring system can be applied to a cloud server (such as a computer system, a server), such as Figure 3 As shown, the management method of the index monitoring system includes the following steps 301 to 303. Each step is described below.

[0061] In step 301, an operation and maintenance triggering event of the indicator monitoring system is obtained in a preset manner.

[0062] Among them, the method of obtaining operation and maintenance trigger events of the indicator monitoring system can be at least one of the following: receiving operation and maintenance trigger events reported by the indicator monitoring system; or, real-time monitoring of the component status of each monitoring component in the indicator monitoring system to obtain operation and maintenance trigger events of the indicator monitoring system.

[0063] In some embodiments, the indicator monitoring system can generate an operation and maintenance trigger event and report it to the operation and maintenance management platform when an event occurs that requires operation and maintenance processing, for example, when the host machine of the monitoring component fails, or when the load of a monitoring component is too high. The operation and maintenance management platform can receive the operation and maintenance trigger event reported by the indicator monitoring system.

[0064] In other embodiments, the operation and maintenance management platform can monitor each monitoring component in the indicator monitoring system in real time through the K8s interface, for example, monitor the container resource usage information (including CPU usage information, memory usage information, etc.) of each monitoring component.

[0065] In this embodiment, before executing the operation of obtaining the operation and maintenance trigger event of the indicator monitoring system, it is also necessary to containerize the monitoring components in the indicator monitoring system based on the system deployment operation when receiving the system deployment operation triggered by the user through the interface. The monitoring components include at least one of the following: an indicator data capture component, an indicator data insertion component, an indicator data storage component, and an indicator data query component.

[0066] In this embodiment, in order to ensure that the resources of each monitoring component in the indicator monitoring system can be effectively isolated, to avoid resource competition among components under high load, resulting in a certain component occupying too many resources, the performance of other components being degraded or failing, and affecting the stability of the entire cluster, the indicator monitoring system disclosed in this disclosure deploys each monitoring component in a containerized manner, so that the host machine can ensure the effective isolation of the resources of each monitoring component by configuring corresponding resources for each container. In addition, during the operation of the indicator monitoring system, the operation and maintenance triggering events of the indicator monitoring system can be obtained through the container interface and container resource utilization information of each monitoring component.

[0067] In step 302, the event type of the operation and maintenance triggering event is determined.

[0068] Among them, the event types of operation and maintenance trigger events may include but are not limited to the following types: host failure events, capacity expansion events, and traffic forwarding strategy adjustment events.

[0069] Among them, the host failure event is used to indicate that the device (or virtualized device) that provides resources for the monitoring component (container) fails and needs to be repaired. The expansion event is used to indicate that the resource consumption of the monitoring component (container) reaches the preset threshold and the number of "copies" of the VictoriaMetrics instance or related services needs to be increased. The traffic forwarding strategy adjustment event is used to indicate that the indicator monitoring data on the write side needs to be written to the VMStorage cluster. Changes.

[0070] In the present disclosure, when reporting an operation and maintenance triggering event, the indicator monitoring system may also report the event type of the operation and maintenance triggering event.

[0071] In step 303, operation and maintenance processing corresponding to the event type of the operation and maintenance triggering event is performed on the indicator monitoring system.

[0072] Different types of operation and maintenance trigger events require different operation and maintenance processing operations. Figure 4-Figure 6 The description of the illustrated embodiment will not be described in detail here.

[0073] In the above steps 301 to 303, the operation and maintenance management platform obtains the operation and maintenance triggering event of the indicator monitoring system in a preset manner; based on the event type of the operation and maintenance triggering event, the corresponding operation and maintenance processing is performed on the indicator monitoring system. Therefore, the technical solution disclosed in the present invention can automatically perform daily operation and maintenance management of the indicator monitoring system through the operation and maintenance management platform, without the need for operation and maintenance personnel to manually perform operation and maintenance management of the indicator monitoring system, which significantly improves the transparency and standardization of operations, reduces operation and maintenance costs, and improves the security and stability of the indicator monitoring system, which helps to achieve efficient indicator monitoring effects.

[0074] In some optional implementations, the operation and maintenance management platform may also remotely back up the data stored in the indicator data storage component to a network storage server according to a preset period.

[0075] Specifically, in containerized deployment, common storage methods include network storage and local storage. Network storage, such as Network File System (NFS), provides flexible storage management, especially in a multi-node environment, which can achieve data sharing and high availability. By backing up the data stored locally in the VictoriaMetrics cluster to a network storage server through network storage, different monitoring components in the VictoriaMetrics cluster can access storage resources across multiple nodes, thereby providing data persistence and disaster recovery capabilities.

[0076] It is understandable that the performance of network storage usually depends on network bandwidth and latency. For high-frequency read and write operations, network storage may become a bottleneck, affecting the read and write efficiency of monitoring data, while local storage can usually provide faster input / output (I / O) performance. Since local storage is directly located on the local physical host, the data read and write latency is low, which is suitable for scenarios that require high throughput. When using local storage, the VictoriaMetrics cluster can give full play to its efficient data compression algorithms and data processing capabilities. However, the disadvantage of local storage is that the fault recovery and scalability of monitoring data are relatively limited. Therefore, in this implementation, a combination of local storage and remote backup is adopted. When querying, the monitoring data stored locally is accessed first. When the host machine fails and node migration is required, the data can be restored from the remote backup.

[0077] Specifically, when the VMStorage service is deployed in a containerized manner, three containers are included: the initialization container (InitContainer), the container responsible for storage services (VMStorage-Container), and the container responsible for backup services (VMBackup-Container). InitContainer is used to check whether there is a data backup remotely before the Pod (one or more containers) is started. If so, it is downloaded to the mounted directory. VMBackup-Container is responsible for regularly backing up data to remote storage to ensure data security and recoverability. The operation and maintenance management platform can set the period for VMBackup-Container to backup data by calling the VMBackup-Container interface.

[0078] In this implementation, an automatic disaster recovery backup solution is implemented, which can regularly back up data to a remote network storage server to ensure data security and recoverability.

[0079] Figure 4 This is a flowchart of another embodiment of the management method of the indicator monitoring system disclosed in the present invention; this embodiment takes how to handle a host machine failure event as an example for exemplary description, such as Figure 4 As shown, it includes the following steps 401 to 402. Each step is described below.

[0080] In step 401, in response to the operation and maintenance triggering event being a host machine failure event, a host machine where the failure occurs is determined based on the host machine failure event.

[0081] The host failure event is used to indicate an event that a device (or virtualized device) that provides resources for a monitoring component (container) fails and needs to be repaired.

[0082] In some implementations, when a host machine reports a fault event, the operation and maintenance management platform may determine a host machine identifier of the host machine where the fault occurs based on the reported event.

[0083] In other embodiments, when the operation and maintenance management platform monitors the indicator monitoring system in real time, it can also determine the host machine where the failure event occurred based on the resource usage information of each container on the host machine. For example, if all Pods or instances on a host machine can no longer be used, or the monitoring data on the host machine is lost, or the monitoring data is interrupted, etc., it can be determined that a failure event has occurred on the host machine and the host machine identifier of the failed host machine can be determined.

[0084] In step 402, the state of the failed host machine is set to an unschedulable state, and an eviction operation is performed on the running instance deployed on the host machine.

[0085] When it is determined that a host failure event has occurred, the state of the failed host can be set to an unschedulable state to ensure that the running Pods are not affected during the host maintenance.

[0086] In this example, by evicting the Pod or running instance deployed on the host, the evicted Pod or running instance can be migrated to other hosts for operation according to the internal scheduling policy of K8s.

[0087] After migrating the Pod or running instance to another host machine, the data can be restored from the remote backup network storage server to ensure that the Pod or running instance can continue to run normally.

[0088] The above steps 401 to 402 disclose an operation and maintenance processing method when a host failure event occurs. When any host fails, the Pod or running instance deployed on the failed host can be seamlessly switched to other available hosts, further improving the high availability and fault tolerance of the system.

[0089] Figure 5 FIG. 1 is a flowchart of another embodiment of the management method of the indicator monitoring system disclosed in the present invention; this embodiment uses how to handle the expansion event as an example to illustrate, Figure 5 As shown, it includes the following steps 501 to 502. Each step is described below.

[0090] In step 501, in response to the operation and maintenance triggering event being a capacity expansion event, based on the capacity expansion event, the type of monitoring component to be expanded is determined.

[0091] The expansion event is used to indicate that the resource consumption of the monitoring component (container) reaches the preset threshold and the number of "copies" of VictoriaMetrics instances or related services needs to be increased. The type of monitoring component to be expanded is used to indicate the type of monitoring component to be expanded, such as VMAgent, VMStorage, VMInsert, VMSelect, etc.

[0092] In some implementations, when a host machine reports a capacity expansion event, the operation and maintenance management platform may determine the type of monitoring component to be expanded based on the reported event.

[0093] In other embodiments, when the operation and maintenance management platform monitors the indicator monitoring system in real time, it can also determine the usage of the corresponding monitoring component based on the resource usage information of each container on the host machine. When the used resources exceed the preset threshold, the type of monitoring component to be expanded can be obtained.

[0094] In step 502, a monitoring component instance consistent with the monitoring component type is added.

[0095] Among them, in a containerized deployment environment, an automatic expansion strategy can be introduced to improve the indicator monitoring system's ability to cope with large-scale traffic writing, and when expansion is needed, dynamically increase monitoring component instances that are consistent with the monitoring component type.

[0096] The above steps 501 to 502 disclose an implementation method for dynamically increasing running instances through an automatic capacity expansion strategy based on containerized deployment. Through this implementation method, the present disclosure can effectively cope with sudden high-traffic write scenarios, significantly improve the stability of the VM cluster, and ensure that the indicator monitoring system can still maintain efficient and continuous operation under high-traffic pressure, avoiding service interruptions due to resource exhaustion.

[0097] Figure 6 Flow chart of another embodiment of the management method of the indicator monitoring system disclosed in the present invention; this embodiment takes how to handle the traffic forwarding strategy adjustment event as an example for exemplary description, such as Figure 6 As shown, it includes the following steps 601 to 602. Each step is described below.

[0098] In step 601, in response to the operation and maintenance triggering event being a traffic forwarding strategy adjustment event, an adjusted traffic forwarding strategy is determined based on the traffic forwarding strategy adjustment event.

[0099] The traffic forwarding policy adjustment event is used to indicate an event in which a VMStorage cluster to which the indicator monitoring data of the writing end is to be written changes.

[0100] In some embodiments, when the traffic forwarding gateway determines that the amount of data written to one or some VM clusters is too large based on the amount of data written to each VM cluster in the current time period, it can report a traffic forwarding policy adjustment event to the operation and maintenance management platform so that the operation and maintenance management platform can adjust the traffic forwarding policy based on the event and balance the load.

[0101] In other implementations, when the operation and maintenance management platform monitors the indicator monitoring system in real time, it can also determine the usage of the corresponding VM cluster based on the amount of write data of each VM cluster on the host machine. When the amount of write data of one or some VM clusters is too large, the traffic forwarding strategy can be automatically adjusted.

[0102] In other embodiments, when a task of monitoring equipment in a new computer room is added to the indicator monitoring system and a corresponding VM cluster is created to store indicator monitoring data, the operation and maintenance management platform can adjust the traffic forwarding strategy and add a forwarding strategy for writing to the newly created VM cluster.

[0103] In step 602, the adjusted traffic forwarding policy is sent to the traffic forwarding gateway in the indicator monitoring system.

[0104] The adjusted traffic forwarding strategy is used by the traffic forwarding gateway to write the received indicator data obtained by each data writing end into the corresponding data storage end. After the traffic forwarding strategy adjustment event occurs and the traffic forwarding strategy is adjusted, the adjusted traffic forwarding strategy can be sent to the traffic forwarding gateway through the K8s interface, so that the traffic forwarding gateway can subsequently write the data of the writing end into the corresponding VM cluster according to the adjusted traffic forwarding strategy.

[0105] The above steps 601 to 602 disclose that when a traffic forwarding policy adjustment event occurs, the traffic forwarding policy is automatically adjusted to flexibly control the data flow, ensure that the indicator monitoring data is efficiently written to the corresponding VM cluster, and improve the flexibility of traffic management.

[0106] Corresponding to the embodiment of the management method of the indicator monitoring system described above, the present disclosure also provides an embodiment of the management device of the indicator monitoring system corresponding to the embodiment.

[0107] Exemplary Devices

[0108] Figure 7 FIG. 1 is a schematic diagram of a structure of an embodiment of a management device of an indicator monitoring system disclosed in the present invention. The device is applied to an electronic device (such as a computer system or a server). Figure 7 As shown, the device comprises:

[0109] An event acquisition module 71 is used to acquire operation and maintenance triggering events of the indicator monitoring system in a preset manner;

[0110] The type determination module 72 is used to determine the event type of the operation and maintenance triggering event.

[0111] The operation and maintenance processing module 73 is used to perform operation and maintenance processing corresponding to the event type of the operation and maintenance triggering event on the indicator monitoring system.

[0112] Figure 8 FIG. 1 is a structural diagram of another embodiment of the management device of the indicator monitoring system disclosed in the present invention. Figure 8 As shown, in Figure 7 Based on the illustrated embodiment, in some optional implementation manners, the method further includes:

[0113] The system deployment module 74 is used to respond to receiving a system deployment operation triggered by a user through an interface, and based on the system deployment operation, containerize and deploy each monitoring component in the indicator monitoring system, wherein the monitoring components include at least one of the following: an indicator data capture component, an indicator data insertion component, an indicator data storage component, and an indicator data query component.

[0114] In some optional embodiments, the method further comprises:

[0115] The data backup module 75 is used to remotely back up the data stored in the indicator data storage component to the network storage server according to a preset period.

[0116] In some optional implementations, the event acquisition module 71 is used to acquire operation and maintenance triggering events of the indicator monitoring system through the container interface and container resource utilization information of each monitoring component.

[0117] In some optional implementations, the event acquisition module 71 includes:

[0118] The receiving submodule 711 is used to receive the operation and maintenance triggering event reported by the indicator monitoring system; or,

[0119] The monitoring submodule 712 is used to monitor the component status of each monitoring component in the indicator monitoring system in real time to obtain the operation and maintenance triggering events of the indicator monitoring system.

[0120] In some optional implementations, the operation and maintenance processing module 73 includes:

[0121] A first determination submodule 731 is configured to determine a failed host machine in response to the operation and maintenance triggering event being a host machine failure event, based on the host machine failure event;

[0122] The first processing submodule 732 is used to set the state of the failed host machine to an unschedulable state, and perform an eviction operation on the running instance deployed on the host machine.

[0123] In some optional implementations, the operation and maintenance processing module 73 includes:

[0124] The second determination submodule 733 is used to determine the type of monitoring component to be expanded based on the expansion event in response to the operation and maintenance triggering event being an expansion event;

[0125] The second processing submodule 734 is used to add a monitoring component instance consistent with the monitoring component type.

[0126] In some optional implementations, the operation and maintenance processing module 73 includes:

[0127] The third determination submodule 735 is configured to determine an adjusted traffic forwarding strategy based on the traffic forwarding strategy adjustment event in response to the operation and maintenance triggering event being a traffic forwarding strategy adjustment event;

[0128] The third processing submodule 736 is used to send the adjusted traffic forwarding strategy to the traffic forwarding gateway in the indicator monitoring system. The adjusted traffic forwarding strategy is used by the traffic forwarding gateway to write the indicator data received by each data writing end into the corresponding data storage end.

[0129] The modules and units in the device disclosed in the present invention can also be divided into finer granularity according to actual needs, and can be specifically set according to actual needs.

[0130] The device of the embodiment of the present disclosure can be used to implement the methods of the above-mentioned embodiments of the present disclosure. The two correspond to each other in specific implementation, and the specific implementations of related parts are referenced to each other, which will not be repeated here.

[0131] Exemplary systems, electronic devices, computer program products, and computer-readable storage media

[0132] The disclosed embodiment also provides a management system for an indicator monitoring system, the system comprising an indicator monitoring system and a management device for the above-mentioned indicator monitoring system; wherein the indicator monitoring system comprises: at least one data writing end, at least one data storage end and a traffic forwarding gateway; the management device for the indicator system is used to obtain operation and maintenance triggering events of the indicator monitoring system in a preset manner; based on the operation and maintenance triggering events, perform corresponding operation and maintenance processing on the indicator monitoring system, the operation and maintenance processing including at least one of the following: monitoring component failure migration, monitoring component expansion, and adjustment of monitoring data forwarding strategy.

[0133] An embodiment of the present disclosure further provides an electronic device, comprising: a memory for storing a computer program; a processor for executing the computer program stored in the memory, and when the computer program is executed, the management method of the indicator monitoring system described in any of the above embodiments of the present disclosure is implemented.

[0134] Below, reference Fig. 9 An electronic device according to an embodiment of the present disclosure is described, in which a device for implementing the method according to an embodiment of the present disclosure may be integrated. Fig. 9 A structural diagram of an electronic device provided in an exemplary embodiment of the present disclosure, such as Fig. 9 As shown, the electronic device includes one or more processors 91, one or more computer-readable storage media memory 92, and a computer program stored in the memory and executable on the processor. When executing the program in the memory 92, the management method of the indicator monitoring system described above can be implemented.

[0135] Specifically, in practical applications, the electronic device may further include components such as an input device 93 and an output device 94, and these components are interconnected via a bus system and / or other forms of connection mechanisms (not shown). Those skilled in the art will appreciate that Fig. 9The structure of the electronic device shown in the figure does not constitute a limitation of the electronic device, and may include more or less components than shown in the figure, or certain components, or different component arrangements.

[0136] in:

[0137] The processor 91 can be a central processing unit (CPU) or other forms of processing units with management capabilities and / or instruction execution capabilities of the indicator monitoring system. It performs various functions and processes data by running or executing software programs and / or modules stored in the memory 92, and calling data stored in the memory 92, thereby monitoring the electronic device as a whole.

[0138] The memory 92 may include one or more computer program products, and the computer program product may include various forms of computer-readable storage media, such as volatile memory and / or non-volatile memory. Volatile memory may include, for example, random access memory (RAM) and / or cache memory (cache), etc. Non-volatile memory may include, for example, read-only memory (ROM), hard disk, flash memory, etc. One or more computer program instructions may be stored on a computer-readable storage medium, and the processor 91 may run the program instructions to implement the management method of the indicator monitoring system of each embodiment of the present disclosure above and / or other desired functions. Various contents such as input signals, signal components, noise components, etc. may also be stored in the computer-readable storage medium.

[0139] The input device 93 can be used to receive input digital or character information, and generate keyboard, mouse, joystick, optical or trackball signal input related to user settings and function control.

[0140] The output device 94 can output various information to the outside, including the determined distance information, direction information, etc. The output device 94 can include, for example, a display, a speaker, a printer, a communication network and a remote output device connected thereto, and the like.

[0141] The electronic device may also include a power supply for supplying power to various components, which may be connected to the processor 91 functional module through a power management system, so as to manage charging, discharging, power consumption and other functions through the power management system. The power supply may also include any components such as one or more DC or AC power supplies, recharging systems, power failure detection circuits, power converters or inverters, and power status indicators.

[0142] Of course, to simplify, Fig. 9Only some of the components related to the present disclosure in the electronic device are shown, and components such as a bus, an input / output interface, etc. are omitted. In addition, according to specific application situations, the electronic device may further include any other appropriate components.

[0143] In addition to the above-mentioned methods and devices, an embodiment of the present disclosure may also be a computer program product, which includes computer program instructions, which, when executed by a processor, enable the processor to execute the steps of the management method of the indicator monitoring system according to various embodiments of the present disclosure described in the above-mentioned "Exemplary Method" section of this specification.

[0144] The computer program product may be written in any combination of one or more programming languages ​​to write program code for performing the operations of the disclosed embodiments, including object-oriented programming languages ​​such as Java, C++, etc., and conventional procedural programming languages ​​such as "C" or similar programming languages. The program code may be executed entirely on the user computing device, partially on the user device, as a separate software package, partially on the user computing device and partially on a remote computing device, or entirely on a remote computing device or server.

[0145] In addition, an embodiment of the present disclosure may also be a computer-readable storage medium having computer program instructions stored thereon, which, when executed by a processor, enable the processor to execute the steps of the management method of the indicator monitoring system according to various embodiments of the present disclosure described in the above “Exemplary Method” section of this specification.

[0146] The computer readable storage medium can adopt any combination of one or more readable media. The readable medium can be a readable signal medium or a readable storage medium. The readable storage medium can include, for example, but is not limited to, a system, device or device of electricity, magnetism, light, electromagnetic, infrared, or semiconductor, or any combination of the above. More specific examples (non-exhaustive list) of readable storage media include: an electrical connection with one or more wires, a portable 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.

[0147] The basic principles of the present disclosure are described above in conjunction with specific embodiments. However, it should be noted that the advantages, strengths, effects, etc. mentioned in the present disclosure are only examples and not limitations, and it cannot be considered that these advantages, strengths, effects, etc. are required by each embodiment of the present disclosure. In addition, the specific details disclosed above are only for the purpose of illustration and ease of understanding, and are not limitations. The above details do not limit the present disclosure to the necessity of adopting the above specific details to be implemented.

[0148] Each embodiment in this specification is described in a progressive manner, and each embodiment focuses on the differences from other embodiments. The same or similar parts between the embodiments can be referred to each other. For the system embodiment, since it basically corresponds to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment.

[0149] A person of ordinary skill in the art can understand that all or part of the steps of implementing the above method embodiment can be completed by hardware related to program instructions, and the aforementioned program can be stored in a computer-readable storage medium. When the program is executed, it executes the steps of the above method embodiment; and the aforementioned storage medium includes: ROM, RAM, magnetic disk or optical disk, etc., various media that can store program codes.

[0150] The method and apparatus of the present disclosure may be implemented in many ways. For example, the method and apparatus of the present disclosure may be implemented by software, hardware, firmware, or any combination of software, hardware, and firmware. The above order of steps for the method is for illustration only, and the steps of the method of the present disclosure are not limited to the order specifically described above, unless otherwise specifically stated. In addition, in some embodiments, the present disclosure may also be implemented as a program recorded in a recording medium, which includes machine-readable instructions for implementing the method according to the present disclosure. Therefore, the present disclosure also covers a recording medium storing a program for executing the method according to the present disclosure.

[0151] The description of the present disclosure is given for the purpose of illustration and description, and is not intended to be exhaustive or to limit the present disclosure to the disclosed form. Many modifications and variations will be apparent to those of ordinary skill in the art. The embodiments are selected and described in order to better illustrate the principles and practical applications of the present disclosure, and to enable those of ordinary skill in the art to understand the present disclosure and thereby design various embodiments with various modifications suitable for specific uses.

Claims

1. A management method for an indicator monitoring system, characterized in that: include: Obtain the operation and maintenance trigger events of the indicator monitoring system through the preset method; Determine the event type of the operation and maintenance triggering event; The operation and maintenance processing corresponding to the event type of the operation and maintenance triggering event is performed on the indicator monitoring system.

2. The method according to claim 1, characterized in that Before obtaining the operation and maintenance triggering event of the indicator monitoring system in a preset manner, the method further includes: In response to receiving a system deployment operation triggered by a user through an interface, each monitoring component in the indicator monitoring system is containerized and deployed based on the system deployment operation, and the monitoring component includes at least one of the following: an indicator data capture component, an indicator data insertion component, an indicator data storage component, and an indicator data query component.

3. The method according to claim 2, characterized in that Also includes: According to a preset period, the data stored in the indicator data storage component is remotely backed up to a network storage server.

4. The method according to any one of claims 1 to 3, characterized in that: The operation and maintenance triggering event of the indicator monitoring system is obtained by a preset method, including: Receive an operation and maintenance trigger event reported by the indicator monitoring system; or, The component status of each monitoring component in the indicator monitoring system is monitored in real time to obtain the operation and maintenance triggering event of the indicator monitoring system.

5. The method according to any one of claims 1 to 4, characterized in that: The performing operation and maintenance processing corresponding to the event type of the operation and maintenance triggering event on the indicator monitoring system includes: In response to the operation and maintenance triggering event being a host machine failure event, determining a host machine where the failure occurs based on the host machine failure event; The state of the failed host machine is set to an unschedulable state, and an eviction operation is performed on the running instance deployed on the host machine.

6. The method according to any one of claims 1 to 5, characterized in that: The performing operation and maintenance processing corresponding to the event type of the operation and maintenance triggering event on the indicator monitoring system includes: In response to the operation and maintenance triggering event being a capacity expansion event, determining the type of monitoring component to be expanded based on the capacity expansion event; Add a monitoring component instance that is consistent with the monitoring component type.

7. The method according to any one of claims 1 to 6, characterized in that: The performing operation and maintenance processing corresponding to the event type of the operation and maintenance triggering event on the indicator monitoring system includes: In response to the operation and maintenance triggering event being a traffic forwarding strategy adjustment event, determining an adjusted traffic forwarding strategy based on the traffic forwarding strategy adjustment event; The adjusted traffic forwarding strategy is sent to the traffic forwarding gateway in the indicator monitoring system, and the adjusted traffic forwarding strategy is used by the traffic forwarding gateway to write the indicator data received by each data writing end into the corresponding data storage end.

8. A management system for an indicator monitoring system, characterized in that: The system includes an indicator monitoring system and an operation and maintenance management platform for executing the management method of the indicator monitoring system according to any one of claims 1 to 7; Wherein, the indicator monitoring system includes: at least one data writing end, at least one data storage end and a traffic forwarding gateway; The management device of the indicator system is used to obtain the operation and maintenance triggering event of the indicator monitoring system in a preset manner; determine the event type of the operation and maintenance triggering event; and perform operation and maintenance processing corresponding to the operation and maintenance triggering event on the indicator monitoring system.

9. A computer-readable storage medium, characterized in that: The storage medium stores computer program instructions, and when the computer program instructions are executed, the method described in any one of claims 1 to 7 is implemented.

10. An electronic device, characterized in that: The electronic device comprises: a memory for storing a computer program product; A processor is used to execute the computer program product stored in the memory, and when the computer program product is executed, it implements the method described in any one of claims 1 to 7.

11. A computer program product comprising computer program instructions, characterized in that When the computer program instructions are executed by a processor, the method described in any one of claims 1 to 7 is implemented.

Images