A host monitoring event processing method, device, equipment and storage medium
By identifying host monitoring events and querying resource usage records, obtaining hardware and network parameters, performing status detection, and generating abnormal events, the problems of misjudgment and inconvenient acceptance in the operation of bare metal computing power are solved, and efficient anomaly identification and traceability are achieved.
Patent Information
- Application Number
- CN202611261380.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2026-08-19
- Publication Date
- 2026-11-06
AI Technical Summary
In bare metal computing scenarios, the probability of misjudging host monitoring events is high, and bare metal computing power acceptance and problem tracing are inconvenient.
By receiving host monitoring events and identifying their types, querying resource usage records, updating scheduling monitoring records, obtaining hardware and network parameters, detecting processor power saving status and network bandwidth, and generating abnormal events.
It reduces the probability of misjudgment in shutdown or restart scenarios, improves the efficiency of bare metal computing power acceptance and problem tracing, and realizes automatic identification of abnormal environments.
Smart Images
Figure CN123048322A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of bare metal computing resource operation monitoring technology, and in particular to a host monitoring event processing method, apparatus, equipment and storage medium. Background Technology
[0002] In bare-metal computing scenarios, the entire process of a host instance from startup and operation to shutdown is typically monitored by a host-side monitoring agent continuously reporting its status to the region management service. The reported status includes not only login and heartbeat information, but also various host monitoring events such as successful startup, running, shutdown, restart, and GPU anomalies. These events are crucial for determining whether a host has truly started successfully, is operating healthily, and has experienced any hardware anomalies. In related technologies, host monitoring events are often processed only as independent logs or simple status feedback. This can easily lead to misjudgments in shutdown or restart scenarios. Furthermore, these technologies are not conducive to bare-metal computing power acceptance testing and problem tracing.
[0003] Therefore, how to solve the above-mentioned technical defects has become a technical problem that urgently needs to be solved by those skilled in the art. Summary of the Invention
[0004] The purpose of this application is to provide a host monitoring event processing method, device, equipment and storage medium that can reduce the probability of misjudgment in shutdown or restart scenarios and facilitate bare metal computing power acceptance and problem tracing.
[0005] To address the aforementioned technical problems, this application provides a host monitoring event processing method, comprising: Receive host monitoring events and identify the type of the host monitoring events; If the host monitoring event is a host shutdown event or a host restart event, then query the corresponding resource usage records; If the resource usage record has not ended, update the shutdown time in the corresponding scheduling monitoring record and issue a master shutdown notification event; If the host monitoring event is a successful host startup event, then update the startup time and the most recent running and reporting time in the scheduling monitoring record; If the host monitoring event is a successful host startup event, then the network parameters and hardware parameters are obtained and written into the scheduling monitoring record; The processor power-saving status is detected based on the hardware parameters, and the network bandwidth is detected based on the network parameters. If the processor's power-saving mode is not turned off or the network bandwidth is abnormal, a corresponding abnormal event will be generated.
[0006] In some embodiments, it also includes: If the host monitoring event is a graphics processor status event, then a corresponding graphics processor status processor is selected according to the graphics processor status type to process the graphics processor status event through the selected graphics processor status processor; wherein, when processing the graphics processor status event, the virtual machine scheduling record corresponding to the bare metal computing power scheduling record is queried; if a virtual machine scheduling record is found, the graphics processor status is associated with the virtual machine scheduling record.
[0007] In some embodiments, it also includes: If the host monitoring event is a host running status event, then refresh the most recent running reporting time in the scheduling monitoring record.
[0008] In some embodiments, it also includes: The host status and graphics processor status are asynchronously reported to the upper-layer system, and the corresponding events are recorded in the local event system.
[0009] In some embodiments, it also includes: If a virtual machine scheduling record is found, the virtual machine scheduling identifier is reported to the upper-layer system.
[0010] In some embodiments, it also includes: Receive a login request and verify the login request; If the verification passes, a client mapping relationship is established based on the monitoring type, operating environment, and host identifier.
[0011] In some embodiments, it also includes: Establish a long-connection listening channel for the host monitoring server; the long-connection listening channel for the host monitoring server is used to receive the host monitoring events and the login request.
[0012] To address the aforementioned technical problems, this application also provides a host monitoring event processing device, comprising: The identification unit is used to receive host monitoring events and identify the type of the host monitoring events; The query unit is used to query the corresponding resource usage records if the host monitoring event is a host shutdown event or a host restart event. The first update unit is used to update the shutdown time in the corresponding scheduling monitoring record and issue a host shutdown notification event if the resource usage record has not ended. The second update unit is used to update the startup time and the most recent running and reporting time in the scheduling monitoring record if the host monitoring event is a successful host startup event. The writing unit is used to obtain network parameters and hardware parameters and write the network parameters and hardware parameters into the scheduling monitoring record if the host monitoring event is a host boot success event; The detection unit is used to detect the processor's power-saving status based on the hardware parameters and to detect the network bandwidth based on the network parameters. The generation unit is used to generate corresponding abnormal events if the processor's power-saving state is not turned off or the network bandwidth is abnormal.
[0013] To address the aforementioned technical problems, this application also provides an electronic device, comprising: Memory, used to store computer programs; A processor is configured to implement the steps of the host monitoring event handling method as described above when executing the computer program.
[0014] To address the aforementioned technical problems, this application also provides a computer-readable storage medium storing a computer program, which, when executed by a processor, implements the steps of the host monitoring event handling method described above.
[0015] The host monitoring event handling method provided in this application includes: receiving a host monitoring event and identifying the type of the host monitoring event; if the host monitoring event is a host shutdown event or a host restart event, querying the corresponding resource usage record; if the resource usage record has not ended, updating the shutdown time in the corresponding scheduling monitoring record and issuing a host shutdown notification event; if the host monitoring event is a host successful startup event, updating the startup time and the most recent running reporting time in the scheduling monitoring record; if the host monitoring event is a host successful startup event, obtaining network parameters and hardware parameters, and writing the network parameters and hardware parameters into the scheduling monitoring record; performing processor power saving status detection based on the hardware parameters, and performing network bandwidth detection based on the network parameters; if the processor power saving status is not turned off or the network bandwidth is abnormal, generating a corresponding abnormal event.
[0016] As can be seen, the host monitoring event handling method provided in this application, in the case of shutdown or restart, queries the corresponding resource usage records. The fact that the resource usage record has not ended indicates that the host monitoring event is a valid running instance. Subsequent operations are then performed when the host monitoring event is a valid running instance, thus reducing the probability of misjudgment due to premature termination of bare metal computing power scheduling records. When the host successfully boots up, hardware and network parameters are obtained and written into the scheduling monitoring record. This provides a data foundation for subsequent acceptance, traceability, and anomaly comparison of bare metal computing power, improving the efficiency of bare metal computing power acceptance and problem tracing. Furthermore, this application performs processor power-saving status detection based on hardware parameters and network bandwidth detection based on network parameters. When processor power-saving status is not disabled or network bandwidth is abnormal, corresponding abnormal events are generated, thus achieving automatic identification of abnormal environments.
[0017] The host monitoring event processing device, equipment, and computer-readable storage medium provided in this application all have the aforementioned technical effects. Attached Figure Description
[0018] To more clearly illustrate the technical solutions in the embodiments of this application, the drawings used in the prior art and embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.
[0019] Figure 1 A flowchart illustrating a host monitoring event processing method provided in an embodiment of this application; Figure 2 This is a schematic diagram of a host monitoring agent and event distribution process provided in an embodiment of this application; Figure 3 A schematic diagram of a host status event processing flow provided in an embodiment of this application; Figure 4 This is a schematic diagram illustrating the process of hardware network snapshot persistence and abnormal derivation after a host is powered on, as provided in an embodiment of this application. Figure 5 This is a schematic diagram of a GPU state event processing flow provided in an embodiment of this application; Figure 6 This is a flowchart illustrating a host monitoring event processing device provided in an embodiment of this application; Figure 7 This is a schematic diagram of an electronic device provided in an embodiment of this application. Detailed Implementation
[0020] The core of this application is to provide a host monitoring event processing method, device, equipment and storage medium, which can reduce the probability of misjudgment in shutdown or restart scenarios, and is conducive to bare metal computing power acceptance and problem tracing.
[0021] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.
[0022] Please refer to Figure 1 , Figure 1 This is a flowchart illustrating a host monitoring event processing method provided in an embodiment of this application. (Refer to...) Figure 1 As shown, the method includes: S101: Receive host monitoring events and identify the type of the host monitoring events.
[0023] The execution entity in this embodiment is a region management service. The region management service receives host monitoring events reported by the host monitoring agent. The types of host monitoring events include host successful boot events, host running status events, host shutdown events, host restart events, and GPU status events. Additionally, the region management service can also receive login requests and heartbeat requests.
[0024] Login requests establish a one-to-one mapping between host identifiers and persistent connection channels. Heartbeat requests maintain connection validity. Successful host boot events generate host runtime snapshots and complete boot acceptance testing. Host runtime status events refresh runtime heartbeat timestamps. Host shutdown or reboot events record shutdown times, persist events to the database, and trigger event recycling. GPU status events update GPU monitoring status and report anomalies to the upper-layer system.
[0025] S102: If the host monitoring event is a host shutdown event or a host restart event, then query the corresponding resource usage records.
[0026] S103: If the resource usage record has not ended, update the shutdown time in the corresponding scheduling monitoring record and issue a host shutdown notification event.
[0027] If the host monitoring event is a host shutdown or host restart event, the most recent bare metal computing power scheduling record is retrieved based on the host identifier (e.g., host MAC address). After obtaining the bare metal computing power scheduling record, the resource usage record associated with it is further queried. The resource usage record is used to determine whether the host monitoring event belongs to a valid running instance. If the resource usage record has not ended, the host monitoring event belongs to a valid running instance. Conversely, if the resource usage record has ended, the host monitoring event does not belong to a valid running instance, and therefore, it is not necessary to update the shutdown time in the corresponding scheduling monitoring record, and no host shutdown notification event is issued. If no corresponding bare metal computing power scheduling record is found, an error log is recorded and the process ends.
[0028] If the host monitoring event pertains to a valid running instance, the shutdown time in the corresponding scheduling monitoring record is updated, a shutdown event is written, and a host shutdown notification event is published to drive subsequent resource reclamation or termination. The host shutdown event and host restart event can share the same state processor, which handles both events. Furthermore, the type of host monitoring event distinguishes the subsequent resource termination or reclamation path.
[0029] The scheduling and monitoring records can include power-on time, power-off time, most recent running and reporting time, hardware information, network information, and GPU status.
[0030] S104: If the host monitoring event is a host startup success event, then update the startup time and the most recent running report time in the scheduling monitoring record.
[0031] S105: If the host monitoring event is a host startup success event, then obtain the network parameters and hardware parameters, and write the network parameters and hardware parameters into the scheduling monitoring record.
[0032] S106: Detect processor power-saving status based on the hardware parameters, and detect network bandwidth based on the network parameters.
[0033] S107: If the processor power saving state is not turned off or the network bandwidth is abnormal, a corresponding abnormal event will be generated.
[0034] If the host monitoring event is a successful host startup event, then query the most recent bare metal computing power scheduling record based on the host identifier, and update the startup time and the most recent running and reporting time in the scheduling monitoring record corresponding to the bare metal computing power scheduling record.
[0035] In addition, network parameters and hardware parameters are obtained. Hardware parameters may include at least one of the following: CPU information, motherboard information, memory information, graphics card information, graphics card hardware identifier, network card speed, and CPU power-saving status. Preferably, the network and hardware information are serialized as structured objects and written as a whole into the scheduling and monitoring record.
[0036] When CPU power saving is enabled, a CPU power saving not disabled event is generated. When the network card speed includes a preset low bandwidth flag, a network bandwidth anomaly event is generated.
[0037] In some embodiments, it also includes: If the host monitoring event is a host running status event, then refresh the most recent running reporting time in the scheduling monitoring record.
[0038] If the host monitoring event is a host running status event, then refresh the most recent running reporting time in the scheduling monitoring record.
[0039] In some embodiments, it also includes: If the host monitoring event is a graphics processor status event, then a corresponding graphics processor status processor is selected according to the graphics processor status type to process the graphics processor status event through the selected graphics processor status processor; wherein, when processing the graphics processor status event, the virtual machine scheduling record corresponding to the bare metal computing power scheduling record is queried; if a virtual machine scheduling record is found, the graphics processor status is associated with the virtual machine scheduling record.
[0040] When a host monitoring event is a GPU status event, the corresponding GPU status handler is selected based on the GPU status type, and the event is processed by the appropriate GPU status handler. The GPU status and anomaly description in the scheduling monitoring record are updated. Specifically, when processing a GPU status event, the virtual machine scheduling record corresponding to the bare metal computing power scheduling record is queried. If a virtual machine scheduling record exists, the GPU anomaly is simultaneously associated with that record.
[0041] GPU status processors can be registered with the processor factory during system initialization to support the categorized handling of different GPU anomaly types. Different GPU status processors can correspond to different scenarios such as no driver, no GPU, GPU anomaly, and GPU memory anomaly. The GPU status processor can write the GPU status code, anomaly description, and timestamp into the hardware snapshot or GPU status field in the scheduling monitoring record.
[0042] In some embodiments, it also includes: The host status and GPU status are asynchronously reported to the upper-layer system, and the corresponding events are recorded in the local event system.
[0043] In addition, in some embodiments, if a virtual machine scheduling record is found, the virtual machine scheduling identifier is reported to the upper-layer system.
[0044] When a virtual machine scheduling record exists, the corresponding virtual machine scheduling identifier should be attached when reporting.
[0045] In some embodiments, it also includes: Receive a login request and verify the login request; If the verification passes, a unique client mapping relationship is established based on the monitoring type, operating environment, and host identifier.
[0046] The system receives login requests from host monitoring agents and verifies the signature, timestamp, and host identifier. Upon successful login verification, a unique client mapping relationship is established based on the monitoring type (e.g., bare metal computing power, virtual machine), operating environment (e.g., Windows, Linux), and host identifier. The key value of the unique client mapping relationship must include at least one of the following: monitoring type, operating environment, and host identifier (e.g., MAC address), to ensure that only one valid monitoring connection exists for the same host under the same operating environment. The signature is preferably generated based on a combination of license identifier, pre-shared key, and timestamp to prevent unauthorized agent access.
[0047] Once login verification is successful, a unique mapping is established between the current channel and the monitoring agent of that host, using the monitoring type, operating environment, and host MAC address as a composite key. If the same composite key already exists and the old channel is still valid, new duplicate login requests are rejected. If the old channel has expired, the old mapping is removed and a new channel is accepted. This ensures that only one valid monitoring connection is ever established for the same host under the same operating environment.
[0048] In some embodiments, it also includes: Establish a long-connection listening channel for the host monitoring server; the long-connection listening channel for the host monitoring server is used to receive monitoring requests.
[0049] Establish a long-lived listening channel for the host monitoring server to receive JSON-RPC monitoring requests sent by the host monitoring agent.
[0050] Based on the above embodiments, the host monitoring agent and event distribution process can be referred to Figure 2As shown, the host monitoring agent reports login requests, heartbeat requests, host successful boot events, host running status events, host shutdown events, host restart events, and GPU status events to the HostMonitorServer, i.e., the region management service. For login requests, the region management service performs login verification. For heartbeat requests, host successful boot events, host running status events, host shutdown events, host restart events, and GPU status events, the appropriate status handler is selected based on the method identifier for processing.
[0051] The host status event handling process can be referenced. Figure 3 As shown, the area management service receives host status reports. It verifies whether the long-connection channel is logged in. If logged in, it queries the latest bare-metal scheduling record based on the host MAC address. It then determines the type of the monitoring event. If it's a host running status event, it refreshes the most recent running report time. If it's a host shutdown or restart event, it continues querying resource usage records; based on the resource usage record status, it confirms whether the current event still belongs to a valid running instance. If it belongs to a valid running instance, it updates the scheduling monitoring record and performs subsequent processing.
[0052] The process for hardware network snapshot persistence and anomaly propagation after host boot can be found in [reference needed]. Figure 4 As shown. The area management service receives a successful host boot event. It matches the currently running bare metal scheduling record. It collects network parameters, which may include IP address, subnet mask, and gateway. It collects hardware parameters, which may include CPU, motherboard, memory, graphics card, graphics card hardware identifier, network card speed, and CPU power-saving status. It writes the network and hardware parameters into the scheduling monitoring record, updating the boot time and the most recent reported time. It performs environmental verification on the CPU power-saving status and network card speed; when the CPU power-saving status is enabled, it generates a CPU power-saving not disabled event. When the network card speed contains a preset low-speed bandwidth identifier, it generates a network bandwidth abnormality event.
[0053] The GPU status event handling process can be referenced. Figure 5 As shown. The region management service receives GPU status events. Based on the GPU status code, it selects the corresponding GPU status processor from the GPU processor factory. It queries the running bare metal scheduling record based on the host identifier. It queries the scheduling monitoring record associated with this bare metal scheduling record. It updates the GPU status, exception description, and timestamp. It generates a GPU exception BM event. It then checks the virtual machine scheduling record; if it exists, it reports it to the upper-layer system along with the virtual machine scheduling identifier.
[0054] In summary, the host monitoring event handling method provided in this application queries the relevant resource usage records in shutdown or restart scenarios. The fact that the resource usage record has not ended indicates that the host monitoring event is a valid running instance. Subsequent operations are then performed only when the host monitoring event is a valid running instance, thus reducing the probability of misjudgments due to premature termination of bare metal computing power scheduling records. When the host successfully boots up, hardware and network parameters are obtained and written into the scheduling monitoring record. This provides a data foundation for subsequent acceptance testing, traceability, and anomaly comparison of bare metal computing power, improving the efficiency of bare metal computing power acceptance and problem tracing. Furthermore, this application performs processor power-saving status detection based on hardware parameters and network bandwidth detection based on network parameters. When processor power-saving status is not disabled or network bandwidth is abnormal, corresponding abnormal events are generated, thus achieving automatic identification of abnormal environments.
[0055] This application also provides a host monitoring event processing apparatus, which is described below and can be referred to in conjunction with the method described above. Please refer to... Figure 6 , Figure 6 This is a schematic diagram of a host monitoring event processing device provided in an embodiment of this application, combined with... Figure 6 As shown, the device includes: The identification unit 10 is used to receive host monitoring events and identify the type of the host monitoring events; The query unit 20 is used to query the corresponding resource usage records if the host monitoring event is a host shutdown event or a host restart event. The first update unit 30 is used to update the shutdown time in the corresponding scheduling monitoring record and issue a host shutdown notification event if the resource usage record has not ended. The second update unit 40 is used to update the startup time and the most recent running and reporting time in the scheduling monitoring record if the host monitoring event is a successful host startup event. The writing unit 50 is used to obtain network parameters and hardware parameters and write the network parameters and hardware parameters into the scheduling monitoring record if the host monitoring event is a host boot success event. The detection unit 60 is used to detect the processor power-saving status based on the hardware parameters and to detect the network bandwidth based on the network parameters. The generation unit 70 is used to generate corresponding abnormal events if the processor power-saving state is not turned off or the network bandwidth is abnormal.
[0056] In some embodiments, it also includes: The selection unit is configured to, if the host monitoring event is a graphics processor status event, select the corresponding graphics processor status processor according to the graphics processor status type, so as to process the graphics processor status event through the selected graphics processor status processor; wherein, when processing the graphics processor status event, the virtual machine scheduling record corresponding to the bare metal computing power scheduling record is queried; if a virtual machine scheduling record is found, the graphics processor status is associated with the virtual machine scheduling record.
[0057] In some embodiments, it also includes: The refresh unit is used to refresh the most recent running reporting time in the scheduling monitoring record if the host monitoring event is a host running status event.
[0058] In some embodiments, it also includes: The reporting unit is used to asynchronously report the host status and graphics processor status to the upper-layer system and record the corresponding events in the local event system.
[0059] In some embodiments, it also includes: The virtual machine scheduling record query unit is used to report the virtual machine scheduling identifier to the upper-layer system if a virtual machine scheduling record is found.
[0060] In some embodiments, it also includes: A login verification unit is used to receive login requests and verify the login requests; The first establishment unit is used to establish a client mapping relationship based on the monitoring type, operating environment, and host identifier if the verification passes.
[0061] In some embodiments, it also includes: The second establishment unit is used to establish a long-connection listening channel for the host monitoring server; the long-connection listening channel for the host monitoring server is used to receive the host monitoring events and the login requests.
[0062] The host monitoring event processing device provided in this application queries relevant resource usage records during shutdown or restart scenarios. The presence of an unfinished resource usage record indicates that the host monitoring event is a valid running instance. Subsequent operations are then performed only when the host monitoring event is a valid running instance, reducing the probability of misjudgments due to premature termination of bare metal computing power scheduling records. Upon successful host startup, hardware and network parameters are acquired and written into the scheduling monitoring record. This provides a data foundation for subsequent acceptance testing, traceability, and anomaly comparison of bare metal computing power, improving the efficiency of bare metal computing power acceptance and problem tracing. Furthermore, this application performs processor power-saving status detection based on hardware parameters and network bandwidth detection based on network parameters. When processor power-saving status is not disabled or network bandwidth is abnormal, corresponding abnormal events are generated, thus achieving automatic identification of abnormal environments.
[0063] This application also provides an electronic device, referenced... Figure 7 As shown, the device includes a memory 1 and a processor 2.
[0064] Memory 1 is used to store computer programs; Processor 2 is used to execute computer programs to perform the following steps: The system receives host monitoring events and identifies their types. If the event is a host shutdown or restart event, it queries the corresponding resource usage record. If the resource usage record is not yet complete, it updates the shutdown time in the corresponding scheduling monitoring record and issues a host shutdown notification event. If the event is a successful host startup event, it updates the startup time and the most recent running report time in the scheduling monitoring record. It acquires network parameters and hardware parameters and writes them into the scheduling monitoring record. It performs processor power-saving status detection based on the hardware parameters and network bandwidth detection based on the network parameters. If processor power-saving status is not disabled or network bandwidth is abnormal, it generates a corresponding abnormal event.
[0065] For a description of the equipment provided in this application, please refer to the above method embodiments; further details will not be provided here.
[0066] This application also provides a computer-readable storage medium storing a computer program, which, when executed by a processor, can perform the following steps: The system receives host monitoring events and identifies their types. If the event is a host shutdown or restart event, it queries the corresponding resource usage record. If the resource usage record is not yet complete, it updates the shutdown time in the corresponding scheduling monitoring record and issues a host shutdown notification event. If the event is a successful host startup event, it updates the startup time and the most recent running report time in the scheduling monitoring record. It acquires network parameters and hardware parameters and writes them into the scheduling monitoring record. It performs processor power-saving status detection based on the hardware parameters and network bandwidth detection based on the network parameters. If processor power-saving status is not disabled or network bandwidth is abnormal, it generates a corresponding abnormal event.
[0067] The computer-readable storage medium may include various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.
[0068] For a description of the computer-readable storage medium provided in this application, please refer to the above method embodiments; further details will not be repeated here.
[0069] The various embodiments in this specification are described in a progressive manner, with each embodiment focusing on its differences from other embodiments. Similar or identical parts between embodiments can be referred to interchangeably. For the apparatuses, devices, and computer-readable storage media disclosed in the embodiments, since they correspond to the methods disclosed in the embodiments, the descriptions are relatively simple; relevant details can be found in the method section.
[0070] Those skilled in the art will further recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of both. To clearly illustrate the interchangeability of hardware and software, the components and steps of the various examples have been generally described in terms of functionality in the foregoing description. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.
[0071] The steps of the methods or algorithms described in conjunction with the embodiments disclosed herein can be implemented directly by hardware, a software module executed by a processor, or a combination of both. The software module can be located in random access memory (RAM), main memory, read-only memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium known in the art.
[0072] The host monitoring event processing method, apparatus, device, and storage medium provided in this application have been described in detail above. Specific examples have been used to illustrate the principles and implementation methods of this application. The descriptions of the embodiments above are only for the purpose of helping to understand the method and core ideas of this application. It should be noted that those skilled in the art can make several improvements and modifications to this application without departing from the principles of this application, and these improvements and modifications also fall within the protection scope of this application.
Claims
1. A host monitoring event handling method, characterized in that, include: Receive host monitoring events and identify the type of the host monitoring events; If the host monitoring event is a host shutdown event or a host restart event, then query the corresponding resource usage records; If the resource usage record has not ended, update the shutdown time in the corresponding scheduling monitoring record and issue a master shutdown notification event; If the host monitoring event is a successful host startup event, then update the startup time and the most recent running and reporting time in the scheduling monitoring record; If the host monitoring event is a successful host startup event, then the network parameters and hardware parameters are obtained and written into the scheduling monitoring record; The processor power-saving status is detected based on the hardware parameters, and the network bandwidth is detected based on the network parameters. If the processor's power-saving mode is not turned off or the network bandwidth is abnormal, a corresponding abnormal event will be generated.
2. The host monitoring event processing method according to claim 1, characterized in that, Also includes: If the host monitoring event is a graphics processor status event, then the corresponding graphics processor status processor is selected according to the graphics processor status type, so that the graphics processor status event is processed by the selected graphics processor status processor; wherein, when processing the graphics processor status event, the virtual machine scheduling record corresponding to the bare metal computing power scheduling record is queried; if the virtual machine scheduling record is found, the graphics processor status is associated with the virtual machine scheduling record.
3. The host monitoring event processing method according to claim 1, characterized in that, Also includes: If the host monitoring event is a host running status event, then refresh the most recent running reporting time in the scheduling monitoring record.
4. The host monitoring event processing method according to claim 2, characterized in that, Also includes: The host status and graphics processor status are asynchronously reported to the upper-layer system, and the corresponding events are recorded in the local event system.
5. The host monitoring event processing method according to claim 4, characterized in that, Also includes: If a virtual machine scheduling record is found, the virtual machine scheduling identifier is reported to the upper-layer system.
6. The host monitoring event processing method according to claim 1, characterized in that, Also includes: Receive a login request and verify the login request; If the verification passes, a client mapping relationship is established based on the monitoring type, operating environment, and host identifier.
7. The host monitoring event processing method according to claim 6, characterized in that, Also includes: Establish a long-lived listening channel for host monitoring server; The long-connection listening channel of the host monitoring server is used to receive the host monitoring events and the login request.
8. A host monitoring event processing device, characterized in that, include: The identification unit is used to receive host monitoring events and identify the type of the host monitoring events; The query unit is used to query the corresponding resource usage records if the host monitoring event is a host shutdown event or a host restart event. The first update unit is used to update the shutdown time in the corresponding scheduling monitoring record and issue a host shutdown notification event if the resource usage record has not ended. The second update unit is used to update the startup time and the most recent running and reporting time in the scheduling monitoring record if the host monitoring event is a successful host startup event. The writing unit is used to obtain network parameters and hardware parameters and write the network parameters and hardware parameters into the scheduling monitoring record if the host monitoring event is a host boot success event; The detection unit is used to detect the processor's power-saving status based on the hardware parameters and to detect the network bandwidth based on the network parameters. The generation unit is used to generate corresponding abnormal events if the processor's power-saving state is not turned off or the network bandwidth is abnormal.
9. An electronic device, characterized in that, include: Memory, used to store computer programs; A processor, configured to implement the steps of the host monitoring event processing method as described in any one of claims 1 to 7 when executing the computer program.
10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a processor, implements the steps of the host monitoring event handling method as described in any one of claims 1 to 7.