Distributed deployment methods, devices and media for equipment monitoring

Abstract

This disclosure provides a distributed deployment method, apparatus, and medium for device monitoring, relating to the field of network technology. The method includes: obtaining an uncompressed package and multiple containers for installing device monitoring functions; the uncompressed package encapsulates basic functions for installing the device monitoring functions; each of the multiple containers is used to install a module function of the device monitoring functions; at a distributed node of the device monitoring system, the basic functions of the device monitoring functions are installed using the uncompressed package, and the multiple module functions of the device monitoring functions are installed using the multiple containers; the distributed node monitors several devices using the basic functions and the multiple module functions, and reports the monitoring data to the central node of the device monitoring system. This disclosure decomposes the device monitoring function into basic functions and multiple module functions, with each module function deployed through a container, facilitating the fulfillment of different monitoring deployment requirements for different devices.

Description

Technical Field

[0001] This disclosure relates at least to the field of network technology, and in particular to a distributed deployment method for device monitoring, a distributed deployment apparatus for device monitoring, and a computer-readable storage medium. Background Technology

[0002] With the rapid development of communication networks, operators face the challenges of increasingly complex network architectures and constantly changing user needs. Against this backdrop, deploying network management systems has become an inevitable choice. Modern communication networks encompass multiple technologies such as 5G (5th Generation Mobile Communication Technology), IoT (Internet of Things), and cloud computing. The convergence of these technologies makes network management more complex, and current management methods for these complex networks are not ideal. Summary of the Invention

[0003] The technical problem to be solved by this disclosure is to address the above-mentioned shortcomings by providing a distributed deployment method, a distributed deployment device, and a computer-readable storage medium for device monitoring, so as to solve the problem of how to achieve real-time control of network status through centralized monitoring and management of various network devices.

[0004] Firstly, this disclosure provides a distributed deployment method for device monitoring.

[0005] The methods include:

[0006] Obtain an unzipped package and multiple containers for installing the device monitoring function. The unzipped package encapsulates the basic functions for installing the device monitoring function, and each of the multiple containers is used to install a module function of the device monitoring function.

[0007] The basic functions of the equipment monitoring function are installed at a certain distributed node of the equipment monitoring system through the decompression package, and multiple module functions of the equipment monitoring function are installed through the multiple containers.

[0008] The distributed node monitors several devices through the basic functions and the multiple module functions, and reports the monitoring data to the central node of the device monitoring system.

[0009] Furthermore, among which:

[0010] The basic functions include:

[0011] The communication capability is specifically implemented by configuring a communication protocol and routing table for transmitting the monitoring data to the distributed node.

[0012] The data management function specifically includes the local storage function of the monitoring data of a certain distributed node and the reconciliation function of the monitoring data between the certain distributed node and the central node;

[0013] The functions of the multiple modules include any of the following:

[0014] The hardware monitoring function is used to monitor the online status and hardware performance parameters of the aforementioned devices.

[0015] Configure monitoring functionality to monitor the configuration files and configuration change operations of the aforementioned devices.

[0016] The security monitoring function is used to monitor user authentication activities of the aforementioned devices and collect device logs.

[0017] The routing monitoring function is used to monitor routing protocol issues and routing security events of the aforementioned devices.

[0018] The traffic monitoring function is used to monitor the traffic and traffic security events of each interface of the aforementioned devices.

[0019] The service monitoring function is used to monitor the network resources on which the services of the aforementioned devices depend.

[0020] Furthermore, the method also includes:

[0021] In response to the need to modify a certain module function among the multiple module functions, the container of the modified module function is obtained, and the modified container is used to replace the corresponding container before the modification at a certain distribution node to realize the modification operation of the module function.

[0022] Furthermore, the method specifically includes:

[0023] The central node will deploy device monitoring functions to a certain distributed node, which are divided into basic functions and multiple module functions. The basic functions are encapsulated into an unzipped package, and the multiple module functions are each encapsulated into a container.

[0024] The central node sends the decompressed package and the multiple containers to the distributed node, so that the distributed node can install the basic functions through the decompressed package and install the multiple module functions through the multiple containers;

[0025] The central node receives monitoring data from a certain distributed node, which is obtained by the distributed node through the basic functions and the multiple module functions to monitor several devices;

[0026] In response to a request to modify the functionality of a module, the central node obtains the container of the modified module and several distributed nodes that distribute the module functionality, and sends the modified container to the distributed nodes so that the distributed nodes can replace the corresponding container before the modification with the modified container.

[0027] Furthermore, the method also includes:

[0028] In response to the monitoring of a new device accessing the system, the central node obtains the device information of the new device, selects a deployment strategy corresponding to the device information, the deployment strategy includes selecting a distribution node for monitoring the new device and the device monitoring function to be deployed to the distribution node for monitoring the new device, and establishes a connection with the distribution node via the Secure Shell protocol SSH. The SSH is used to send the decompressed package and the multiple containers to the distribution node, and obtain the installation progress of the decompressed package and the multiple containers on the distribution node.

[0029] Furthermore, among which:

[0030] The device information includes: device type information, device model information, network performance parameters, network topology information, and hardware and software resource information of the new device;

[0031] The deployment strategy is determined by the central node: either automatically selecting a deployment strategy pre-configured by the network administrator through a visual interface based on the device information, or displaying the device information to the network administrator through a visual interface and receiving the deployment strategy selected by the network administrator based on the device information;

[0032] The device monitoring function includes: the number and version of multiple module functions selected based on device type information and device model information, and the communication protocol, routing table and transmission cycle selected based on network performance parameters, network topology information and hardware and software resource information for transmitting the monitoring data to the central node.

[0033] Furthermore, the method specifically includes:

[0034] A distributed node receives a decompressed package and multiple containers from a central node. The decompressed package encapsulates basic functions for installing device monitoring functions, and each of the multiple containers is used to install a module function of the device monitoring function.

[0035] The distributed node installs the basic functions of device monitoring on itself through the decompressed package, and installs multiple module functions of device monitoring on itself through the multiple containers.

[0036] The distributed node monitors several devices and obtains monitoring data through the basic functions and the multiple module functions, and reports the monitoring data to the central node.

[0037] The distributed node receives a modified container from the central node and replaces the corresponding container before the modification with the modified container to realize the modification operation of a certain module function among the multiple module functions.

[0038] Furthermore, the monitoring of several devices is achieved through the basic functions and the functions of the multiple modules to obtain monitoring data, and the monitoring data is reported to the central node, specifically including:

[0039] The multiple modules are used to monitor several devices and obtain any number of hardware monitoring data, configuration monitoring data, security monitoring data, routing monitoring data, traffic monitoring data, and service monitoring data for each device.

[0040] The basic functions determine the transmission cycle of the monitoring data reported to the central node, store the monitoring data within one transmission cycle locally, and delete the locally stored monitoring data after reconciling the monitoring data with the central node.

[0041] Secondly, this disclosure provides a distributed deployment device for device monitoring, the device comprising:

[0042] The decomposition module is used to obtain an unzipped package and multiple containers for installing the equipment monitoring function. The unzipped package encapsulates the basic functions for installing the equipment monitoring function, and each of the multiple containers is used to install a module function of the equipment monitoring function.

[0043] The installation module, connected to the decompression module, is used to install the basic functions of the equipment monitoring function at a certain distributed node of the equipment monitoring system through the decompression package, and to install multiple module functions of the equipment monitoring function through the multiple containers.

[0044] The monitoring module, connected to the installation module, is used by the distributed node to monitor several devices through the basic functions and the functions of the multiple modules, and to report the monitoring data to the central node of the device monitoring system.

[0045] Thirdly, this disclosure provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the distributed deployment method for device monitoring as described above.

[0046] This disclosure provides a distributed deployment method, a distributed deployment device, and a computer-readable storage medium for device monitoring. The device monitoring function is decomposed into basic functions and multiple module functions. The basic functions are deployed in a unified environment, and each module function is deployed through a container. This facilitates meeting the different monitoring deployment requirements of different devices, and can improve deployment efficiency and reduce deployment costs. Attached Figure Description

[0047] Figure 1 This is a flowchart of a distributed deployment method for device monitoring according to an embodiment of this disclosure;

[0048] Figure 2 This is a flowchart of another distributed deployment method for device monitoring according to an embodiment of this disclosure;

[0049] Figure 3 This is a flowchart of a distributed deployment method for device monitoring in accordance with an embodiment of this disclosure, targeting the network access of new devices;

[0050] Figure 4 This is a flowchart of a distributed deployment method for device monitoring based on AirFlow DAG, according to an embodiment of this disclosure;

[0051] Figure 5 This is a flowchart of a maintenance method for a distributed deployment of device monitoring according to an embodiment of this disclosure;

[0052] Figure 6 This is a schematic diagram of the structure of a distributed deployment device for device monitoring according to an embodiment of the present disclosure. Detailed Implementation

[0053] To enable those skilled in the art to better understand the technical solutions of this disclosure, the embodiments of this disclosure will be further described in detail below with reference to the accompanying drawings.

[0054] It is understood that the specific embodiments and accompanying drawings described herein are for illustrative purposes only and are not intended to limit the scope of this disclosure.

[0055] It is understood that, without conflict, the various embodiments and features in the embodiments of this disclosure can be combined with each other.

[0056] It is understood that, for ease of description, only the parts relevant to this disclosure are shown in the accompanying drawings, while parts unrelated to this disclosure are not shown in the drawings.

[0057] It is understood that each module or unit involved in the embodiments of this disclosure may correspond to only one entity structure, or may be composed of multiple entity structures, or multiple modules or units may be integrated into one entity structure.

[0058] It is understood that, without conflict, the functions and steps marked in the flowcharts and block diagrams of this disclosure may occur in a different order than that marked in the accompanying drawings.

[0059] It is understood that the flowcharts and block diagrams of this disclosure illustrate the architecture, functions, and operations of possible implementations of systems, apparatuses, devices, and methods according to various embodiments of this disclosure. Each block in a flowchart or block diagram may represent a module, unit, program segment, or code, containing executable instructions for implementing the specified function. Furthermore, each block or combination of blocks in the block diagrams and flowcharts may be implemented using a hardware-based system to implement the specified function, or using a combination of hardware and computer instructions.

[0060] It is understood that the modules and units involved in the embodiments of this disclosure can be implemented by software or by hardware, for example, the modules and units can be located in a processor.

[0061] Example 1:

[0062] like Figure 1 As shown, this disclosure provides a distributed deployment method for device monitoring, the method comprising:

[0063] S1. Obtain an unzipped package and multiple containers for installing the device monitoring function. The unzipped package encapsulates the basic functions for installing the device monitoring function, and each of the multiple containers is used to install a module function of the device monitoring function.

[0064] S2. At a certain distributed node of the equipment monitoring system, the basic functions of the equipment monitoring function are installed through the decompression package, and multiple module functions of the equipment monitoring function are installed through the multiple containers.

[0065] S3. The distributed node monitors several devices through the basic functions and the multiple module functions, and reports the monitoring data to the central node of the device monitoring system.

[0066] In this embodiment, the method decomposes the device monitoring function into basic functions and multiple module functions. The basic functions are deployed in a unified environment, and each module function is deployed in its own container. This facilitates meeting the different monitoring deployment requirements of different devices, thereby improving deployment efficiency and reducing deployment costs.

[0067] More specifically, this embodiment provides a distributed deployment and maintenance method for an equipment monitoring system, including providing a network management system that centrally monitors and manages various network devices to achieve real-time control of network status and ensure efficient fault handling and performance optimization.

[0068] This embodiment provides a distributed system architecture design, emphasizing the characteristics of universal monitoring functionality, high throughput, and low latency. The system adopts a distributed architecture, achieving comprehensive monitoring of network devices through the collaborative work of a central node and various monitoring nodes (distributed nodes). This system architecture abandons the traditional distributed system task upload process, where the master node (control node) uploads tasks and data, and worker nodes execute them. Instead, it adopts a deployment-assignment approach, assigning tasks to corresponding modules simultaneously with the deployment of functional modules on the nodes.

[0069] The deployment process in this embodiment is as follows: Figure 2 As shown, the process includes the following steps: preparing the deployment environment and creating the monitoring module (this step can be done by the network administrator). The monitoring module is configured differently for different devices to be monitored. Deploying the central node and storing all module data, the central node can encapsulate the module data into containers. When deploying, the corresponding container combination can be selected to obtain different monitoring functions for different devices. Scanning the network environment and establishing network and permissions for the pre-deployed devices. Completing the deployment of the monitoring node and starting to execute monitoring tasks. The same module function may have different versions and monitoring content for different devices, so the data content collected by each container may be different for different devices.

[0070] Unlike traditional distributed worker nodes, the monitoring nodes in this embodiment are tasked with a streamlined process of automatically collecting, identifying, and monitoring data from network devices, and then reporting the data to the central node. Traditional nodes operate by receiving and executing commands, while the monitoring nodes (distributed nodes) in this embodiment execute relevant monitoring tasks independently based on their configuration, no longer receiving monitoring collection commands for each instance.

[0071] The central node in this embodiment is not the control node of a traditional distributed system. Traditional control nodes mainly issue commands and transmit data. The central node in this embodiment is responsible for the management and control of node deployment and the reception of monitoring data. The management and control of monitoring nodes is carried out by issuing new configuration files.

[0072] In one embodiment, wherein:

[0073] The basic functions include:

[0074] The communication capability is specifically implemented by configuring a communication protocol and routing table for transmitting the monitoring data to the distributed node.

[0075] The data management function specifically includes the local storage function of the monitoring data of a certain distributed node and the reconciliation function of the monitoring data between the certain distributed node and the central node;

[0076] The functions of the multiple modules include any of the following:

[0077] The hardware monitoring function is used to monitor the online status and hardware performance parameters of the aforementioned devices.

[0078] Configure monitoring functionality to monitor the configuration files and configuration change operations of the aforementioned devices.

[0079] The security monitoring function is used to monitor user authentication activities of the aforementioned devices and collect device logs.

[0080] The routing monitoring function is used to monitor routing protocol issues and routing security events of the aforementioned devices.

[0081] The traffic monitoring function is used to monitor the traffic and traffic security events of each interface of the aforementioned devices.

[0082] The service monitoring function is used to monitor the network resources on which the services of the aforementioned devices depend.

[0083] In this embodiment, the following preparations must be made before deployment:

[0084] Configure unified functions and divide functions for nodes: In conjunction with the architecture design of the network management system, the system configuration is unified and the functions of nodes are divided to clarify the specific configuration details of each network device at the system level during deployment and configuration. The structure to be deployed is divided into two parts: basic functions and module functions.

[0085] The basic functionalities include two functions: communication and storage.

[0086] Communication capability: This enables distributed nodes to have network connectivity, establishing stable network connections with other nodes, meeting inter-node communication requirements, and exchanging data, coordinating tasks, and synchronizing states. Communication capability refers to the ability of each monitoring module in the distributed nodes to transmit data to the central node. This is primarily achieved through configuration of communication protocols such as TCP / IP (Transmission Control Protocol / Internet Protocol). Before deployment, the communication network between each node is established; during deployment, this capability is implemented through routing table configuration.

[0087] Data storage and management capabilities: As nodes in a distributed system, each node possesses local storage capabilities to store its own status data and node data, while ensuring data consistency and guaranteeing strong consistency across all nodes. Status data includes node runtime, node data throughput, and node logs. Node data includes data obtained by the monitoring node from monitoring devices, such as device temperature changes and device logs. Ensuring data consistency is achieved through "data reconciliation" between the central node and the monitoring nodes; this involves periodically checking whether the data exchanged between the two is consistent. Furthermore, the monitoring node's data transmission has a rollback mechanism; if the transmission process is interrupted, the transmitted data is deleted, and the node is required to retransmit new data.

[0088] The above implements the basic functions of a node (distributed node). During deployment, the above functions will be deployed using a unified configuration decompression package deployment method to ensure the basic data interaction capabilities of each device (i.e., a unified deployment environment for each node).

[0089] Module functions are functional modules divided according to the specific needs of the monitoring content, in order to meet the functional requirements of monitoring nodes on various network devices. Based on function, they can be specifically divided into the following categories:

[0090] Hardware monitoring module: Monitors the online status and related performance of network devices, such as online status, CPU (Central Processing Unit) utilization, memory usage, temperature, etc.

[0091] Configure the monitoring module: ensure regular backup and integrity of configuration files, monitor configuration changes to network devices, and record changes such as content, time, and user, to meet compliance requirements.

[0092] Security monitoring module: Monitors user authentication activities on network devices, including successful logins, failed logins, abnormal logins, user authorization, and access control. It also collects various device logs to provide data for device security audits and vulnerability investigations.

[0093] The routing monitoring module monitors the operational status, neighbor relationships, and routing tables of network devices' routing protocols (such as OSPF (Open Shortest Path First) and BGP (Border Gateway Protocol)) to promptly detect routing problems. It also monitors routing-related security events such as route hijacking and route leakage.

[0094] Traffic monitoring module: Monitors the status and traffic data of each interface of network devices, and understands the traffic usage of different applications or services. It obtains the device's QoS (Quality of Service) policy and monitors related security events such as abnormal traffic detection and DDoS (Distributed Denial of Service) attacks.

[0095] Business monitoring module: For critical business systems or applications, monitor the availability, performance, and security of their network-dependent resources to ensure continuous business operation. It analyzes the network call chains and dependencies of business systems to achieve end-to-end network performance and fault monitoring, quickly pinpointing the root cause of problems.

[0096] Different network devices have different monitoring needs. For example, servers and high-performance switches require temperature monitoring, while downstream routers and low-power routers do not. Apart from business servers, most network devices do not require business monitoring modules.

[0097] It is important to note that the module division is only a module planning for functions, while some monitoring may have different versions depending on the equipment requirements. For example, data center equipment requires more precise hardware operating parameters, and Huawei and Cisco routers have different configuration methods. Different deployments mainly affect the level of detail in the collected data. For example, normal hardware monitoring only needs to collect hardware operating status, while data center hardware monitoring requires details such as the duration of high-intensity hardware operation and changes in throughput data.

[0098] The above are the main implementation modules of the system's monitoring function. Unlike the deployment method of the basic functions, these monitoring modules are deployed in a containerized manner. Each module will be encapsulated into a container and deployed to the monitoring node. Each module will have a container.

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

[0100] In response to the need to modify a certain module function among the multiple module functions, the container of the modified module function is obtained, and the modified container is used to replace the corresponding container before the modification at a certain distribution node to realize the modification operation of the module function.

[0101] In this embodiment, the purpose of modularizing and encapsulating the device monitoring function into containers is to reduce the workload of subsequent maintenance work, improve system security, and enable the immediate location of the corresponding functional module's mounting node in the event of system changes or vulnerability remediation, allowing maintenance operations to be performed even when the system's exposure surface is small. Specifically, the modules of each node are recorded at the central node. After transmitting the latest version of the module to the monitoring node that has the corresponding module, the node will directly delete the old container and related module information according to the script, and the new module will directly overwrite and replace the functions of the old module.

[0102] In one embodiment, the method specifically includes:

[0103] The central node will deploy device monitoring functions to a certain distributed node, which are divided into basic functions and multiple module functions. The basic functions are encapsulated into an unzipped package, and the multiple module functions are each encapsulated into a container.

[0104] The central node sends the decompressed package and the multiple containers to the distributed node, so that the distributed node can install the basic functions through the decompressed package and install the multiple module functions through the multiple containers;

[0105] The central node receives monitoring data from a certain distributed node, which is obtained by the distributed node through the basic functions and the multiple module functions to monitor several devices;

[0106] In response to a request to modify the functionality of a module, the central node obtains the container of the modified module and several distributed nodes that distribute the module functionality, and sends the modified container to the distributed nodes so that the distributed nodes can replace the corresponding container before the modification with the modified container.

[0107] In this embodiment, the deployment process may specifically include the deployment of a central management node and distributed monitoring nodes, which can be described separately from both sides. For the central node side, the deployment process executed by the central management node is implemented using an integrated installation package, which encapsulates all required software and configurations and writes execution scripts, enabling fully offline deployment. The specific process includes:

[0108] Scan the deployed devices to ensure the server has sufficient CPU, memory, storage, and network bandwidth resources to support the normal operation of the network management system. The operating system should be hardened and optimized for security: disable unnecessary services, configure firewall rules, and open necessary ports.

[0109] After the operating system configuration is complete, the offline management system is deployed. Based on the data storage and application service requirements of the network management system, pre-made storage devices (media can be external hard drives, USB flash drives, etc.) are connected to the node hardware to complete the installation and configuration of the database, middleware software, and system.

[0110] Log in to the management system, configure account permissions, import licenses (certificates), and complete the management system initialization. Install the master versions of each monitoring module from the installation package into the management system. Then, manage and control the versions, patches, and updates of each monitoring module within the management system.

[0111] After the central management node is configured, it begins connecting to various devices within the network and deploying monitoring nodes. The deployment of monitoring nodes does not require manual access to the hosts and operating systems of individual devices. It only requires granting remote management permissions to the management node after network access. Remote management is achieved via SSH (Secure Shell) and Telnet, and by opening specific ports on the monitoring nodes to the central node's IP address and access permissions. Configuration is completed by the access personnel when the monitoring nodes join the central node system.

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

[0113] In response to the monitoring of a new device accessing the system, the central node obtains the device information of the new device, selects a deployment strategy corresponding to the device information, the deployment strategy includes selecting a distribution node for monitoring the new device and the device monitoring function to be deployed to the distribution node for monitoring the new device, and establishes a connection with the distribution node via the Secure Shell protocol SSH. The SSH is used to send the decompressed package and the multiple containers to the distribution node, and obtain the installation progress of the decompressed package and the multiple containers on the distribution node.

[0114] In this embodiment, the central node provides rich monitoring metrics and real-time monitoring panels, offering a visual presentation platform for data parameters adapted to various network devices. It also supports customized monitoring views and layouts, enabling multi-dimensional data display and correlation analysis. As the direct responsible unit for connecting to the monitoring nodes, the central node is endowed with the functions of deploying, operating, maintaining, and deactivating the monitoring nodes. Specific functions include:

[0115] Data aggregation and storage: The central node receives monitoring data reported by the monitoring nodes and stores it in a centralized database to form a complete record of historical monitoring data, providing a foundation for subsequent data analysis and mining.

[0116] Data Analysis and Visualization: The central node provides a wealth of data analysis and visualization tools, such as real-time performance monitoring, historical data trend analysis, and correlation analysis, to help network administrators extract valuable information from massive amounts of monitoring data and discover abnormal network behavior and potential risks.

[0117] Automatic device discovery and identification: The central node automatically discovers newly connected network devices and obtains basic device information, such as device type, model, and IP address, through network protocols such as CDP (Cisco Discovery Protocol) and LLDP (Link Layer Discovery Protocol). Newly connected devices are required to grant access permissions to the central node (the central node needs to be able to communicate with all managed devices on the network) to facilitate subsequent policy deployment processes.

[0118] Automatic deployment of monitoring nodes:

[0119] Deployment strategy management: Allows network administrators to predefine deployment strategies for monitoring nodes of different types of devices, including installation package selection, configuration parameters, deployment progress and system status monitoring. In addition to automatically generating strategies, the central node also provides a visual deployment strategy management interface, allowing administrators to manually configure deployment strategies, such as adding more monitoring modules or modifying data upload frequency.

[0120] Device adaptation and compatibility check: Based on the type and model of newly discovered devices, the central node automatically selects a compatible monitoring node installation package and configuration template, and submits it to the available options in the platform's deployment policy management for review by deployment personnel. This process ensures deployment compatibility and stability.

[0121] Remote installation and configuration: After the deployment strategy is determined, the central node establishes a connection with the newly discovered device via the SSH security protocol, automatically executes the installation and configuration scripts of the monitoring node, and completes the deployment process of the monitoring node.

[0122] Deployment status tracking: The central node's management platform tracks the deployment status of monitoring nodes in real time, i.e., the deployment task flow, including installation progress, configuration results, startup status, etc., and automatically includes the newly deployed monitoring nodes in the management scope after deployment is completed. The progress status will be uploaded to the central management node.

[0123] By adding the ability to automatically deploy monitoring nodes to the central management node, the network management system can achieve rapid coverage of monitoring capabilities, reducing the workload of network administrators. When a new network device is connected to the network, the central management node can automatically discover and deploy monitoring nodes on the device. Even personnel without system operation experience can complete the monitoring deployment for a single node based on a visualized strategy, greatly improving the efficiency and scalability of network monitoring.

[0124] This automated deployment capability also enhances the intelligence level of the network management system. Through predefined deployment strategies and automated processes, it achieves standardized and regulated deployment of monitoring nodes, reducing human error and configuration deviations, and ensuring the accuracy and consistency of monitoring data. The core purpose of this monitoring-centric architecture design is to comprehensively improve the efficiency and quality of network management, and reduce the incidence and scope of network failures caused by manual deployment issues.

[0125] In one embodiment, wherein:

[0126] The device information includes: device type information, device model information, network performance parameters, network topology information, and hardware and software resource information of the new device;

[0127] The deployment strategy is determined by the central node: either automatically selecting a deployment strategy pre-configured by the network administrator through a visual interface based on the device information, or displaying the device information to the network administrator through a visual interface and receiving the deployment strategy selected by the network administrator based on the device information;

[0128] The device monitoring function includes: the number and version of multiple module functions selected based on device type information and device model information, and the communication protocol, routing table and transmission cycle selected based on network performance parameters, network topology information and hardware and software resource information for transmitting the monitoring data to the central node.

[0129] In this embodiment, the following preparations must be made before deployment:

[0130] Network environment survey: Whether building a new network or adding new equipment to the network, a survey and assessment of the current network environment must be conducted before the deployment process begins. This involves collecting information on device types and quantities, network performance and bandwidth, and updating the network topology to provide a basis for developing a deployment plan.

[0131] Hardware and software resource preparation: Estimate the required hardware resources based on the scale of the network equipment to be deployed and the monitoring function requirements, ensuring that the hardware performance and capacity meet the system's operational requirements. Prepare the necessary software environment, including the operating system, database, and middleware, selecting versions compatible with the network management system, and performing necessary security hardening and optimization configurations.

[0132] Network connectivity testing and security planning: This includes testing network connectivity between devices to ensure that network bandwidth, latency, and packet loss rate meet system communication requirements. Based on the organization's security policy and the security requirements of the network management system, corresponding security strategies are developed. These strategies primarily include access control, data encryption, firewall rules, disaster recovery, and backup. Specific methods for developing these security strategies include: setting access keys, encrypting sensitive data, configuring firewall inbound and outbound rules, and customizing backup and data recovery strategies.

[0133] The specific deployment process is as follows: Figure 3 As shown, the process includes: after a device joins the network, the central node obtains the device information, acquires a deployment strategy based on the device information, adds modules (containers, including module functions corresponding to the device) according to the strategy, determines the monitoring modules and component versions, and judges whether they meet the node requirements. If they do not meet the requirements, the network administrator manually adds modules through a visual interface until the requirements are met. Then, the corresponding deployment process is generated and executed, the deployment feedback from the monitoring node is received, and the deployment success is judged. If it fails, the technical personnel are contacted for handling. If it succeeds, the deployment is completed and the operation begins, that is, the monitoring node performs monitoring and reports monitoring data to the central node.

[0134] The deployment process can be implemented using a scanning program based on the Python Paramiko library (a module for performing remote operations in Python). The management system will scan devices in the current network, identify newly connected network devices, and obtain basic device information. Based on this information, it will provide a solution for deploying the appropriate monitoring modules. For example, if a PowerEdge R750 device joins the network and is identified as a Dell rack server, the system solution would provide suitable hardware for Dell devices, such as iDRAC (Integrated Dell Remote Access Controller, an embedded hardware component in Dell servers) and OMSA (OpenManage Server Administrator, a tool included with Dell servers), along with the configuration of the monitoring system and the corresponding API (Application Programming Interface). Devices from HP, Huawei, and Cisco also have dedicated custom monitoring software, and the database will contain the appropriate versions and corresponding monitoring data acquisition port configurations.

[0135] Security monitoring administrators can adjust the number and version of modules on the management platform according to actual needs. Once finalized, the management system will uniformly package and encapsulate the modules, calling Airflow to execute Python task flows and combining it with the Paramiko library to generate deployment events. Shell commands are transmitted via Paramiko, remotely and automatically leading the deployment of monitoring nodes and providing feedback on deployment results. Each deployment command is placed within the Airflow task flow to achieve automated, step-by-step deployment. The specific DAG (Directed Acyclic Graph) is as follows: Figure 4 As shown, the deployment process in this mode can be described as including: Event 1: Deploy the unified environment and provide feedback; Event 2: Transmit the monitoring module; Event 3: Execute the decompression and deployment module; Event 4: Update the monitoring configuration file and provide feedback; Event 5: Update the network device status; Event 6: Start the monitoring module and provide feedback on the startup result.

[0136] In one embodiment, the method specifically includes:

[0137] A distributed node receives a decompressed package and multiple containers from a central node. The decompressed package encapsulates basic functions for installing device monitoring functions, and each of the multiple containers is used to install a module function of the device monitoring function.

[0138] The distributed node installs the basic functions of device monitoring on itself through the decompressed package, and installs multiple module functions of device monitoring on itself through the multiple containers.

[0139] The distributed node monitors several devices and obtains monitoring data through the basic functions and the multiple module functions, and reports the monitoring data to the central node.

[0140] The distributed node receives a modified container from the central node and replaces the corresponding container before the modification with the modified container to realize the modification operation of a certain module function among the multiple module functions.

[0141] In this embodiment, the deployment process is described from the perspective of the distributed nodes, corresponding to the deployment process described from the perspective of the central node. First, the communication protocol and related components are unified on the monitoring nodes. The system deploys a unified version of the communication protocol on the monitoring nodes and completes data storage and module deployment space allocation. After receiving the encapsulated data packets on the operating system of the deployment device, it decompresses and deploys them according to commands, overwrites configuration files, and locks permissions. All changes related to the monitoring nodes are controlled by the central node. After the node deployment is complete, it reports the deployment results to the central node, and the monitoring module begins its monitoring operation.

[0142] In one embodiment, the monitoring of several devices is achieved through the basic functions and the functions of the multiple modules to obtain monitoring data, and the monitoring data is reported to the central node, specifically including:

[0143] The multiple modules are used to monitor several devices and obtain any number of hardware monitoring data, configuration monitoring data, security monitoring data, routing monitoring data, traffic monitoring data, and service monitoring data for each device.

[0144] The basic functions determine the transmission cycle of the monitoring data reported to the central node, store the monitoring data within one transmission cycle locally, and delete the locally stored monitoring data after reconciling the monitoring data with the central node.

[0145] In this embodiment, after the monitoring module is deployed, the monitoring node continues to issue instructions from the subsequent task flow to perform monitoring tasks. In addition to monitoring tasks, the monitoring node also has the following specific functions:

[0146] Monitoring data collection: Based on the containers issued by the central node, the monitoring tasks and collection rules are determined. The modules of the monitoring nodes periodically or in real time collect various performance indicators and status information of network devices, such as CPU utilization, memory usage, interface traffic, link status, etc.

[0147] Data processing and reporting: The monitoring nodes preprocess and standardize the collected raw data, filter out redundant or invalid data, and report the processed data to the central node through the network.

[0148] Local data storage: In order to avoid data loss due to network interruption or central node failure, monitoring nodes usually cache monitoring data locally for a certain period of time and resend it to the central node after the network is restored.

[0149] After module deployment is complete, the container is started to perform relevant maintenance on the central node and monitoring nodes. While resolving deployment issues, corresponding maintenance solutions are also proposed. Starting from the master-distribute node deployment structure designed in this solution, all control permissions for various nodes are uniformly centralized under the management system of the central node. Therefore, maintenance work revolves around the central node, with the management system extending to the monitoring nodes within this system.

[0150] Basic maintenance procedures are as follows Figure 5 As shown, the process includes: performing maintenance work; identifying the equipment involved in the maintenance; selecting an automated processing solution for the equipment; determining whether the solution meets the maintenance requirements; if not, contacting the on-site equipment manufacturer for processing; if it meets the requirements, generating and executing the corresponding maintenance process; determining whether the maintenance was successful; if not, contacting the on-site equipment manufacturer for processing; if the maintenance was successful, completing the maintenance work.

[0151] The maintenance includes:

[0152] Hardware maintenance: Nodes involved in hardware maintenance, including the central node, will generate alarms in the management system when problems or abnormalities are detected based on hardware monitoring data, focusing on the physical environment and hardware operation status, and will notify the maintenance personnel of the corresponding nodes to carry out replacement or repair work.

[0153] Software maintenance: The software components involved in monitoring originate directly from the central node; therefore, software patch updates and vulnerability fixes begin at the central node. After the central node's rectification is completed, the relevant monitoring nodes are covered by the latest version of the modules distributed by the central node's management system, thus completing the rectification of the monitoring nodes.

[0154] Data Maintenance: The central node controls all data operations, including backup strategy formulation, data recovery, and historical data archiving, and sets backup and archiving strategies for monitoring nodes. Related plans are directly implemented by the management system through configuration files and commands, automating the data maintenance work for each module of each monitoring node.

[0155] Security maintenance: Based on the deployment of the central node and monitoring nodes and the consideration of relying on the same internal network environment, security maintenance is uniformly handled by the access devices and security devices (routers, firewalls and related devices). Data is fed back to the central node by the security monitoring modules on their respective devices for on-duty personnel to verify.

[0156] Overall, the maintenance approach of this framework focuses on three key areas: module maintenance, configuration management, and automated maintenance. Specific maintenance is implemented by the management platform through AirFlow task flows. Combined with the management platform's high-level and unified control over the modules of each node, this achieves distributed monitoring and centralized management and maintenance.

[0157] In summary, this embodiment proposes a distributed deployment method for an equipment monitoring system. By centrally managing the deployment of monitoring nodes, it can solve the following problems existing in the prior art: cumbersome deployment process, high requirements for technical personnel's professional knowledge and related skills, numerous and inconsistent deployment scenarios, and high deployment costs; system maintenance needs to be carried out in various scenarios, and there is a lack of a systematic monitoring system management model, making maintenance inconvenient; and insufficient feedback capabilities during the deployment process.

[0158] The technical effects that can be achieved by this embodiment include:

[0159] 1) Unified deployment environment and reduced deployment costs: By using the operating system of the network devices (i.e., the actual production environment of the devices) as the basis for the deployment scheme design, the system environment of the network devices is unified, so that the same type and series of devices can share a set of monitoring deployment schemes, resulting in less cost.

[0160] 2) Modular Monitoring Component Deployment: The core monitoring functions are modularized, and monitoring function modules for various devices are created based on the common environments of existing equipment. This achieves a more efficient deployment method while providing the flexibility to freely combine monitoring functions. The deployment process is implemented based on the central node's management platform. Combined with the modularization of monitoring functions, this reduces the risks associated with manual connection deployment and greatly improves deployment efficiency.

[0161] 3) Unified Management and Easy Maintenance: Based on task flow, unified management of all devices is achieved. A unified monitoring deployment and maintenance management platform is established in the production environment to enable remote maintenance and unified operations. Through the task flow of the central node, unified, one-to-many control of monitoring nodes is implemented, achieving intelligent and automated equipment monitoring and management, visualization of maintenance work progress, and improved timeliness of monitoring and maintenance feedback. This ensures consistency across all monitoring scenarios during the maintenance process, and allows maintenance personnel to perform maintenance on a unified platform, enhancing their maintenance capabilities.

[0162] 4) Strong feedback capability: Proposes to monitor actual deployment in the form of automated tasks, realize the visualization of progress and the phased process of each deployment stage, and emphasize the feedback capability of each deployment stage to realize timely perception of problems that occur in the deployment process.

[0163] This embodiment's solution can be applied to the deployment and maintenance of industry gateway monitoring. Specifically, existing industry gateway servers can be uniformly managed under a central node to achieve a unified architecture, and permissions can be uniformly opened to the node management platform. Based on this, monitoring modules can be created according to the monitoring needs of existing devices and centrally deployed at the central node. Meanwhile, on-duty personnel can directly use the management platform to review the relevant data from the daily monitoring of each device and perform related maintenance operations according to maintenance specifications. Deployment requires pre-selecting a server with suitable performance as the central node and ensuring that each device system has sufficient space to support the deployment of monitoring functions. Devices operate uniformly within a designated area on the intranet; simply connecting the various servers and device networks is sufficient to meet the basic deployment requirements.

[0164] Example 2:

[0165] like Figure 6 As shown, this disclosure provides a distributed deployment device for device monitoring, the device comprising:

[0166] Decomposition module 1 is used to obtain a decompressed package and multiple containers for installing equipment monitoring functions. The decompressed package encapsulates the basic functions for installing equipment monitoring functions, and each of the multiple containers is used to install a module function of the equipment monitoring function.

[0167] Installation module 2, connected to decomposition module 1, is used to install the basic functions of the equipment monitoring function at a certain distributed node of the equipment monitoring system through the decompression package, and to install multiple module functions of the equipment monitoring function through the multiple containers.

[0168] The monitoring module 3, connected to the installation module 2, is used by the distributed node to monitor several devices through the basic functions and the functions of the multiple modules, and to report the monitoring data to the central node of the device monitoring system.

[0169] In this embodiment, the device may specifically be: a distributed node of an equipment monitoring system, a central node of an equipment monitoring system, or an equipment monitoring system including multiple distributed nodes and at least one central node.

[0170] In one embodiment, wherein:

[0171] The basic functions include:

[0172] The communication capability is specifically implemented by configuring a communication protocol and routing table for transmitting the monitoring data to the distributed node.

[0173] The data management function specifically includes the local storage function of the monitoring data of a certain distributed node and the reconciliation function of the monitoring data between the certain distributed node and the central node;

[0174] The functions of the multiple modules include any of the following:

[0175] The hardware monitoring function is used to monitor the online status and hardware performance parameters of the aforementioned devices.

[0176] Configure monitoring functionality to monitor the configuration files and configuration change operations of the aforementioned devices.

[0177] The security monitoring function is used to monitor user authentication activities of the aforementioned devices and collect device logs.

[0178] The routing monitoring function is used to monitor routing protocol issues and routing security events of the aforementioned devices.

[0179] The traffic monitoring function is used to monitor the traffic and traffic security events of each interface of the aforementioned devices.

[0180] The service monitoring function is used to monitor the network resources on which the services of the aforementioned devices depend.

[0181] In one embodiment, the apparatus further includes:

[0182] The update module is used to respond to a request to change a certain module function among the multiple module functions, obtain the container after the change of the certain module function, and replace the corresponding container before the change with the changed container at a certain distribution node, so as to realize the change operation of the certain module function.

[0183] In one embodiment, the device is specifically a central node, wherein:

[0184] The decomposition module 1 is used to divide the device monitoring function to be deployed to a certain distributed node into basic functions and multiple module functions, and to encapsulate the basic functions into an uncompressed package, and to encapsulate each of the multiple module functions into a container;

[0185] Installation module 2 is used to send the decompressed package and the multiple containers to the distribution node, so that the distribution node can install the basic function through the decompressed package and install the multiple module functions through the multiple containers;

[0186] The monitoring module 3 is used to receive monitoring data from the distributed node. The monitoring data is obtained by the distributed node through the basic functions and the functions of the multiple modules to monitor several devices.

[0187] The update module is used to respond to a change operation of a certain module function, obtain the container of the certain module function after the change and several distribution nodes of the certain module function, and send the changed container to the several distribution nodes so that the several distribution nodes use the changed container to replace the corresponding container before the change.

[0188] In one embodiment, the central node further includes:

[0189] The deployment control module is used to respond to the monitoring of a new device accessing the system, obtain the device information of the new device, select a deployment strategy corresponding to the device information, the deployment strategy includes selecting a distribution node for monitoring the new device and the device monitoring function to be deployed to the distribution node for monitoring the new device, and establishing a connection with the distribution node via the Secure Shell protocol SSH, the SSH being used to send the decompressed package and the multiple containers to the distribution node, and to obtain the installation progress of the decompressed package and the multiple containers on the distribution node.

[0190] In one embodiment, wherein:

[0191] The device information includes: device type information, device model information, network performance parameters, network topology information, and hardware and software resource information of the new device;

[0192] The deployment strategy is determined by the central node: either automatically selecting a deployment strategy pre-configured by the network administrator through a visual interface based on the device information, or displaying the device information to the network administrator through a visual interface and receiving the deployment strategy selected by the network administrator based on the device information;

[0193] The device monitoring function includes: the number and version of multiple module functions selected based on device type information and device model information, and the communication protocol, routing table and transmission cycle selected based on network performance parameters, network topology information and hardware and software resource information for transmitting the monitoring data to the central node.

[0194] In one embodiment, the device is specifically a distributed node, wherein:

[0195] The decomposition module 1 is used to receive a decompressed package and multiple containers from the central node. The decompressed package encapsulates the basic functions for installing the device monitoring function, and each of the multiple containers is used to install a module function of the device monitoring function.

[0196] Installation module 2 is used to install the basic functions of the device monitoring function through the one decompressed package, and to install multiple module functions of the device monitoring function through the multiple containers.

[0197] Monitoring module 3 is used to monitor several devices through the basic functions and the functions of the multiple modules to obtain monitoring data, and to report the monitoring data to the central node;

[0198] The update module is used to receive a modified container from the central node and replace the corresponding unmodified container with the modified container to implement the change operation of a certain module function among the multiple module functions.

[0199] In one embodiment, the monitoring module 3 specifically includes:

[0200] The module monitoring unit is used to monitor several devices through the functions of the multiple modules, so as to obtain any multiple of the hardware monitoring data, configuration monitoring data, security monitoring data, routing monitoring data, traffic monitoring data, and service monitoring data of each device.

[0201] The data management and control unit, connected to the module monitoring unit, is used to determine the transmission cycle of the monitoring data reported to the central node through the basic functions, store the monitoring data within one transmission cycle locally, and delete the locally stored monitoring data after reconciling the monitoring data with the central node.

[0202] Example 3:

[0203] Embodiment 3 of this disclosure provides a computer-readable storage medium storing a computer program. When the computer program is run by a processor, it implements the distributed deployment method for device monitoring as described in Embodiment 1, or the distributed deployment apparatus for device monitoring as described in Embodiment 2.

[0204] The computer-readable storage medium includes volatile or non-volatile, removable or non-removable media implemented in any method or technology for storing information (such as computer-readable instructions, data structures, computer program units, or other data). Computer-readable storage media include, but are not limited to, RAM (Random Access Memory), ROM (Read-Only Memory), EEPROM (Electrically Erasable Programmable Read-Only Memory), flash memory or other memory technologies, CD-ROM (Compact Disc Read-Only Memory), DVD or other optical disc storage, cartridges, magnetic tapes, disk storage or other magnetic storage devices, or any other medium that can be used to store desired information and is accessible to a computer.

[0205] Additionally, this disclosure may also provide a computer device including a memory and a processor, wherein the memory stores a computer program, and when the processor runs the computer program stored in the memory, the processor executes the distributed deployment method for device monitoring as described in Embodiment 1. This computer device may also be a distributed deployment apparatus for device monitoring as described in Embodiment 2.

[0206] The memory is connected to the processor. The memory can be flash memory, read-only memory or other types of memory. The processor can be a central processing unit or a microcontroller.

[0207] Embodiments 1-3 of this disclosure provide a distributed deployment method for device monitoring, a distributed deployment device for device monitoring, and a computer-readable storage medium. The device monitoring function is decomposed into basic functions and multiple module functions. The basic functions are deployed in a unified environment, and each module function is deployed through a container. This facilitates meeting the different monitoring deployment requirements of different devices, and can improve deployment efficiency and reduce deployment costs.

[0208] It is understood that the above embodiments are merely exemplary embodiments used to illustrate the principles of this disclosure, and this disclosure is not limited thereto. For those skilled in the art, various modifications and improvements can be made without departing from the spirit and substance of this disclosure, and these modifications and improvements are also considered to be within the scope of protection of this disclosure.

Claims

1. A distributed deployment method for device monitoring, characterized in that, The method includes: Obtain an unzipped package and multiple containers for installing the device monitoring function. The unzipped package encapsulates the basic functions for installing the device monitoring function, and each of the multiple containers is used to install a module function of the device monitoring function. The basic functions of the equipment monitoring function are installed at a certain distributed node of the equipment monitoring system through the decompressed package, and multiple module functions of the equipment monitoring function are installed through the multiple containers. The distributed node monitors several devices through the basic functions and the multiple module functions, and reports the monitoring data to the central node of the device monitoring system, specifically including: The multiple modules are used to monitor several devices and obtain any number of hardware monitoring data, configuration monitoring data, security monitoring data, routing monitoring data, traffic monitoring data, and service monitoring data for each device. The basic functions determine the transmission cycle of the monitoring data reported to the central node, store the monitoring data within one transmission cycle locally, and delete the locally stored monitoring data after reconciling the monitoring data with the central node.

2. The method according to claim 1, characterized in that, in: The basic functions include: The communication capability is specifically implemented by configuring a communication protocol and routing table for transmitting the monitoring data to the distributed node. The data management function specifically includes the local storage function of the monitoring data of a certain distributed node and the reconciliation function of the monitoring data between the certain distributed node and the central node; The functions of the multiple modules include any of the following: The hardware monitoring function is used to monitor the online status and hardware performance parameters of the aforementioned devices. Configure monitoring functionality to monitor the configuration files and configuration change operations of the aforementioned devices. The security monitoring function is used to monitor user authentication activities of the aforementioned devices and collect device logs. The routing monitoring function is used to monitor routing protocol issues and routing security events of the aforementioned devices. The traffic monitoring function is used to monitor the traffic and traffic security events of each interface of the aforementioned devices. The service monitoring function is used to monitor the network resources on which the services of the aforementioned devices depend.

3. The method according to claim 1 or 2, characterized in that, The method further includes: In response to the need to modify a certain module function among the multiple module functions, the container of the modified module function is obtained, and the modified container is used to replace the corresponding container before the modification at a certain distribution node to realize the modification operation of the module function.

4. The method according to claim 3, characterized in that The method specifically includes: The central node will deploy device monitoring functions to a certain distributed node, which are divided into basic functions and multiple module functions. The basic functions are encapsulated into an unzipped package, and each of the multiple module functions is encapsulated into a container. The central node sends the decompressed package and the multiple containers to the distributed node, so that the distributed node can install the basic functions through the decompressed package and install the multiple module functions through the multiple containers; The central node receives monitoring data from a certain distributed node, which is obtained by the distributed node through the basic functions and the multiple module functions to monitor several devices; In response to a request to modify the functionality of a module, the central node obtains the container of the modified module and several distributed nodes that distribute the module functionality, and sends the modified container to the distributed nodes so that the distributed nodes can replace the corresponding container before the modification with the modified container.

5. The method according to claim 4, characterized in that, The method further includes: In response to the monitoring of a new device accessing the system, the central node obtains the device information of the new device, selects a deployment strategy corresponding to the device information, the deployment strategy includes selecting a distribution node for monitoring the new device and the device monitoring function to be deployed to the distribution node for monitoring the new device, and establishes a connection with the distribution node via the Secure Shell protocol SSH. The SSH is used to send the decompressed package and the multiple containers to the distribution node, and obtain the installation progress of the decompressed package and the multiple containers on the distribution node.

6. The method according to claim 5, characterized in that, in: The device information includes: device type information, device model information, network performance parameters, network topology information, and hardware and software resource information of the new device; The deployment strategy is determined by the central node: either automatically selecting a deployment strategy pre-configured by the network administrator through a visual interface based on the device information, or displaying the device information to the network administrator through a visual interface and receiving the deployment strategy selected by the network administrator based on the device information; The device monitoring function includes: the number and version of multiple module functions selected based on device type information and device model information, and the communication protocol, routing table and transmission cycle selected based on network performance parameters, network topology information and hardware and software resource information for transmitting the monitoring data to the central node.

7. The method according to claim 3, characterized in that, The method specifically includes: A distributed node receives a decompressed package and multiple containers from a central node. The decompressed package encapsulates basic functions for installing device monitoring functions, and each of the multiple containers is used to install a module function of the device monitoring function. The distributed node installs the basic functions of device monitoring on itself through the decompressed package, and installs multiple module functions of device monitoring on itself through the multiple containers. The distributed node monitors several devices and obtains monitoring data through the basic functions and the multiple module functions, and reports the monitoring data to the central node. The distributed node receives a modified container from the central node and replaces the corresponding container before the modification with the modified container to realize the modification operation of a certain module function among the multiple module functions.

8. A distributed deployment device for equipment monitoring, characterized in that, The device includes: The decomposition module is used to obtain an unzipped package and multiple containers for installing the equipment monitoring function. The unzipped package encapsulates the basic functions for installing the equipment monitoring function, and each of the multiple containers is used to install a module function of the equipment monitoring function. The installation module, connected to the decompression module, is used to install the basic functions of the equipment monitoring function at a certain distributed node of the equipment monitoring system through the decompression package, and to install multiple module functions of the equipment monitoring function through the multiple containers. The monitoring module, connected to the installation module, is used by a distributed node to monitor several devices through the basic functions and the functions of the multiple modules, and to report the monitoring data to the central node of the device monitoring system. Specifically, it includes: The multiple modules are used to monitor several devices and obtain any number of hardware monitoring data, configuration monitoring data, security monitoring data, routing monitoring data, traffic monitoring data, and service monitoring data for each device. The basic functions determine the transmission cycle of the monitoring data reported to the central node, store the monitoring data within one transmission cycle locally, and delete the locally stored monitoring data after reconciling the monitoring data with the central node.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a processor, implements the distributed deployment method for device monitoring as described in any one of claims 1-7.

Images