A distributed resource monitoring method and system

Abstract

The present application provides a distributed resource monitoring method and system, belonging to the field of computer technology. The monitoring method specifically includes: establishing a software environment and deploying middleware on each node; all middleware covers the monitoring center and each node, and forms a global data space between the monitoring center and each node. Each node transmits data to the global data space through the middleware. The monitoring center subscribes to the monitoring data required in the global data space through the middleware. The resource monitor node registers the information related to this node in the database of the monitoring center by calling the topic binding interface of the monitoring center, so as to realize the one-to-one mapping relationship between the topic and the monitoring node; after the topic binding interface of the monitoring center is called by the monitored node, it subscribes to the monitoring data of this node according to the topic Topic provided by the monitored node, and the user sets the monitoring data pulling rate to obtain the monitoring data of the corresponding node from the global data space.

Description

Technical Field

[0001] This application relates to the field of computer technology, and in particular, to a distributed resource monitoring method and system. Background Art

[0002] In the airborne environment, each aircraft platform carries a variety of intelligent devices and payload resources, naturally forming a distributed cluster. Reasonably and efficiently utilizing the existing resources on the aircraft platform is the key to winning in high-intensity air combat confrontations. Summary of the Invention

[0003] In view of this, this application provides a distributed resource monitoring method and system, which solves the problems in the prior art, realizes the effective monitoring of airborne resources, and while meeting the real-time and security requirements of the airborne embedded environment, ensures that all the airborne resources scheduled and used during the task distribution and deployment of the upper-layer decision-making module are in an available state.

[0004] On the one hand, a distributed resource monitoring method provided by this application adopts the following technical solutions:

[0005] A distributed resource monitoring method, which is applied to a distributed system. The resource monitoring method includes:

[0006] Establish a software environment and deploy middleware on each node; all middleware covers the monitoring center and each node, and forms a global data space between the monitoring center and each node. Each node transmits data to the global data space through the middleware, and the monitoring center subscribes to the monitoring data required in the global data space through the middleware;

[0007] The resource monitor node registers the information related to this node in the database of the monitoring center by calling the topic binding interface of the monitoring center, realizing the one-to-one mapping relationship between the topic and the monitoring node;

[0008] After the monitoring center topic binding interface is called by the monitored node, it subscribes to the monitoring data of this node according to the topic Topic provided by the monitored node. The user sets the monitoring data pulling rate, and obtains the monitoring data of the corresponding node from the global data space.

[0009] Optionally, the specific steps of each node include:

[0010] Step 1: Each computing node and terminal node in the cluster call the topic binding interface of the monitoring center for node registration. The parameters included in the interface call include the node name, node IP address, node MAC physical address, monitoring data topic Topic, and monitoring period;

[0011] Step 2: After the node receives the binding success flag, it starts multiple threads to concurrently monitor various resources of the node;

[0012] Step 3: The node stores the monitoring data in the local storage medium;

[0013] Step 4: The node encapsulates the collected monitoring data into the JSON data format;

[0014] Step 5: According to the monitoring data topic Topic bound in Step 1, the node publishes the encapsulated monitoring data to the global data space through the DDS middleware, and proceeds to execute Step 2.

[0015] Optionally, the specific steps of the monitoring center include:

[0016] Step 1: The monitoring center enables the topic binding interface service;

[0017] Step 2: The monitoring center receives the topic binding request from the node, parses the request, subscribes to the node monitoring data topic according to the Topic field, enables the monitoring thread for obtaining the monitoring data, and returns the binding success flag;

[0018] Step 3: According to the node monitoring data pulling rate set by the user, obtain the monitoring data of the corresponding node from the global data space.

[0019] Optionally, generate the Topic by the string random method or splice the MAC physical address of the node.

[0020] Optionally, the monitoring items of the monitored node and the processing method for the monitoring data include:

[0021] For the computing node, the monitoring items include the node CPU occupancy rate, memory occupancy rate, disk occupancy rate, network bandwidth occupancy rate, node survival status, node working status, task running status, monitoring timestamp;

[0022] For the terminal node, the monitoring items include the monitoring items of the computing node and the data collected by the sensor, and the terminal working status;

[0023] After receiving the binding success flag returned by the monitoring center, the resource monitor of the monitored node monitors the monitoring items of the node according to the preset monitoring period, locally stores the monitoring result data, and publishes it to the global data space through the DDS middleware according to the above-mentioned bound monitoring data topic Topic;

[0024] The node encapsulates the collected monitoring data into a recognizable data format.

[0025] On the other hand, a distributed resource monitoring system provided by the present application adopts the following technical solutions:

[0026] A distributed resource monitoring system, including a monitoring center and multiple nodes. The monitoring center deploys a cluster monitor and DDS middleware, and all nodes deploy a resource monitor and DDS middleware. Among them:

[0027] The monitoring center deploys a cluster monitor and DDS middleware to monitor all bound computing nodes and terminal nodes in the cluster;

[0028] The resource monitor is used to monitor the resource status of the node;

[0029] The DDS middleware is used to publish the monitored resource status data to the global data space;

[0030] The monitoring center subscribes to and obtains the monitoring data published by the computing nodes and terminal nodes in the global data space through the DDS middleware.

[0031] Optionally, the system includes N computing nodes, N terminal nodes and a monitoring center. Among them:

[0032] The computing nodes provide computing resources for running computing tasks;

[0033] The terminal nodes provide sensing resources and functional resources for realizing the computing, storage and communication of terminal devices.

[0034] Optionally, the terminal node includes a terminal device and a computing device. The terminal device includes a sensing device and a functional device. The computing device includes a general computing device with computing, storage and communication capabilities. A resource agent is deployed in the computing device for controlling interaction and data interaction with the terminal device. The resource agent runs in a container of the computing device, and the container encapsulates the driver of the terminal device. The container provides interface methods externally for controlling the terminal device.

[0035] Optionally, the interface methods include one or more of Socket call, Web Service, JSON-RPC, and Restful API.

[0036] Optionally, all nodes in the system include a processor and a computer-readable storage medium, and a computer program for realizing distributed monitoring is stored in the computer-readable storage medium.

[0037] In summary, the present application includes the following beneficial technical effects:

[0038] 1. In this application, middleware is deployed on each node to achieve resource and status monitoring of each distributed node in the cluster. The node calls the topic binding interface of the monitoring center to agree on the Topic for monitoring data transmission and communication. The monitoring center and the monitored node publish and obtain monitoring data through the same topic Topic.

[0039] 2. Commonly used open-source distributed monitoring tools such as Zabbix use the C / S architecture. When the number of monitoring hosts increases and the data volume grows, it will cause increased pressure on the server side and even lead to server downtime. This application realizes distributed monitoring through the DDS publish-subscribe mechanism. The monitoring center can dynamically adjust the monitoring data pulling rate according to its own load. At the same time, since the monitoring center and the monitored node interact data through the DDS topic Topic, the cluster communication is more flexible. When a new node joins the cluster, it only needs to call the topic binding interface of the monitoring center for registration, making the system easier to expand; it is more lightweight and more suitable for the embedded environment. BRIEF DESCRIPTION OF THE DRAWINGS

[0040] To more clearly illustrate the technical solutions of the embodiments of this application, the following will briefly introduce the drawings required in the embodiments. Obviously, the drawings in the following description are only some embodiments of this application. For those of ordinary skill in the art, without creative efforts, other drawings can be obtained based on these drawings.

[0041] Figure 1 It is a schematic diagram of the distributed resource monitoring process of this application.

[0042] Figure 2 It is a cluster architecture diagram of the distributed resource monitoring system of this application. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0043] The following will describe the embodiments of this application in detail with reference to the drawings.

[0044] The following illustrates the implementation manners of this application through specific specific examples. Those skilled in the art can easily understand other advantages and effects of this application from the content disclosed in this specification. Obviously, the described embodiments are only a part of the embodiments of this application, rather than all of the embodiments. This application can also be implemented or applied through other different specific implementation manners. Various details in this specification can also be modified or changed based on different viewpoints and applications without departing from the spirit of this application. It should be noted that, without conflict, the following embodiments and the features in the embodiments can be combined with each other. All other embodiments obtained by those of ordinary skill in the art based on the embodiments in this application without creative efforts belong to the scope of protection of this application.

[0045] It should be noted that the following describes various aspects of embodiments within the scope of the appended claims. It will be apparent that the aspects described herein can be embodied in a wide variety of forms, and any specific structure and / or function described herein is illustrative only. Based on this application, those skilled in the art should understand that one aspect described herein can be implemented independently of any other aspect, and two or more of these aspects can be combined in various ways. For example, any number of aspects set forth herein can be used to implement an apparatus and / or practice a method. In addition, this apparatus can be implemented and this method can be practiced using other structures and / or functionality in addition to one or more of the aspects set forth herein.

[0046] It should also be noted that the drawings provided in the following embodiments only illustrate the basic concept of this application schematically. Only the components related to this application are shown in the drawings, rather than being drawn according to the number, shape and size of the components in actual implementation. The type, quantity and proportion of each component in its actual implementation can be arbitrarily changed, and the component layout type may also be more complex.

[0047] In addition, in the following description, specific details are provided to facilitate a thorough understanding of the examples. However, those skilled in the art will understand that the aspects described can be practiced without these specific details.

[0048] An embodiment of this application provides a distributed resource monitoring method.

[0049] As Figure 1 shown, a distributed resource monitoring method, the method is applied to a distributed system, and the resource monitoring method includes:

[0050] Establish a software environment and deploy middleware on each node; all middleware covers the monitoring center and each node, and forms a global data space between the monitoring center and each node. Each node transmits data to the global data space through the middleware, and the monitoring center subscribes to the monitoring data required in the global data space through the middleware.

[0051] The resource monitor node registers the information related to this node in the database of the monitoring center by calling the topic binding interface of the monitoring center, and realizes the one-to-one mapping relationship between the topic and the monitoring node;

[0052] After the topic binding interface of the monitoring center is called by the monitored node, it subscribes to the monitoring data of this node according to the topic Topic provided by the monitored node. The user sets the monitoring data pulling rate, and obtains the monitoring data of the corresponding node from the global data space.

[0053] The specific steps of each node include:

[0054] Step 1: Each computing node and terminal node in the cluster calls the topic binding interface of the monitoring center for node registration. The parameters included in the interface call are node name, node IP address, node MAC physical address, monitoring data topic Topic, and monitoring period;

[0055] Step 2: After the node receives the binding success flag, it starts multiple threads to concurrently monitor various resources of the node;

[0056] Step 3: The node stores the monitoring data in the local storage medium;

[0057] Step 4: The node encapsulates the collected monitoring data into the JSON data format;

[0058] Step 5: According to the monitoring data topic Topic bound in Step 1, the node publishes the encapsulated monitoring data to the global data space through the DDS middleware, and then proceeds to execute Step 2.

[0059] The specific steps of the monitoring center include:

[0060] Step 1: The monitoring center starts the topic binding interface service;

[0061] Step 2: The monitoring center receives the topic binding request from the node and parses the request. According to the Topic field, it subscribes to the node monitoring data topic, starts the monitoring thread for obtaining monitoring data, and returns the binding success flag;

[0062] Step 3: According to the node monitoring data pulling rate set by the user, obtain the monitoring data of the corresponding node from the global data space.

[0063] To ensure the uniqueness of the monitoring data topic Topic in the global data space, generate the Topic by the string random method or concatenate the MAC physical address of the node. By setting the same domain, ensure the logical isolation of the monitoring data interaction from the communication network of other applications within the system, while the communication between the monitoring center and the monitored node is not affected.

[0064] The monitoring items of the monitored node and the processing methods for the monitoring data include:

[0065] For computing nodes, the monitoring items include node CPU occupancy rate, memory occupancy rate, disk occupancy rate, network bandwidth occupancy rate, node survival status, node working status, task running status, monitoring timestamp;

[0066] For terminal nodes, the monitoring items include the monitoring items of computing nodes and the data collected by sensors, and the terminal working status;

[0067] The resource monitor of the monitored node receives the successful binding flag returned by the monitoring center, monitors the monitoring items of the node according to the preset monitoring period, locally stores the monitoring result data, and publishes it to the global data space through the DDS middleware according to the monitored data topic Topic bound above;

[0068] The node encapsulates the collected monitoring data into a recognizable data format.

[0069] This application also discloses a distributed resource monitoring system

[0070] Such as Figure 2 As shown, a distributed resource monitoring system includes a monitoring center and multiple nodes. The monitoring center deploys a cluster monitor and DDS middleware, and all nodes deploy a resource monitor and DDS middleware, where:

[0071] The monitoring center deploys a cluster monitor and DDS middleware to monitor all bound computing nodes and terminal nodes in the cluster;

[0072] The resource monitor is used to monitor the resource status of the node;

[0073] The DDS middleware is used to publish the monitored resource status data to the global data space;

[0074] Through the DDS middleware, the monitoring center can subscribe to and obtain the monitoring data published by the computing nodes and terminal nodes in the global data space.

[0075] The monitoring center can, through the DDS middleware, subscribe to and obtain the monitoring data published by the computing nodes and terminal nodes in the global data space. The monitoring center can dynamically adjust the monitoring data pulling rate according to its own load conditions, including data reception and processing capabilities, and communication bandwidth capabilities.

[0076] This application realizes the resource and status monitoring of each distributed node in the cluster through the publish / subscribe mechanism of DDS. The node calls the topic binding interface of the monitoring center to agree on the Topic for monitoring data transmission and communication. The monitoring center and the monitored node publish and obtain monitoring data through the same topic Topic. The present invention realizes the active data acquisition of the monitoring center through the publish / subscribe method, can dynamically adjust the amount and frequency of monitoring data acquisition according to the load of the monitoring center, and effectively solves the data congestion problem at the receiving end. At the same time, the flexibility and scalability of the system are also improved.

[0077] The system includes N computing nodes, N terminal nodes and a monitoring center, where:

[0078] The computing node provides computing resources for running computing tasks;

[0079] The terminal node provides sensing resources and functional resources for implementing the computing, storage, and communication of the terminal device.

[0080] The terminal node is a combination of the terminal device and the computing device. The terminal node includes the terminal device and the computing device. The terminal device includes the sensing device and the functional device. The computing device includes the general computing device, which has the capabilities of computing, storage, and communication. A resource broker is deployed in the computing device for controlling interaction and data interaction with the terminal device. The resource broker runs in a container of the computing device, and the driver of the terminal device is encapsulated in the container. The container provides interface methods externally for controlling the terminal device.

[0081] The interface methods include one or more of Socket calls, Web Service, JSON-RPC, and Restful API.

[0082] All nodes in the system include a processor and a computer-readable storage medium. A computer program for implementing distributed monitoring is stored in the computer-readable storage medium.

[0083] As Figure 1 shown, the process of distributed resource monitoring is that the distributed resource monitoring process is divided into two processes: the monitored node and the monitoring center.

[0084] For the monitored node:

[0085] Step a1: Each computing node and terminal node in the cluster calls the topic binding interface of the monitoring center for node registration. The parameters included in the interface call are the node name, node IP address, node MAC physical address, monitoring data topic Topic, and monitoring period.

[0086] Step a2: After the node receives the binding success flag, it starts multiple threads to concurrently monitor various resources of the node.

[0087] Step a3: The node stores the monitoring data in the local storage medium.

[0088] Step a4: The node encapsulates the collected monitoring data into the JSON data format.

[0089] Step a5: According to the monitoring data topic Topic bound in step 1, the node publishes the encapsulated monitoring data to the global data space through the DDS middleware and then goes back to execute step a4.

[0090] For the monitoring center:

[0091] Step b2: The monitoring center starts the topic binding interface service.

[0092] Step b2: The monitoring center receives the topic binding request from the node, parses the request, subscribes to the node monitoring data topic according to the Topic field, starts a monitoring thread to obtain the monitoring data, and returns a binding success flag.

[0093] Step b3: Obtain the monitoring data of the corresponding node from the global data space according to the node monitoring data pulling rate set by the user.

[0094] Step b4: If the latest obtained monitoring data is abnormal and exceeds the set threshold, an event alarm is issued.

[0095] When the computing node and the terminal node successfully call the topic binding interface, it means that the monitored node and the monitoring center have reached a topic agreement, and data communication between the two is achieved by publishing and subscribing to data to the same topic Topic. Steps b1 to b3 are the processes for the monitored node to continuously monitor the resource status and publish the monitoring data, and step b4 is the response processing of the monitoring center to the abnormal node resources or status.

[0096] When the monitoring center receives the topic binding request from the node, it parses and processes the interface data, and cyclically reads the monitoring data of the node at the preset pulling rate through step c2.

[0097] As described above, it is only the specific implementation manner of this application, but the protection scope of this application is not limited thereto. Any changes or substitutions that can be easily thought of by those skilled in the art within the technical scope disclosed by this application should be covered by the protection scope of this application. Therefore, the protection scope of this application should be subject to the protection scope of the claims.

Claims

1. A distributed resource monitoring method, which is applied to a distributed system, characterized in that, The described resource monitoring method includes: Establish a software environment and deploy middleware on each node; all middleware covers the monitoring center and each node, and forms a global data space between the monitoring center and each node. Each node transmits data to the global data space through the middleware, and the monitoring center subscribes to the required monitoring data in the global data space through the middleware. The resource monitor node registers the relevant information of this node in the database of the monitoring center by calling the topic binding interface of the monitoring center, realizing the one-to-one mapping relationship between the topic and the monitoring node. After the monitoring center topic binding interface is called by the monitored node, it subscribes to the monitoring data of this node according to the topic Topic provided by the monitored node. The user sets the monitoring data pulling rate, and obtains the monitoring data of the corresponding node from the global data space. The specific steps of each node include: Step 1: Each computing node and terminal node in the cluster call the topic binding interface of the monitoring center for node registration. The parameters included in the interface call include node name, node IP address, node MAC physical address, monitoring data topic Topic, and monitoring period. Step 2: After the node receives the binding success flag, it starts multiple threads to concurrently monitor various resources of the node. Step 3: The node stores the monitoring data in the local storage medium. Step 4: The node encapsulates the collected monitoring data into the JSON data format. Step 5: According to the monitoring data topic Topic bound in Step 1, the node publishes the encapsulated monitoring data to the global data space through the DDS middleware, and then proceeds to execute Step 2. The specific steps of the monitoring center include: Step 1: The monitoring center starts the topic binding interface service. Step 2: The monitoring center receives the topic binding request from the node and parses the request. It subscribes to the node monitoring data topic according to the Topic field, starts the monitoring thread for obtaining monitoring data, and returns the binding success flag. Step 3: According to the node monitoring data pulling rate set by the user, obtain the monitoring data of the corresponding node from the global data space.

2. The distributed resource monitoring method according to claim 1, characterized in that Generate Topic through the string random method or concatenate the MAC physical address of the node.

3. The distributed resource monitoring method according to claim 1, wherein The monitoring items of the monitored node and the processing method of the monitoring data include: For the computing node, the monitoring items include node CPU occupancy rate, memory occupancy rate, disk occupancy rate, network bandwidth occupancy rate, node survival status, node working status, task running status, monitoring timestamp. For the terminal node, the monitoring items include the monitoring items of the computing node and the data collected by the sensor, and the terminal working status. After the resource monitor of the monitored node receives the binding success flag returned by the monitoring center, it monitors the monitoring items of the node according to the preset monitoring period, locally stores the monitoring result data, and publishes it to the global data space through the DDS middleware according to the above-mentioned bound monitoring data topic Topic. The node encapsulates the collected monitoring data into a recognizable data format.

4. A distributed resource monitoring system, characterized in that, It includes a monitoring center and multiple nodes. The monitoring center deploys a cluster monitor and DDS middleware, and all nodes deploy a resource monitor and DDS middleware, where: The monitoring center deploys a cluster monitor and DDS middleware to monitor all bound computing nodes and terminal nodes in the cluster; The resource monitor is used to monitor the resource status of nodes; The DDS middleware is used to publish the monitored resource status data to the global data space; The monitoring center subscribes to and obtains the monitoring data published by the computing nodes and terminal nodes in the global data space through the DDS middleware; The specific steps for each node include: Step 1: Each computing node and terminal node in the cluster calls the topic binding interface of the monitoring center for node registration. The parameters included in the interface call are node name, node IP address, node MAC physical address, monitoring data topic Topic, and monitoring period; Step 2: After the node receives the binding success flag, it starts multiple threads to concurrently monitor various resources of the node; Step 3: The node stores the monitoring data in the local storage medium; Step 4: The node encapsulates the collected monitoring data into the JSON data format; Step 5: According to the monitoring data topic Topic bound in Step 1, the node publishes the encapsulated monitoring data to the global data space through the DDS middleware, and then goes back to execute Step 2; The specific steps for the monitoring center include: Step 1: The monitoring center starts the topic binding interface service; Step 2: The monitoring center receives the topic binding request from the node and parses the request. According to the Topic field, it subscribes to the node monitoring data topic, starts the monitoring thread for obtaining monitoring data, and returns the binding success flag; Step 3: According to the node monitoring data pulling rate set by the user, obtain the monitoring data of the corresponding node from the global data space.

5. The distributed resource monitoring system according to claim 4, wherein The system includes N computing nodes, N terminal nodes, and a monitoring center, where: The computing nodes provide computing resources for running computing tasks; The terminal nodes provide sensing resources and functional resources for realizing the computing, storage, and communication of terminal devices.

6. The distributed resource monitoring system according to claim 5, wherein, The terminal node includes a terminal device and a computing device. The terminal device includes a sensing device and a functional device. The computing device includes a general computing device with computing, storage, and communication capabilities. A resource broker is deployed in the computing device for control interaction and data interaction with the terminal device. The resource broker runs in a container of the computing device, and the driver program of the terminal device is encapsulated in the container. The container provides interface methods externally for controlling the terminal device.

7. The distributed resource monitoring system according to claim 6, wherein, The interface methods include one or more of Socket calls, Web Service, JSON-RPC, and Restful API.

8. The distributed resource monitoring system according to claim 4, wherein All nodes in the system include a processor and a computer-readable storage medium, and a computer program for realizing distributed monitoring is stored in the computer-readable storage medium.

Images