Method, device and storage medium for querying service status

Abstract

The application provides a service state query method, device and equipment and a storage medium. The method comprises the following steps: if a downtime event on a target node in a data center operating system is monitored, obtaining a node identifier of the target node and a timestamp corresponding to the downtime event; obtaining historical service information of the target node according to the node identifier of the target node and the timestamp corresponding to the downtime event; determining target service information corresponding to a target service from the historical service information, wherein the target service information comprises a target service identifier and a user identifier; and querying a current running state of the target service according to the target service identifier and the user identifier. The application can directly determine the current running state of the service on the node when the downtime occurs, thereby improving the efficiency of querying the service state.

Description

Technical Field

[0001] This invention relates to the field of cloud computing technology, and in particular to a method, apparatus, device, and storage medium for querying business status. Background Technology

[0002] With the development of cloud computing technology, the number of services processed through DCOS (Data Center Operating System) is increasing. A DCOS consists of multiple nodes that handle various types of services. When a node in the DCOS fails for some reason (such as hardware failure), quickly determining the service status across multiple nodes is crucial for users.

[0003] However, existing technologies require technicians to retrieve the operational logs of the failed node before they can query the current operational status of the services within that node. Because this involves numerous manual steps and is time-consuming and labor-intensive, querying service status using this method is inefficient. Summary of the Invention

[0004] This invention provides a method, apparatus, device, and storage medium for querying business status, which can improve the efficiency of determining business status.

[0005] In a first aspect, the present invention provides a method for querying business status; comprising:

[0006] If a crash event is detected on a target node in the data center operating system, the node identifier of the target node and the timestamp corresponding to the crash event are obtained.

[0007] Based on the node identifier of the target node and the timestamp corresponding to the downtime event, obtain the historical business information of the target node;

[0008] Based on the historical business information, the target business information corresponding to the target business is determined, and the target business information includes the target business identifier and the user identifier;

[0009] Based on the target service identifier and the user identifier, query the current operating status of the target service.

[0010] In one possible design, obtaining the historical business information of the target node based on the node identifier of the target node and the timestamp corresponding to the downtime event includes: determining the call interface information corresponding to the target node based on the node identifier of the target node and the timestamp corresponding to the downtime event; and obtaining the historical business information of the target node through the call interface information.

[0011] In one possible design, the API call information includes resource address information; obtaining the historical business information of the target node through the API call information includes: establishing an information connection with a monitoring plugin deployed within the target node through the resource address information; and obtaining the historical business information of the target node from the monitoring information of the monitoring plugin through the information connection.

[0012] In one possible design, the historical service information includes service information for multiple services, the service information including the service's operating status, service identifier, and user identifier, the operating status including a running state and a non-running state; determining the target service information corresponding to the target service based on the historical service information includes: determining the target service whose operating status is in the running state based on the service information of the multiple services; and selecting the target service information corresponding to the target service from the historical service information.

[0013] In one possible design, querying the current operating status of the target service based on the target service identifier and the user identifier includes: determining query interface information based on the target service identifier and the user identifier; and querying the current operating status of the target service based on the query interface information.

[0014] In one possible design, the query interface information includes the allocation address information of the target service; querying the current operating status of the target service based on the query interface information includes: obtaining the node where the target service is currently located based on the allocation address information of the target service; and querying the current operating status of the target service from the node where the target service is currently located.

[0015] In one possible design, the data center operating system includes multiple nodes, and the method further includes: deploying a monitoring plugin in each node of the data center operating system; obtaining the running status, service identifier, and user identifier of multiple services on each node through the monitoring plugin; and for each node, associating and storing the service identifier, the user identifier, and the running status to obtain the historical service information of each node.

[0016] Secondly, the present invention provides a device for querying business status, the device comprising:

[0017] The monitoring module is used to obtain the node identifier of the target node and the timestamp corresponding to the downtime event if a downtime event is detected on the target node in the data center operating system.

[0018] The acquisition module is used to acquire the historical business information of the target node based on the node identifier of the target node and the timestamp corresponding to the downtime event;

[0019] The determination module is used to determine the target service information corresponding to the target service based on the historical service information, wherein the target service information includes a target service identifier and a user identifier;

[0020] The query module is used to query the current operating status of the target service based on the target service identifier and the user identifier.

[0021] Thirdly, the present invention provides a server, comprising: at least one processor and a memory;

[0022] The memory stores computer-executed instructions;

[0023] The at least one processor executes the computer execution instructions stored in the memory, causing the at least one processor to perform the business status query method as described in the first aspect and various possible designs of the first aspect.

[0024] Fourthly, the present invention provides a computer storage medium storing computer execution instructions, wherein when a processor executes the computer execution instructions, the method for querying business status as described in the first aspect and various possible designs of the first aspect is implemented.

[0025] Fifthly, the present invention provides a computer program product, including a computer program that, when executed by a processor, implements the business status query method described in the first aspect and various possible designs of the first aspect.

[0026] The present invention provides a method, apparatus, device, and storage medium for querying business status. If a crash event is detected on a target node in a data center operating system, the following steps are taken: First, the node identifier of the target node and the timestamp corresponding to the crash event are obtained. Then, based on the node identifier and the timestamp, historical business information of the target node is obtained. Based on the historical business information, target business information corresponding to the target business is determined, including a target business identifier and a user identifier. Finally, the current operating status of the target business is queried based on the target business identifier and the user identifier. Because when a crash event occurs, the historical business information on the node is first determined based on the node identifier and timestamp, then the target business identifier and user identifier corresponding to the target business are determined, and finally, the current operating status of the target business is queried using the target business identifier and user identifier, this application can directly determine the current operating status of the business on the node when a crash occurs, thereby improving the efficiency of querying business status. Attached Figure Description

[0027] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0028] Figure 1 This is a schematic diagram illustrating an application scenario of the business status query method provided in this embodiment of the invention;

[0029] Figure 2 Flowchart of the business status query method provided in this embodiment of the invention Figure 1 ;

[0030] Figure 3 Flowchart of the business status query method provided in this embodiment of the invention Figure 2 ;

[0031] Figure 4 Flowchart of the business status query method provided in this embodiment of the invention Figure 3 ;

[0032] Figure 5 A schematic diagram of the structure of the business status query device provided in an embodiment of the present invention;

[0033] Figure 6 This is a schematic diagram of the hardware structure of an electronic device provided in an embodiment of the present invention. Detailed Implementation

[0034] To make the objectives, technical solutions, and advantages of the embodiments of the present invention clearer, the technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0035] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, data stored, data displayed, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties. Furthermore, the collection, use and processing of the relevant data must comply with relevant laws, regulations and standards, and corresponding operation entry points are provided for users to choose to authorize or refuse.

[0036] With the development of cloud computing technology, the number of services processed through DCOS (Data Center Operating System) is increasing. A DCOS consists of multiple nodes that handle various types of services. When a node in the DCOS fails for some reason (such as hardware failure), quickly determining the service status across multiple nodes is crucial for users.

[0037] In existing technologies, when a node in a data center operating system fails, technicians need to first retrieve the operational logs of the failed node, then determine the services running within that node based on the logs, and finally query the current operational status of those services. However, the inventors have discovered that existing technologies have at least the following technical problems: because they require technicians to retrieve the operational logs of the failed node before querying the current operational status of the services within that node, the manual steps are numerous, time-consuming, and labor-intensive. Therefore, the efficiency of querying service status using the above method is low.

[0038] To address the aforementioned technical problems, this invention proposes the following technical concept: When a downtime event occurs, firstly, based on the node identifier and timestamp, the historical service information on the node is determined. Then, the target service identifier and user identifier corresponding to the target service are determined. Finally, using the target service identifier and user identifier, the current operating status of the target service is queried. This application can directly determine the current operating status of services on a node when a downtime occurs without the need for technical personnel to operate, thereby improving the efficiency of querying service status. Detailed embodiments are described below.

[0039] Figure 1 This is a schematic diagram illustrating an application scenario of the business status query method provided in this embodiment of the invention. For example... Figure 1 As shown, the display device 101 receives a service status acquisition request input by the user. The display device 101 transmits the acquisition request to the server 102 through the wireless network, so that the server 102 determines the current running status of the service on the node when the downtime occurs based on the acquisition request, and feeds back the current running status of the service on the node to the display device 101 for display.

[0040] Figure 2 Flowchart of the business status query method provided in this embodiment of the invention Figure 1 The execution entity in this embodiment can be Figure 1 The server in the illustrated embodiment is not specifically limited in this embodiment. Figure 2 As shown, the method includes:

[0041] S201: If a crash event is detected on the target node in the data center operating system, obtain the node identifier of the target node and the timestamp corresponding to the crash event.

[0042] In this embodiment, multiple nodes were detected within the data center operating system, capable of handling different services. Generally, a node can handle any type of service. Within the data center operating system, a node can also be referred to as a host or server.

[0043] The node identifier is used to distinguish different nodes. This node identifier can include letters, numbers, text, characters, etc. For example, the node identifier is: Node A.

[0044] The timestamp corresponding to the downtime event is the time when the downtime event occurred. When a downtime event occurs on a target node, that target node may include multiple services; these services include running services and non-running services.

[0045] Optionally, the monitoring component monitors the data center operating system. If a crash event is detected on a target node within the data center operating system, the monitoring component obtains the node identifier of the target node and the timestamp corresponding to the crash event. For example, this monitoring component could be a Prometheus component.

[0046] S202: Obtain the historical business information of the target node based on the node identifier of the target node and the timestamp corresponding to the downtime event.

[0047] In this embodiment, historical service information includes service information for multiple services. Here, "multiple services" refers to the multiple services on the target node at the time of the target node's downtime.

[0048] The service information is used to represent the service initiated by the user and its operational status. Optionally, the service information includes the operational status of the service, the service identifier, and the user identifier. The operational status includes "running" and "not running".

[0049] Optionally, historical business information includes a list of business information. This list contains business information for multiple businesses. The business information for these businesses can be sorted according to the processing order of the businesses.

[0050] S203: Based on historical business information, determine the target business information corresponding to the target business. The target business information includes the target business identifier and the user identifier.

[0051] In this embodiment, the target service identifier is used to distinguish different services. The target service identifier may include letters, numbers, words, characters, etc. For example, the target service identifier is: Service A.

[0052] User identifiers are used to distinguish different users. User identifiers can include letters, numbers, words, characters, etc. For example, a user identifier could be: User A.

[0053] In this embodiment, the target service can be any service on the target node when a crash event occurs, or it can be a service that is running on the target node when a crash event occurs.

[0054] Optionally, the target service is the service that was running on the target node at the time of the outage event. Historical service information includes service information for multiple services. Service information is used to represent user-initiated services and their running status. Optionally, service information includes the service's running status, service identifier, and user identifier. Running status includes running and not running states.

[0055] Accordingly, this step is as follows: Based on the business information of multiple services, determine the target service that is currently in operation; select the target service information corresponding to the target service from the historical business information.

[0056] S204: Query the current operating status of the target service based on the target service identifier and the user identifier.

[0057] In this embodiment, one service identifier and one user identifier correspond to one service. Optionally, this step is as follows: based on the target service identifier and the user identifier, determine the node where the target service is currently located, and query the current running status of the target service from the node's running information.

[0058] If the running status is "running", it means that the target service has been restored; if the running status is "not running", it means that the target service has not yet been restored.

[0059] The service status query method provided in this embodiment first determines the historical service information on the node based on the node identifier and timestamp when a downtime event occurs. Then, it determines the target service identifier and user identifier corresponding to the target service. Finally, it queries the current operating status of the target service using the target service identifier and user identifier. Therefore, this application can directly determine the current operating status of the service on the node when a downtime occurs, thereby improving the efficiency of querying service status.

[0060] Figure 3 Flowchart of the business status query method provided in this embodiment of the invention Figure 2 In this embodiment of the invention, in Figure 2Based on the provided embodiments, the specific implementation method for obtaining the historical business information of the target node in S202 according to the node identifier of the target node and the timestamp corresponding to the downtime event is described in detail. For example... Figure 3 As shown, the method includes:

[0061] S301. Determine the API call information corresponding to the target node based on the node identifier of the target node and the timestamp corresponding to the crash event.

[0062] The API call information is used to connect to the monitoring plugin within the node and obtain the node's business information. Optionally, the API call information includes a node identifier and a timestamp corresponding to the downtime event, used to obtain the target node corresponding to the node identifier and the business information corresponding to the timestamp. Optionally, the API call information is the promethues interface, which connects to the monitoring plugin within the node.

[0063] For example, the API call information can be resource address information. For instance, the resource address information could be: http: / / XXX:29092 / api / v1 / query?query=mesos_task_status{host_ip=XXX}&time=1670428800. Here, host_ip=XXX represents the node identifier, and time=1670428800 represents the timestamp corresponding to the downtime event.

[0064] S302. Obtain historical business information of the target node by calling the interface information.

[0065] Optionally, the API call information includes resource address information. Accordingly, this step is as follows: establish an information connection with the monitoring plugin deployed in the target node through the resource address information; and obtain the historical business information of the target node from the monitoring information of the monitoring plugin through the information connection.

[0066] The monitoring plugin can monitor the services running on the node and obtain service information. Optionally, the monitoring plugin is the mesos-exporter monitoring plugin. This mesos-exporter monitoring plugin can monitor the Mesos services running on the node.

[0067] In this embodiment, the data center operating system includes multiple nodes. The steps for monitoring the operation of multiple nodes and obtaining historical business information are as follows: deploy a monitoring plugin in each node of the data center operating system; obtain the running status, business identifier, and user identifier of multiple services on each node through the monitoring plugin; and for each node, associate and store the business identifier, user identifier, and running status to obtain the historical business information of each node.

[0068] Figure 4 Flowchart of the business status query method provided in this embodiment of the invention Figure 3 In this embodiment of the invention, in Figure 2 Based on the provided embodiments, the specific implementation method of querying the current operating status of the target service according to the target service identifier and the user identifier in S204 is described in detail.

[0069] like Figure 4 As shown, the method includes:

[0070] S401. Determine the query interface information based on the target business identifier and user identifier.

[0071] The query interface information is used to determine the current node of any given service. Optionally, the interface information includes a service identifier and a user identifier, used to obtain the current node of the target service corresponding to that service identifier and user identifier. Optionally, the query interface information is the Marathon (marathon, scheduler) interface, which is used to determine the current node of the service.

[0072] The API call information can be the allocated address information. For example, the allocated address information is: http: / / xx.xx.xx.xx / service / role / v2 / apps / $task_name. Here, task_name represents the business identifier, and role represents the user identifier.

[0073] S402. Based on the query interface information, query the current operating status of the target business.

[0074] Optionally, the query interface information includes the allocation address information of the target service; accordingly, this step is: based on the allocation address information of the target service, obtain the node where the target service is currently located; query the current running status of the target service from the node where the target service is currently located.

[0075] For example, if the target service is currently in an unrunning state, it means that the service has not yet been restored.

[0076] Figure 5 This is a schematic diagram of the structure of a business status query device provided in an embodiment of the present invention. Figure 5 As shown, the device for querying the business status includes: a monitoring module 501, an acquisition module 502, a determination module 503, and a query module 504.

[0077] The monitoring module 501 is used to obtain the node identifier of the target node and the timestamp corresponding to the downtime event if a downtime event is detected on the target node in the data center operating system.

[0078] The acquisition module 502 is used to acquire the historical business information of the target node based on the node identifier of the target node and the timestamp corresponding to the downtime event;

[0079] The determination module 503 is used to determine the target business information corresponding to the target business based on historical business information. The target business information includes the target business identifier and the user identifier.

[0080] The query module 504 is used to query the current running status of the target service based on the target service identifier and the user identifier.

[0081] In one possible design, the acquisition module 502 obtains the historical business information of the target node based on the node identifier of the target node and the timestamp corresponding to the crash event. Specifically, this includes: determining the call interface information corresponding to the target node based on the node identifier of the target node and the timestamp corresponding to the crash event; and obtaining the historical business information of the target node through the call interface information.

[0082] In one possible design, the interface call information includes resource address information; the acquisition module 502 obtains the historical business information of the target node by calling the interface information, specifically including: establishing an information connection with the monitoring plugin deployed in the target node through the resource address information; and obtaining the historical business information of the target node from the monitoring information of the monitoring plugin through the information connection.

[0083] In one possible design, historical business information includes business information for multiple services. The business information includes the service's operating status, service identifier, and user identifier. The operating status includes "running" and "not running". The determination module 503 determines the target business information corresponding to the target service based on the historical business information. Specifically, this includes: determining the target service whose operating status is "running" based on the business information of multiple services; and selecting the target business information corresponding to the target service from the historical business information.

[0084] In one possible design, the query module 504 queries the current operating status of the target service based on the target service identifier and the user identifier, specifically including: determining the query interface information based on the target service identifier and the user identifier; and querying the current operating status of the target service based on the query interface information.

[0085] In one possible design, the query interface information includes the allocation address information of the target service; the query module 504 queries the current running status of the target service based on the query interface information, specifically including: obtaining the node where the target service is currently located based on the allocation address information of the target service; and querying the current running status of the target service from the node where the target service is currently located.

[0086] In one possible design, the data center operating system includes multiple nodes, and the device also includes: a monitoring module; the monitoring module is used to deploy monitoring plugins in each node of the data center operating system; to obtain the running status, service identifier, and user identifier of multiple services on each node through the monitoring plugins; and to associate and store the service identifier, user identifier, and running status of each node to obtain the historical service information of each node.

[0087] The apparatus provided in this embodiment can be used to execute the technical solutions of the above method embodiments. Its implementation principle and technical effects are similar, and will not be described again here.

[0088] Figure 6 This is a schematic diagram of the hardware structure of an electronic device provided in an embodiment of the present invention. For example... Figure 6 As shown, the electronic device of this embodiment includes: a processor 601 and a memory 602; wherein

[0089] Memory 602 is used to store instructions executed by the computer;

[0090] The processor 601 is used to execute computer execution instructions stored in the memory to implement the various steps performed by the electronic device in the above embodiments. For details, please refer to the relevant descriptions in the foregoing method embodiments.

[0091] Alternatively, the memory 602 can be either standalone or integrated with the processor 601.

[0092] When the memory 602 is set up independently, the electronic device also includes a bus 603 for connecting the memory 602 and the processor 601.

[0093] This invention also provides a computer storage medium storing computer execution instructions. When the processor executes the computer execution instructions, it implements the business status query method of the above-described method embodiments.

[0094] This invention also provides a computer program product, including a computer program, which, when executed by a processor, implements the business status query method of the above-described method embodiments.

[0095] In the several embodiments provided by this invention, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are merely illustrative; for instance, the division of modules is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple modules may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be indirect coupling or communication connection through some interfaces, devices, or modules, and may be electrical, mechanical, or other forms.

[0096] The modules described as separate components may or may not be physically separate. The components shown as modules may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to implement the solution of this embodiment according to actual needs.

[0097] Furthermore, the functional modules in the various embodiments of the present invention can be integrated into one processing unit, or each module can exist physically separately, or two or more modules can be integrated into one unit. The unit composed of the above modules can be implemented in hardware or in the form of hardware plus software functional units.

[0098] The integrated modules described above, implemented as software functional modules, can be stored in a computer-readable storage medium. These software functional modules, stored in a storage medium, include several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) or processor to execute partial steps of the methods in the various embodiments of this application.

[0099] It should be understood that the aforementioned processor can be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), etc. A general-purpose processor can be a microprocessor or any conventional processor. The steps of the method disclosed in this invention can be directly manifested as being executed by a hardware processor, or executed by a combination of hardware and software modules within the processor.

[0100] The memory may include high-speed RAM, and may also include non-volatile storage (NVM), such as at least one disk storage device, and may also be a USB flash drive, external hard drive, read-only memory, disk or optical disc, etc.

[0101] The bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. Buses can be categorized as address buses, data buses, control buses, etc. For ease of illustration, the buses shown in the accompanying drawings are not limited to a single bus or a single type of bus.

[0102] The aforementioned storage medium can be implemented from any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk. The storage medium can be any available medium accessible to general-purpose or special-purpose computers.

[0103] An exemplary storage medium is coupled to a processor, enabling the processor to read information from and write information to the storage medium. Alternatively, the storage medium can be an integral part of the processor. Both the processor and the storage medium can reside in an Application Specific Integrated Circuit (ASIC). Alternatively, the processor and storage medium can exist as discrete components in an electronic device or host device.

[0104] Those skilled in the art will understand that all or part of the steps of the above-described method embodiments can be implemented by hardware related to program instructions. The aforementioned program can be stored in a computer-readable storage medium. When executed, the program performs the steps of the above-described method embodiments; and the aforementioned storage medium includes various media capable of storing program code, such as ROM, RAM, magnetic disks, or optical disks.

[0105] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, and not to limit them; although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some or all of the technical features; and these modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of the present invention.

Claims

1. A method for querying business status, characterized in that, include: If a crash event is detected on a target node in the data center operating system, the node identifier of the target node and the timestamp corresponding to the crash event are obtained. Based on the node identifier of the target node and the timestamp corresponding to the downtime event, obtain the historical business information of the target node; Based on the historical business information, the target business information corresponding to the target business is determined, and the target business information includes the target business identifier and the user identifier; Based on the target service identifier and the user identifier, query the current operating status of the target service; Based on the node identifier of the target node and the timestamp corresponding to the downtime event, obtain the historical business information of the target node, including: Based on the node identifier of the target node and the timestamp corresponding to the crash event, the call interface information corresponding to the target node is determined; the call interface information includes resource address information; The resource address information is used to establish an information connection with the monitoring plugin deployed in the target node; Through the information connection, the historical business information of the target node can be obtained from the monitoring information of the monitoring plugin.

2. The method according to claim 1, characterized in that, The historical service information includes service information for multiple services. The service information includes the service's operating status, service identifier, and user identifier. The operating status includes "currently running" and "not running". The step of determining the target service information corresponding to the target service based on the historical service information includes: Based on the business information of the multiple services, determine the target service that is currently running. Select the target business information corresponding to the target business from the historical business information.

3. The method according to claim 1, characterized in that, Based on the target service identifier and the user identifier, query the current operating status of the target service, including: The query interface information is determined based on the target service identifier and the user identifier; Based on the query interface information, query the current operating status of the target service.

4. The method according to claim 3, characterized in that, The query interface information includes the allocation address information of the target service; The step of querying the current operating status of the target service based on the query interface information includes: Based on the allocation address information of the target service, obtain the node where the target service is currently located; Query the current running status of the target service from the node where the target service is currently located.

5. The method according to any one of claims 1-4, characterized in that, The data center operating system includes multiple nodes, and the method further includes: Deploy monitoring plugins within each node of the data center operating system; The monitoring plugin obtains the running status, service identifier, and user identifier of multiple services on each node. For each node, the service identifier, the user identifier, and the running status are associated and stored to obtain the historical service information of each node.

6. A device for querying business status, characterized in that, The device includes: The monitoring module is used to obtain the node identifier of the target node and the timestamp corresponding to the downtime event if a downtime event is detected on the target node in the data center operating system. The acquisition module is used to acquire the historical business information of the target node based on the node identifier of the target node and the timestamp corresponding to the downtime event; The determination module is used to determine the target service information corresponding to the target service based on the historical service information, wherein the target service information includes a target service identifier and a user identifier; The query module is used to query the current operating status of the target service based on the target service identifier and the user identifier; The acquisition module is used to determine the call interface information corresponding to the target node based on the node identifier of the target node and the timestamp corresponding to the downtime event; the call interface information includes resource address information; through the resource address information, an information connection is established with the monitoring plugin deployed in the target node; through the information connection, the historical business information of the target node is obtained from the monitoring information of the monitoring plugin.

7. An electronic device, characterized in that, include: At least one processor and memory; The memory stores computer-executed instructions; The at least one processor executes the computer execution instructions stored in the memory, causing the at least one processor to perform the business status query method as described in any one of claims 1 to 5.

8. A computer storage medium, characterized in that, The computer storage medium stores computer execution instructions. When the processor executes the computer execution instructions, it implements the business status query method as described in any one of claims 1 to 5.

Images