Equipment management method and device, equipment, medium and program product

Abstract

The invention discloses an equipment management method and device, equipment, a medium and a program product. The method comprises the following steps: a management device of a server side obtains state data sent by a proxy device; wherein the state data is at least used for representing the configuration state of at least one monitoring device managed by the proxy device; the at least one monitoring device is used for monitoring the operation state of a target device; in response to a management operation for the state data, generating management data; and sending the management data to the proxy device to trigger the proxy device to manage the at least one monitoring device based on the management data.

Description

Technical Field

[0001] The present application relates to the field of remote monitoring technology, and in particular to a device management method, apparatus, equipment, medium and program product. Background Art

[0002] In remote monitoring scenarios, monitoring devices equipped with Agent components need to rely on complex manual operations by professional technicians or users to control the monitoring devices to obtain and respond to management instructions issued by the management device on the server side. However, the above management methods for monitoring devices are not flexible enough. Summary of the invention

[0003] Based on the above technical problems, the embodiments of the present application provide a device management method, apparatus, equipment, medium and program product.

[0004] The technical solution provided by the embodiment of the present application is as follows:

[0005] The present invention provides a device management method, which includes:

[0006] The management device at the server side obtains the status data sent by the proxy device; wherein the status data is at least used to represent the configuration status of at least one monitoring device managed by the proxy device; the at least one monitoring device is used to monitor the operating status of the target device;

[0007] generating management data in response to a management operation on the state data;

[0008] The management data is sent to the agent device to trigger the agent device to manage the at least one monitoring device based on the management data.

[0009] In some embodiments, generating management data in response to a management operation on the state data includes:

[0010] If the status data indicates that the kth device in the at least one monitoring device is in a first state, in response to a state switching operation for the first state, management data for controlling the kth device to switch to a second state is generated; wherein the management operation includes the state switching operation; k is an integer greater than or equal to 1 and less than or equal to K; and K is the number of devices in the at least one monitoring device.

[0011] In some embodiments, generating management data in response to a management operation on the state data includes:

[0012] If the status data indicates that the version of the proxy component set for the kth device in the at least one monitoring device is different from the specified version, in response to a version switching operation of the proxy component set for the kth device, management data for controlling the version change of the kth device is generated; wherein the management operation includes the version switching operation; the management data includes the version identifier of the specified version of the proxy component; the proxy component is used to control the kth device to monitor the operating status of the target device; k is an integer greater than or equal to 1 and less than or equal to K; K is the number of devices in the at least one monitoring device.

[0013] In some embodiments, before generating management data for controlling the version change of the kth device in response to the version switching operation of the proxy component set for the kth device, the method further includes:

[0014] Sending an information acquisition request to the proxy device, so that the proxy device sends the information acquisition request to the kth device; wherein the kth device is used to respond to the information acquisition request, acquire and send configuration data of the kth device to the proxy device; the configuration data of the kth device at least includes a version identifier of the proxy component set by the kth device;

[0015] Receive and store the configuration data of the kth device sent by the proxy device.

[0016] In some embodiments, generating management data for controlling the version change of the kth device includes:

[0017] Determine a data storage address of the specified version of the proxy component; wherein the data storage address is used for the proxy device to obtain the specified version of the proxy component;

[0018] The management data for controlling a changed version of the k-th device is generated based on the data storage address.

[0019] In some embodiments, generating management data in response to a management operation on the state data includes:

[0020] If the status data indicates that the kth device in the at least one monitoring device is not configured with an agent component, in response to a management operation for the kth device not being configured with the agent component, management data is generated to instruct the kth device to install an agent component of a specified type; wherein the agent component is used to control the kth device to monitor the operating status of the target device; k is an integer greater than or equal to 1 and less than or equal to K; and K is the number of devices in the at least one monitoring device.

[0021] In some embodiments, generating management data in response to a management operation on the state data includes:

[0022] If the status data represents that the device time of the kth device in the at least one monitoring device is different from the device time of the management device, management data associated with the device time of the kth device is generated in response to a time setting operation for the device time of the kth device; wherein the management operation includes the time setting operation; the management data is used to trigger the synchronization of the device time of the kth device to the device time of the management device; k is an integer greater than or equal to 1 and less than or equal to K; and K is the number of devices in the at least one monitoring device.

[0023] In some embodiments, obtaining the status data sent by the proxy device includes:

[0024] receiving a connection establishment request sent by the proxy device; wherein the connection establishment request includes device authentication information of the proxy device;

[0025] In response to the connection establishment request, performing identity authentication on the proxy device based on the device authentication information to obtain an authentication result;

[0026] If the authentication result is an authentication pass state, establishing a two-way communication connection between the management device and the proxy device;

[0027] The status data sent by the proxy device is obtained through the two-way communication connection.

[0028] The embodiment of the present application further provides a device management device, which is arranged in a management device at a server end; the device management device comprises:

[0029] A transceiver module, used to obtain status data sent by the proxy device; wherein the status data is at least used to characterize the configuration status of at least one monitoring device managed by the proxy device; the at least one monitoring device is used to monitor the operating status of the target device;

[0030] a processing module, configured to generate management data in response to a management operation on the state data;

[0031] The transceiver module is further configured to send the management data to the agent device to trigger the agent device to manage the at least one monitoring device based on the management data.

[0032] An embodiment of the present application also provides a management device on the server side, the management device comprising a processor and a memory; wherein a computer program is stored in the memory; when the computer program is executed by the processor, it can implement any of the device management methods described above.

[0033] An embodiment of the present application further provides a computer-readable storage medium, in which a computer program is stored; when the computer program is executed by a processor of an electronic device, the device management method as described above can be implemented.

[0034] An embodiment of the present application further provides a computer program product, which includes a computer program; when the computer program is executed by a processor of an electronic device, it can implement any of the device management methods described above.

[0035] In the device management method provided in the embodiment of the present application, the management device on the server side obtains the status data sent by the proxy device, and the status data is at least used to characterize the configuration status of at least one monitoring device managed by the proxy device, and the at least one monitoring device is used to monitor the operating status of the target device. In this way, through the above-mentioned transmission process of the status data between the monitoring device, the proxy device and the management device, the management device on the server side can flexibly, automatically and in real time obtain the configuration status of the monitoring device; and, by generating management data in response to management operations on the status data, a connection is established between the management data and the status data in the management operation dimension, thereby improving the pertinence and accuracy of the management data; in this On the basis of this, management data is sent to the proxy device to trigger the proxy device to manage at least one monitoring device based on the management data. In this way, through the above operations, the management device can achieve targeted, high-precision, real-time, automated and flexible management of at least one monitoring device through the proxy device, thereby solving the technical problem that the management device in the related technology cannot automatically manage the monitoring device; on the other hand, during the execution of the device management method provided in the embodiment of the present application, no manual intervention by professional technicians or users is required, thereby reducing labor costs, and reducing the probability of equipment management errors due to manual intervention by professional technicians or users, and improving the efficiency of managing monitoring equipment.

[0036] When the device management method provided in the embodiment of the present application is applied to a large-scale monitoring device management scenario, it can not only improve the efficiency of large-scale monitoring device management, but also improve the real-time and intelligence level of monitoring device management, and improve the flexibility of monitoring device management. BRIEF DESCRIPTION OF THE DRAWINGS

[0037] Figure 1 A schematic diagram of a process flow of a device management method provided in an embodiment of the present application;

[0038] Figure 2 A schematic diagram of the structure of the management window provided in the embodiment of the present application;

[0039] Figure 3 A schematic diagram of a process for switching the version of a proxy component provided in an embodiment of the present application;

[0040] Figure 4 Another structural diagram of the management window provided in the embodiment of the present application;

[0041] Figure 5 A schematic diagram of a process for a management device to manage a monitoring device through a proxy device provided in an embodiment of the present application;

[0042] Figure 6 A schematic diagram of a process for establishing a two-way communication connection provided in an embodiment of the present application;

[0043] Figure 7 A schematic diagram of the structure of the device management device provided in the embodiment of the present application;

[0044] Figure 8 A schematic diagram of the structure of the management device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0045] The technical solutions in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application.

[0046] It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0047] In remote monitoring scenarios, monitoring devices installed with Agent clients need to rely on complex manual operations by professional technicians or users to control the monitoring devices to obtain and respond to management instructions issued by the management devices on the server side.

[0048] For example, for Zabbix Agent or Promethues expoter, if the monitoring device equipped with the Agent component has a version update requirement, the version update operation needs to be manually performed by professional technicians or users when the monitoring device is connected to the Internet; if the monitoring device cannot be connected to the Internet, professional technicians or users need to download the specified version of the Agent component installation package from the version website, then manually stop the current Agent program, manually decompress the specified version of the Agent component installation package to obtain the binary file, and then copy the binary file to the monitoring device to update the Agent component, and manually start the updated Agent component.

[0049] Obviously, the operation of the above-mentioned management method for monitoring equipment is complicated. During the execution of the above-mentioned method, professional technicians or users are required to perform a large number of manual operations including installation package update instructions, manual downloading and decompression of Agent component installation packages, as well as manual operations such as stopping and restarting the Agent client, thereby increasing labor costs and making the above-mentioned process more likely to go wrong and inefficient.

[0050] Furthermore, the execution process of the above method completely relies on the manual operation of professional technicians or users, which results in insufficient real-time performance of the above method and inability to achieve real-time supervision.

[0051] Based on the above technical problems, the embodiments of the present application provide a device management method, apparatus, equipment, medium and program product.

[0052] Figure 1 A flow chart of a device management method provided in an embodiment of the present application is shown in FIG. Figure 1 As shown, the method may include the following steps:

[0053] Step 101: The management device at the server side obtains status data sent by the proxy device.

[0054] The state data is at least used to characterize the configuration state of at least one monitoring device managed by the proxy device; and the at least one monitoring device is used to monitor the operating state of the target device.

[0055] In one implementation, the target device may include an electronic device with monitoring requirements.

[0056] In one embodiment, the operating status of the target device may include whether the target device is in an operating state, the power consumption of the target device during operation, the process and / or thread switching state of the target device during operation, whether an abnormality occurs during data processing by the target device, and whether the intermediate data obtained by processing the input data during data processing by the target device and the final result meet the expected state.

[0057] In one embodiment, the monitoring device may include an electronic device provided with an Agent component; illustratively, a communication connection may be established between the monitoring device and the target device, so that the monitoring device can obtain the operating status of at least one target device, and can also manage at least one target device based on the above operating status or the control instructions issued by the agent device.

[0058] In one implementation, the target device and the monitoring device may both be physical machines or virtual machines.

[0059] In one embodiment, the configuration status may include the status of the software and / or hardware currently configured by the monitoring device; exemplarily, the software may include at least one of an Agent component, a user application or a system application configured by the monitoring device, and accordingly, the status of the software may include at least one of the version of the Agent component, the name, number and version of the user application or the system application; exemplarily, the hardware may include at least one of a processor, a hard disk, a memory and a network connection device of the monitoring device, and accordingly, the status of the hardware may include at least one of the model of the processor, the size of the remaining available storage space of the hard disk, the model and size of the memory, the network port included in the network connection device and the type of the communication module; exemplarily, the processor may include at least one of an Application Specific Integrated Circuit (ASIC), a Digital Signal Processor (DSP), a Digital Signal Processing Device (DSPD), a Programmable Logic Device (PLD), a Field Programmable Gate Array (FPGA), a Central Processing Unit (CPU), a controller, a Micro Controller Unit (MCU), and a microprocessor.

[0060] In one embodiment, the proxy device can be used to manage at least one monitoring device and can also track the operating status of at least one monitoring device. For example, the proxy device can obtain the heartbeat status of at least one monitoring device in real time and determine whether the at least one monitoring device is in a continuous operating state based on the heartbeat status.

[0061] In one implementation, the server may include a cloud or a remote network side.

[0062] In one implementation, the management device may include a physical machine or a virtual machine device set up at the server; illustratively, the management device may implement centralized management and centralized control of multiple proxy devices.

[0063] In one embodiment, a communication connection may be established between the management device and at least one proxy device. Through the communication connection, the management device may actively send a status acquisition request to at least one proxy device, so that at least one proxy device collects and sends status data to the management device in response to the status acquisition request. Alternatively, at least one proxy device may actively collect and send status data to the management device.

[0064] Step 102: Generate management data in response to a management operation on the state data.

[0065] In one implementation, the management data may include at least one of a state switching operation that needs to be performed by the monitoring device, an execution time of performing the state switching operation on the monitoring device, and an execution result of the above state switching operation.

[0066] In one embodiment, the management operation may include editing, updating, adding, deleting and selecting operations on the operating parameters of the monitoring device, and may also include state switching operations on the monitoring device; illustratively, the above-mentioned operating parameters may be associated with the operating mode and / or power consumption of the monitoring device.

[0067] In one embodiment, the management data may be generated by:

[0068] After receiving the status data, the management device creates a management window, and at the same time, classifies and summarizes the data in the status data to obtain a summary result, and then displays the above summary result, the device identification of each monitoring device, and the operation options that can perform operations on the summary result in the management window; and, by determining the selection operation of the management operation on the operation option, the operation category, the data in the summary result targeted by the management operation, and the selection operation on the device identification are determined to generate management data; exemplarily, the device identification may include the number, name and address of the monitoring device, wherein the address may include any one of the Internet Protocol Address (IP) address, Domain Name System (DNS) address, Media Access Control (MAC) address and Uniform Resource Locator (URL) address of the monitoring device.

[0069] Figure 2 A schematic diagram of the structure of the management window provided in the embodiment of the present application, such as Figure 2As shown, after the server option in the management window 201 is triggered, a list of monitoring devices equipped with Agent components can be displayed, wherein in the above list, the first to fourth monitoring devices contained in the resource name can represent the device identification of at least one monitoring device, the operating system type can include the type of the operating system of at least one monitoring device, the Agent status can include the running status of the Agent component set in at least one monitoring device, the Agent version can include the version of the Agent component set in at least one monitoring device, and the operation options can include operation options that can be performed on the nth monitoring device; wherein the operating system type can include Linux, the Agent version can be represented by a hexadecimal character combination, and n is an integer greater than or equal to 1 and less than or equal to 4.

[0070] Exemplarily, the management IP in the management window 201 may represent the IP address of the nth monitoring device, and the resource tenant may represent the user information associated with the nth monitoring device; and the management window 201 also provides filtering options and options for performing searches based on resource names.

[0071] Step 103: Send the management data to the agent device to trigger the agent device to manage at least one monitoring device based on the management data.

[0072] In one embodiment, the agent device manages at least one monitoring device based on the management data, which can be achieved in the following manner:

[0073] According to the device identification contained in the management data, the device to be managed is determined from at least one monitoring device, and then based on the operation type contained in the management data, the items to be managed in the device to be managed are managed; exemplarily, the items to be managed may include software or hardware parameters in the device to be managed corresponding to the data in the summary result targeted by the management operation.

[0074] From the above, it can be seen that in the device management method provided in the embodiment of the present application, the management device on the server side obtains the status data sent by the agent device, and the status data is at least used to characterize the configuration status of at least one monitoring device managed by the agent device, and at least one monitoring device is used to monitor the operating status of the target device. In this way, through the above-mentioned transmission process of the status data between the monitoring device, the agent device and the management device, the management device on the server side can flexibly, automatically and in real time obtain the configuration status of the monitoring device; and, by generating management data in response to management operations on the status data, a connection is established between the management data and the status data in the management operation dimension, thereby improving the pertinence and accuracy of the management data. ; On this basis, management data is sent to the proxy device to trigger the proxy device to manage at least one monitoring device based on the management data. In this way, through the above operations, the management device can achieve targeted, high-precision, real-time, automated and flexible management of at least one monitoring device through the proxy device, thereby solving the technical problem that the management device cannot automatically manage the monitoring device in the related technology; on the other hand, during the execution of the device management method provided in the embodiment of the present application, no manual intervention by professional technicians or users is required, thereby reducing labor costs, and reducing the probability of equipment management errors due to manual intervention by professional technicians or users, and improving the efficiency of managing monitoring equipment.

[0075] When the device management method provided in the embodiment of the present application is applied to a large-scale monitoring device management scenario, it can not only improve the efficiency of large-scale monitoring device management, but also improve the real-time and intelligence level of monitoring device management, and improve the flexibility of monitoring device management.

[0076] Based on the foregoing embodiments, in the device management method provided in the embodiments of the present application, generating management data in response to a management operation on status data can be implemented in the following manner:

[0077] If the state data indicates that a kth device in the at least one monitoring device is in a first state, in response to a state switching operation for the first state, management data for controlling the kth device to switch to a second state is generated.

[0078] The management operation includes a state switching operation; k is an integer greater than or equal to 1 and less than or equal to K; and K is the number of devices in the at least one monitoring device.

[0079] Accordingly, if the state data indicates that the kth device in the at least one monitoring device is not in the first state, management data for controlling the kth device to switch to the second state may not be generated.

[0080] In one implementation, the first state may represent the current state of the kth device.

[0081] In one implementation, the management window may display the first state of the kth device and may also load a state switching option for switching the first state. Thus, the state switching operation may be triggered by selecting or switching the state switching option.

[0082] In one implementation, the second state may be opposite to the first state. For example, the first state may include an off state or an on state, and the second state may include an on state or an off state.

[0083] In one implementation, the second state may be different from the first state. For example, the first state may be a high power consumption operation state, and the second state may be a low power consumption operation state. For another example, the first state may be an operation state, and the second state may be a sleep state.

[0084] In one implementation, the state switching operation may include a state identifier of the second state, so that the management device may generate management data for controlling the kth device to switch to the second state based on the state identifier of the second state and the device identifier of the kth device.

[0085] In one implementation, the management device may send management data for controlling the kth device to switch to the second state to the proxy device, so that the proxy device controls the kth device to switch from the first state to the second state based on the device identification of the kth device.

[0086] As can be seen from the above, in the device management method provided by the embodiment of the present application, if the state data indicates that the kth device in at least one monitoring device is in the first state, in response to the state switching operation for the first state, management data for controlling the kth device to switch to the second state is generated, and the management operation includes the state switching operation. In this way, through the above operation, the management device is able to generate management data for state switching of the kth device in at least one monitoring device, thereby providing a data basis for the management device to switch the state of the kth device through the proxy device, and also improving the flexibility of the management device in managing the state switching of the kth device.

[0087] Based on the foregoing embodiments, in the device management method provided in the embodiments of the present application, generating management data in response to a management operation on status data can also be implemented in the following manner:

[0088] If the status data indicates that the version of the proxy component set for the kth device in at least one monitoring device is different from the specified version, management data for controlling the version change of the kth device is generated in response to a version switching operation of the proxy component set for the kth device.

[0089] Among them, the management operation includes a version switching operation; the management data includes a version identifier of a specified version of the proxy component; the proxy component is used to control the kth device to monitor the operating status of the target device; k is an integer greater than or equal to 1 and less than or equal to K.

[0090] Accordingly, if the status data indicates that the version of the proxy component set in the kth device in at least one monitoring device is the same as the specified version, the management device may not respond to the version switching operation, and may not generate management data for controlling the version change of the kth device.

[0091] In one implementation, the proxy component may be the Agent component in the aforementioned embodiment.

[0092] In one implementation, the specified version may include the latest version of the agent component set by the kth device, or may be a version specified by a management device, a professional technician, or a user.

[0093] In one implementation, the type of the proxy component represented by the specified version may be the same as or different from the type of the proxy component set in the kth device.

[0094] In one implementation, the version switching operation may be implemented by a professional technician or a user by selecting or operating the proxy component of the kth device displayed in the management window.

[0095] In one implementation, a professional technician or a user may determine or set a version identifier of a specified version during the process of performing a version switching operation.

[0096] In one embodiment, the management data for controlling the version change of the kth device can instruct the kth device to perform a version update operation, and can also instruct the kth device to perform a simultaneous switching operation of the agent component type and the component version. For example, after the management device sends the management data for controlling the version change of the kth device to the agent device, the agent device can determine the target agent component and / or target version set by the management device for the kth device based on the version identifier of the specified version of the agent component contained in the above management data, and based on the target agent component and / or target version, instruct the kth device to switch from the first type of agent component to the second type of agent component of the target version, so as to achieve simultaneous update switching of the agent component in type and version; exemplarily, the second type of agent component of the target version may include the target agent component.

[0097] As can be seen from the above, in the device management method provided by the embodiment of the present application, if the status data indicates that the version of the proxy component set for the kth device in at least one monitoring device is different from the specified version, then in response to the version switching operation of the proxy component set for the kth device, management data for controlling the version change of the kth device is generated, and the management operation includes the version switching operation, the management data includes the version identifier of the proxy component of the specified version, and the proxy component is used to control the kth device to monitor the operating status of the target device. In this way, through the above operation, the management device can flexibly generate management data for controlling the switch version of the proxy component of the kth device under controllable conditions, thereby providing a data basis for the management device to flexibly control the version switching of the proxy component of the kth device through the proxy device.

[0098] Based on the foregoing embodiment, in the device management method provided in the embodiment of the present application, in response to the version switching operation of the proxy component set for the kth device, before generating the management data for controlling the version change of the kth device, the following operations may be performed:

[0099] An information acquisition request is sent to the proxy device, so that the proxy device sends the information acquisition request to the kth device; and configuration data of the kth device sent by the proxy device is received and stored.

[0100] The kth device is used to obtain and send the configuration data of the kth device to the proxy device in response to the information acquisition request; the configuration data of the kth device at least includes the version identifier of the proxy component set by the kth device.

[0101] In one implementation, the information acquisition request may include a device identification of the kth device, and may also include the type of configuration data of the kth device that the management device needs to obtain.

[0102] In one implementation, the information acquisition request may be generated in the following manner:

[0103] The management device generates an information acquisition request in response to a triggering or selection operation of an information acquisition option associated with the kth device displayed in the management window by a professional technician or a user.

[0104] In one embodiment, after receiving the information acquisition request, the proxy device can determine the kth device from at least one management device based on the device identifier of the kth device contained in the information acquisition request, and can also instruct the kth device to send the above-mentioned type of configuration data of the kth device to be obtained contained in the information acquisition request to the proxy device, so that the proxy device can send the above-mentioned type of configuration data to the management device.

[0105] In one implementation, after the management device receives the configuration data of the kth device, the configuration data of the kth device may be saved in a database set in the management device.

[0106] From the above, it can be seen that in the device management method provided in the embodiment of the present application, the management device sends an information acquisition request to the kth device through the proxy device, so that the proxy device sends the information acquisition request to the kth device, so that the kth device can obtain and send the configuration data of the kth device to the management device. In this way, through the above operation, the management device can flexibly and controllably obtain the configuration data of the kth device; and, by storing the configuration data of the kth device, the management device can achieve stable storage and management of the configuration data of the kth device; on the other hand, since the configuration data of the kth device includes the version identifier of the proxy component set by the kth device, in this way, the management device can not only obtain the version identifier of the proxy component set by the kth device in real time, but also provide a data basis for the management device to perform version switching operations on the proxy component of the kth device.

[0107] Based on the above embodiments, in the device management method provided in the embodiments of the present application, generating management data for controlling the version change of the kth device can be achieved in the following manner:

[0108] Determine a data storage address of a specified version of the proxy component; and generate management data for controlling version changes of the kth device based on the data storage address.

[0109] The data storage address is used for the proxy device to obtain the proxy component of a specified version.

[0110] In one implementation, the data storage space indicated by the data storage address may be set in the management device.

[0111] In one implementation, the management device may generate management data for controlling the version change of the kth device based on the version identifier of the agent component of the specified version and the above data storage address.

[0112] In one embodiment, after the proxy device obtains the management data including the data storage address sent by the management device, it can analyze the management data to obtain the above-mentioned data storage address, and can also generate a version acquisition request based on the version identifier of the specified version of the proxy component, and send the version acquisition request to the storage space or device indicated by the data storage address to obtain the specified version of the proxy component, and then send the specified version of the proxy component to the kth device, as well as an instruction instructing the kth device to switch the proxy component, thereby triggering the kth device to perform the proxy component switching operation based on the specified version of the proxy component.

[0113] Figure 3A schematic diagram of the process of switching the proxy component version provided in the embodiment of the present application is as follows: Figure 3 As shown, the process can be implemented by a first device combination 301, a second device combination 302 and a management device 303 on the server side.

[0114] Exemplarily, the first MAgent in the first device combination 301 and the second Magent in the second device combination 302 may be a first agent device and a second agent device in at least one agent device; the first octopus in the first device combination 301 and the second octopus in the second device combination 302 may be a first device and a second device associated with the first agent device and the second agent device, respectively.

[0115] Exemplarily, the management device may include AgentMan.

[0116] The process may include the following steps:

[0117] Step A1-1: The management device requests heartbeat information from the first proxy device.

[0118] Exemplarily, after the first MAgent receives the request for heartbeat information sent by AgentMan, it may trigger the execution of step A2.

[0119] Step A1-2: The management device requests the second proxy device for heartbeat information.

[0120] Exemplarily, the order of steps A1-1 to A1-2 may be adjusted or performed in parallel, which is not limited in the embodiments of the present application.

[0121] Step A2: The first agent device obtains the version of the Agent component in the first device.

[0122] Exemplarily, if the first agent device cannot obtain the version of the Agent component in the first device, it can be indicated that the first device is currently in an offline or abnormal state.

[0123] Exemplarily, the first agent device may also obtain the status of the Agent component in the first device.

[0124] Exemplarily, the first agent device may send the version and status of the Agent in the first device to AgentMan.

[0125] Step A3: data storage.

[0126] Exemplarily, after AgentMan obtains the version and status of the Agent in the first device, it may store them in the database.

[0127] Step A4: Issue a version upgrade instruction.

[0128] Exemplarily, if AgentMan determines that the version of the Agent in the first device is different from the specified version, it can generate management data for instructing the first device to perform a version switching operation, and add the data storage address of the target version of the agent component and the version identifier of the target version of the agent component in the management data.

[0129] Exemplarily, after the first MAgent receives the management data for instructing the first device to perform the version switching operation, step A5 may be performed.

[0130] Step A5: Download the target version of the proxy component.

[0131] Exemplarily, the first MAgent may send a download request for the target version of the agent component to the FileServer of the management device based on the data storage address, and obtain the target version of the agent component.

[0132] Step A6: Upgrade the proxy component.

[0133] Exemplarily, when the version of the agent component set in the first octopus is lower than the target version, the first Magent may instruct the first octopus to perform a version upgrade operation of the agent component based on the target version of the agent component.

[0134] Through the above process, any monitoring device, namely octopus, can realize flexible upgrade of agent components with the cooperation of management devices AgentMan and Magent.

[0135] As can be seen from the above, in the device management method provided by the embodiment of the present application, after the management device determines the data storage address of the specified version of the proxy component, it generates management data for controlling the version change of the kth device based on the data storage address, and the data storage address is used for the proxy device to obtain the specified version of the proxy component. In this way, through the above method, the management data contains the data storage address of the specified version of the proxy component, thereby providing an address basis for the proxy device to obtain the specified version of the proxy component, thereby improving the accuracy and flexibility of controlling the kth device to execute the version change of the proxy component through the proxy device.

[0136] Based on the foregoing embodiments, in the device management method provided in the embodiments of the present application, generating management data in response to a management operation on status data can also be implemented in the following manner:

[0137] If the state data indicates that a kth device in at least one monitoring device is not equipped with an agent component, in response to a management operation for the kth device not being equipped with an agent component, management data for instructing the kth device to install an agent component of a specified type is generated.

[0138] The proxy component is used to control the kth device to monitor the operating status of the target device; k is an integer greater than or equal to 1 and less than or equal to K; and K is the number of devices in at least one monitoring device.

[0139] Accordingly, if the status data indicates that the kth device in at least one monitoring device has been configured with an agent component, management data for instructing the kth device to install an agent component of a specified type may not be generated.

[0140] In one implementation, the management data for instructing the kth device to install an agent component of a specified type may be generated in the following manner:

[0141] The management window of the management device can display a device information list of devices that are not configured with proxy components. In response to the user's component installation operation on the kth device in the device information list, the device identification of the kth device and the specified type of proxy component are obtained, and management data is generated based on the device identification of the kth device and the specified type of proxy component.

[0142] Figure 4 Another structural diagram of the management window provided in the embodiment of the present application is as follows: Figure 4 As shown, after the cloud host option in the management window is triggered, the cloud host comparison data can be displayed. The figure shows a cloud host named SSO_Server, and its status is shut down, the collection status is data not reported, and a prompt information bar can be outputted "Agent is not installed, network card status data cannot be collected, please contact the tenant to install", and the options of one-click installation of Agent and manual installation of Agent can also be displayed in the prompt bar; exemplarily, if the one-click installation of Agent is triggered, the management device can send management data indicating the installation of a specified type of agent component associated with the cloud host named SSO_Server, and realize the installation of the agent component through the agent device control; exemplarily, if the manual installation of Agent option is triggered, the user of the agent device can manually download and install the specified type of Agent. Among them, the cloud host can include a device that is not configured with an Agent component.

[0143] From the above, it can be known that in the device management method provided by the embodiment of the present application, if the status data indicates that the kth device in at least one monitoring device is not configured with an agent component, then in response to the management operation for the kth device not being configured with an agent component, management data for instructing the kth device to install an agent component of a specified type is generated, and the agent component is used to control the kth device to monitor the operating status of the target device. In this way, through the above method, the management device can control whether to generate management data for controlling the kth device to install an agent component of a specified type based on the actual status of whether the kth device is configured with an agent component, thereby providing a data basis for the management device to manage the installation status of the agent component of any monitoring device, and also improving the flexibility of managing the installation status of the agent component of the monitoring device.

[0144] Based on the foregoing embodiments, in the device management method provided in the embodiments of the present application, generating management data in response to a management operation on status data can also be implemented in the following manner:

[0145] If the status data indicates that the device time of a kth device in at least one monitoring device is different from the device time of the management device, management data associated with the device time of the kth device is generated in response to a time setting operation for the device time of the kth device.

[0146] Among them, the management operation includes a time setting operation; the management data is used to trigger the device time of the kth device to be synchronized to the device time of the management device; k is an integer greater than or equal to 1 and less than or equal to K; K is the number of devices in at least one monitoring device.

[0147] Accordingly, if the status data indicates that the device time of the kth device in at least one monitoring device is the same as the device time of the management device, management data associated with the device time of the kth device may not be generated.

[0148] In one implementation, the time setting operation may include setting the device time of the kth device as the target time; illustratively, the target time may include the device time of the management device.

[0149] In one implementation, during the execution of the time setting operation for the device time of the kth device, the device identification and the target time of the kth device may be determined.

[0150] In one embodiment, the management device may send management data associated with the device time of the kth device to the proxy device, so that the proxy device can control the kth device to modify its device time to the target time based on the device identification of the kth device, thereby achieving synchronization between the device time of the kth device and the device time of the management device; exemplarily, the target time may be the same as or different from the device time of the management device.

[0151] Figure 5 A schematic diagram of a process of managing a monitoring device through a proxy device provided in an embodiment of the present application, such as Figure 5 As shown, the process may include the following steps:

[0152] Step B1: Perform operations on the status data displayed in the management window to generate management data.

[0153] Exemplarily, the management data may include data in the aforementioned embodiments for instructing the monitoring device to execute installation of a specified type of agent component, version switching operations, and device time synchronization of the monitoring device.

[0154] Exemplarily, the management data may also include a control instruction for controlling the start or shut down of the monitoring device.

[0155] Step B2: The management device obtains management data.

[0156] Step B3: Send the management data to the first MAgent.

[0157] Step B4: managing the first octopus based on the management data.

[0158] Exemplarily, after receiving the management data, the first MAgent may perform the management operation on the first octopus shown in the above embodiment according to the management data.

[0159] Through the above process, the management device can implement flexible and diversified management of the first octopus through the first MAgent.

[0160] As can be seen from the above, in the device management method provided by the embodiment of the present application, if the status data indicates that the device time of the kth device in at least one monitoring device is different from the device time of the management device, then in response to the time setting operation for the device time of the kth device, management data associated with the device time of the kth device is generated, and the management data is used to trigger the device time of the kth device to be synchronized to the device time of the management device. In this way, through the above operation, the management device can flexibly generate management data for controlling the time synchronization of the kth device under controllable circumstances, thereby providing a data basis for controlling the synchronization of the device time of the kth device; on this basis, by controlling the synchronization of the device time of the kth device, the accuracy of the kth device in monitoring the target device can also be improved.

[0161] Based on the above embodiments, the device management method provided in the embodiments of the present application obtains the status data sent by the proxy device, which can be implemented by the following steps:

[0162] Step C1: receiving a connection establishment request sent by a proxy device.

[0163] The connection establishment request includes device authentication information of the proxy device.

[0164] In one implementation, the device authentication information may include data such as a device identifier of the proxy device, an access key (Access Key, AK) of the proxy device, and a security key (Secret Key, SE).

[0165] In one implementation, the proxy device may generate and send a connection establishment request based on the device authentication information in response to a trigger operation of the user.

[0166] Step C2: In response to the connection establishment request, the proxy device is authenticated based on the device authentication information to obtain an authentication result.

[0167] In one embodiment, after receiving a connection establishment request, the management device may first forward the connection establishment request to a security authentication module so that the security authentication module can determine the legitimacy of the device authentication information carried in the connection establishment request, thereby obtaining an authentication result; exemplarily, the security authentication module may include Keystone.

[0168] Step C3: If the authentication result is an authentication pass status, a two-way communication connection is established between the management device and the proxy device.

[0169] Correspondingly, if the authentication result is an authentication failure state, a two-way communication connection between the management device and the agent device may not be established.

[0170] In one embodiment, the bidirectional communication connection may allow the management device to send data to the agent device, and also enable the management device to obtain the data sent by the agent device at any time.

[0171] In one implementation, the bidirectional communication connection may be a long connection.

[0172] Step C4: Acquire status data sent by the proxy device through a two-way communication connection.

[0173] Figure 6 A schematic diagram of a process for establishing a two-way communication connection provided in an embodiment of the present application, such as Figure 6 As shown, the process may include the following steps:

[0174] Step D1: Request to establish a two-way data connection.

[0175] Exemplarily, taking the first MAgent in the first device combination 301 as an example, it can obtain the device authentication information of the first MAgent, and generate and send a connection establishment request to AgentMan based on the device authentication information.

[0176] Exemplarily, the bidirectional data connection may be the bidirectional communication connection in the aforementioned embodiment.

[0177] Step D2: Perform device authentication.

[0178] Exemplarily, after receiving the connection establishment request, AgentMan may send the device authentication information in the connection establishment request to Keystone, so that Keystone can perform device identity authentication on the first MAgent.

[0179] Step D3: Establish a two-way communication connection.

[0180] Exemplarily, if the result of the device identity authentication is that the authentication is successful, a two-way communication connection may be established between the management device and the first MAgent.

[0181] Through the above process, a two-way communication connection can be flexibly established between the management device AgentMan and the agent device MAgent.

[0182] From the above, it can be seen that in the device management method provided in the embodiment of the present application, the management device receives a connection establishment request sent by the proxy device, and responds to the connection establishment request, performs identity authentication on the proxy device based on the device authentication information contained in the connection establishment request, and obtains an authentication result. Through the above operation, the security of the process of establishing a connection between the management device and the proxy device can be improved; and if the authentication result is an authentication pass status, a two-way communication connection is established between the management device and the proxy device, and the status data sent by the proxy device is obtained through the two-way communication connection. In this way, through the above-mentioned two-way communication connection, the flexibility of status data transmission between the management device and the proxy device can be improved.

[0183] When the device management method provided by the embodiment of the present application is applied to a management scenario of, for example, 100 monitoring devices, for example, for the version update of the proxy component of the monitoring device, it may take several hours to manually update the proxy component version of all monitoring devices in the related art, while the process of performing the version update using the method provided by the embodiment of the present application takes no more than ten minutes. In this way, while reducing labor costs, it can also reduce the overall time consumption of large-scale proxy component upgrades.

[0184] Based on the above embodiments, the present application also provides a device management device, which is arranged in a management device of a server. Figure 7 This is a schematic diagram of the structure of the device management device provided in the embodiment of the present application. Figure 7 As shown, the equipment management device 7 may include:

[0185] The transceiver module 701 is used to obtain the status data sent by the proxy device; wherein the status data is at least used to characterize the configuration status of at least one monitoring device managed by the proxy device; at least one monitoring device is used to monitor the operating status of the target device;

[0186] A processing module 702, configured to generate management data in response to a management operation on the state data;

[0187] The transceiver module 701 is further configured to send management data to the proxy device to trigger the proxy device to manage at least one monitoring device based on the management data.

[0188] In some embodiments, the processing module 702 is used to generate management data for controlling the kth device to switch to a second state in response to a state switching operation for the first state if the state data indicates that the kth device in at least one monitoring device is in a first state; wherein the management operation includes a state switching operation; k is an integer greater than or equal to 1 and less than or equal to K; and K is the number of devices in the at least one monitoring device.

[0189] In some embodiments, the processing module 702 is used to generate management data for controlling the version change of the kth device in response to a version switching operation of the proxy component set for the kth device if the status data represents that the version of the proxy component set for the kth device in at least one monitoring device is different from the specified version; wherein the management operation includes a version switching operation; the management data includes a version identifier of the specified version of the proxy component; the proxy component is used to control the kth device to monitor the operating status of the target device; k is an integer greater than or equal to 1 and less than or equal to K; and K is the number of devices in at least one monitoring device.

[0190] In some embodiments, the transceiver module 701 is used to send an information acquisition request to the proxy device, so that the proxy device sends the information acquisition request to the kth device; wherein the kth device is used to respond to the information acquisition request, obtain and send the configuration data of the kth device to the proxy device; the configuration data of the kth device at least includes a version identifier of the proxy component set by the kth device;

[0191] The transceiver module 701 is further configured to receive and store configuration data of the kth device sent by the proxy device.

[0192] In some embodiments, the processing module 702 is used to determine a data storage address of a specified version of the proxy component; wherein the data storage address is used for the proxy device to obtain the specified version of the proxy component;

[0193] The processing module 702 is further configured to generate management data for controlling a version change of the kth device based on the data storage address.

[0194] In some embodiments, the processing module 702 is used to generate management data for instructing the kth device to install a specified type of agent component in response to a management operation for the kth device not being configured with the agent component if the status data indicates that the kth device in at least one monitoring device is not configured with the agent component; wherein the agent component is used to control the kth device to monitor the operating status of the target device; k is an integer greater than or equal to 1 and less than or equal to K; and K is the number of devices in the at least one monitoring device.

[0195] In some embodiments, the processing module 702 is used to generate management data associated with the device time of the kth device in response to a time setting operation for the device time of the kth device if the status data represents that the device time of the kth device in at least one monitoring device is different from the device time of the management device; wherein the management operation includes a time setting operation; the management data is used to trigger the synchronization of the device time of the kth device to the device time of the management device; k is an integer greater than or equal to 1 and less than or equal to K; and K is the number of devices in the at least one monitoring device.

[0196] In some embodiments, the transceiver module 701 is used to receive a connection establishment request sent by a proxy device; wherein the connection establishment request includes device authentication information of the proxy device;

[0197] The processing module 702 is used to respond to the connection establishment request, authenticate the proxy device based on the device authentication information, and obtain an authentication result; if the authentication result is an authentication pass state, establish a two-way communication connection between the management device and the proxy device;

[0198] The transceiver module 701 is used to obtain status data sent by the proxy device through a two-way communication connection.

[0199] Based on the above embodiments, the present application also provides a management device. Figure 8 A schematic diagram of the structure of the management device provided in the embodiment of the present application, such as Figure 8 As shown, the management device 8 may include a processor 801 and a memory 802 ; wherein the memory 802 stores a computer program, and when the computer program is executed by the processor 801 , it can implement the device management method provided in any of the previous embodiments.

[0200] Based on the foregoing embodiments, an embodiment of the present application further provides a computer-readable storage medium, in which a computer program is stored. When the computer program is executed by a processor of an electronic device, the device management method provided in any of the previous embodiments can be implemented.

[0201] Based on the foregoing embodiments, an embodiment of the present application further provides a computer program product, which includes a computer program; when the computer program is executed by a processor of an electronic device, it can implement a device management method provided in any of the previous embodiments.

[0202] The above description of various embodiments tends to emphasize the differences between the various embodiments. The same or similar aspects can be referenced to each other, and for the sake of brevity, they will not be repeated herein.

[0203] The methods disclosed in the various method embodiments provided in this application can be arbitrarily combined without conflict to obtain new method embodiments.

[0204] The features disclosed in the various product embodiments provided in this application can be arbitrarily combined without conflict to obtain new product embodiments.

[0205] The features disclosed in the various method or device embodiments provided in this application can be arbitrarily combined without conflict to obtain new method embodiments or device embodiments.

[0206] It should be noted that the above-mentioned computer-readable storage medium can be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), a magnetic random access memory (FRAM), a flash memory (Flash Memory), a magnetic surface memory, an optical disc, or a compact disc read-only memory (CD-ROM) and other memories; it can also be various electronic devices including one or any combination of the above-mentioned memories, such as mobile phones, computers, tablet devices, personal digital assistants, etc.

[0207] It should be noted that, in this article, the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "comprises a ..." does not exclude the existence of other identical elements in the process, method, article or device including the element.

[0208] The serial numbers of the above-mentioned embodiments of the present application are for description only and do not represent the advantages or disadvantages of the embodiments.

[0209] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus necessary general hardware nodes, and of course can also be implemented by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present application, or the part that contributes to the prior art, can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk), and includes a number of instructions for a terminal device (which can be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in each embodiment of the present application.

[0210] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0211] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0212] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0213] The above are only preferred embodiments of the present application, and are not intended to limit the patent scope of the present application. Any equivalent structure or equivalent process transformation made using the contents of the present application specification and drawings, or directly or indirectly applied in other related technical fields, are also included in the patent protection scope of the present application.

Claims

1. A device management method, characterized in that: The method comprises: The management device at the server side obtains the status data sent by the proxy device; wherein the status data is at least used to represent the configuration status of at least one monitoring device managed by the proxy device; the at least one monitoring device is used to monitor the operating status of the target device; generating management data in response to a management operation on the state data; The management data is sent to the agent device to trigger the agent device to manage the at least one monitoring device based on the management data.

2. The method according to claim 1, characterized in that The generating management data in response to the management operation on the state data comprises: If the status data indicates that the kth device in the at least one monitoring device is in a first state, in response to a state switching operation for the first state, management data for controlling the kth device to switch to a second state is generated; wherein the management operation includes the state switching operation; k is an integer greater than or equal to 1 and less than or equal to K; and K is the number of devices in the at least one monitoring device.

3. The method according to claim 1, characterized in that The generating management data in response to the management operation on the state data comprises: If the status data indicates that the version of the proxy component set for the kth device in the at least one monitoring device is different from the specified version, in response to a version switching operation of the proxy component set for the kth device, management data for controlling the version change of the kth device is generated; wherein the management operation includes the version switching operation; the management data includes the version identifier of the specified version of the proxy component; the proxy component is used to control the kth device to monitor the operating status of the target device; k is an integer greater than or equal to 1 and less than or equal to K; K is the number of devices in the at least one monitoring device.

4. The method according to claim 3, characterized in that Before generating management data for controlling the version change of the kth device in response to the version switching operation of the proxy component set for the kth device, the method further includes: Sending an information acquisition request to the proxy device, so that the proxy device sends the information acquisition request to the kth device; wherein the kth device is used to respond to the information acquisition request, acquire and send configuration data of the kth device to the proxy device; the configuration data of the kth device at least includes a version identifier of the proxy component set by the kth device; Receive and store the configuration data of the kth device sent by the proxy device.

5. The method according to claim 3, characterized in that: The generating of management data for controlling the version change of the kth device includes: Determine a data storage address of the specified version of the proxy component; wherein the data storage address is used for the proxy device to obtain the specified version of the proxy component; The management data for controlling a changed version of the k-th device is generated based on the data storage address.

6. The method according to claim 1, characterized in that The generating management data in response to the management operation on the state data comprises: If the status data indicates that the kth device in the at least one monitoring device is not configured with an agent component, in response to a management operation for the kth device not being configured with the agent component, management data is generated to instruct the kth device to install an agent component of a specified type; wherein the agent component is used to control the kth device to monitor the operating status of the target device; k is an integer greater than or equal to 1 and less than or equal to K; and K is the number of devices in the at least one monitoring device.

7. The method according to claim 1, characterized in that The generating management data in response to the management operation on the state data comprises: If the status data represents that the device time of the kth device in the at least one monitoring device is different from the device time of the management device, management data associated with the device time of the kth device is generated in response to a time setting operation for the device time of the kth device; wherein the management operation includes the time setting operation; the management data is used to trigger the synchronization of the device time of the kth device to the device time of the management device; k is an integer greater than or equal to 1 and less than or equal to K; and K is the number of devices in the at least one monitoring device.

8. The method according to any one of claims 1 to 7, characterized in that: The management device of the server obtains the status data sent by the proxy device, including: receiving a connection establishment request sent by the proxy device; wherein the connection establishment request includes device authentication information of the proxy device; In response to the connection establishment request, performing identity authentication on the proxy device based on the device authentication information to obtain an authentication result; If the authentication result is an authentication pass state, establishing a two-way communication connection between the management device and the proxy device; The status data sent by the proxy device is obtained through the two-way communication connection.

9. A device management device, characterized in that: The device management device is arranged on a management device at the server end; the device management device comprises: A transceiver module, used to obtain status data sent by the proxy device; wherein the status data is at least used to characterize the configuration status of at least one monitoring device managed by the proxy device; the at least one monitoring device is used to monitor the operating status of the target device; a processing module, configured to generate management data in response to a management operation on the state data; The transceiver module is further configured to send the management data to the agent device to trigger the agent device to manage the at least one monitoring device based on the management data.

10. A management device for a server, characterized in that: The management device includes a processor and a memory; wherein a computer program is stored in the memory; when the computer program is executed by the processor, the device management method according to any one of claims 1 to 8 can be implemented.

11. A computer-readable storage medium, characterized in that: The storage medium stores a computer program; when the computer program is executed by a processor of an electronic device, the device management method according to any one of claims 1 to 8 can be implemented.

12. A computer program product, characterized in that The program product includes a computer program; when the computer program is executed by a processor of an electronic device, the device management method according to any one of claims 1 to 8 can be implemented.

Images