Methods, devices, equipment and storage media for monitoring operational status

Abstract

This application provides a method, apparatus, device, and storage medium for monitoring operational status, relating to the field of computer technology. The method includes: obtaining a first task through an interface automation module, the first task indicating monitoring of a technical case; obtaining a server address and case information based on the parsing and processing of the first task by the interface automation module; sending the case information to the corresponding server based on the server address, so that the server executes the technical case according to the case information; obtaining the execution result returned by the server; storing the execution result in a database in the data layer; and obtaining the operational status of the operating system based on the execution result in the database. This method solves the problem that existing monitoring and testing techniques for multi-environment systems can only identify whether the system is normal by checking interfaces, and cannot accurately monitor the system's operational status.

Description

Technical Field

[0001] This application relates to computer technology, and more particularly to a method, apparatus, device, and storage medium for monitoring operational status. Background Technology

[0002] Monitoring the system's operating status is an essential measure to ensure its normal operation and prevent malfunctions.

[0003] In multi-environment system architectures based on Spring Boot, Spring Boot Actuator is typically used to monitor and manage system operation. The automatic recovery and scaling of applications on container cloud platforms rely on system monitoring capabilities, making it crucial to have real-time access to system status. Enabling Spring Boot Actuator monitors operational information such as disk space, Redis, and databases. During development and testing, the TestUI framework is commonly used. This framework provides a simple UI interface, allowing product, testing, and development teams to test their respective focus points, reducing the complexity of testing.

[0004] Existing monitoring and testing techniques for multi-environment systems can only identify whether a system is functioning normally by checking its interfaces, and cannot accurately monitor the system's operating status. Summary of the Invention

[0005] This application provides a method, apparatus, device, and storage medium for monitoring operating status, in order to solve the problem that existing monitoring and testing techniques for multi-environment systems can only identify whether the system is normal by checking the interface, and cannot accurately monitor the operating status of the system.

[0006] On the one hand, this application provides a method for monitoring operational status, including:

[0007] The first task is obtained through the interface automation module, and the first task is used to instruct the monitoring of technical cases;

[0008] Based on the parsing and processing of the first task by the interface automation module, the server address and case information are obtained. Based on the server address, the case information is sent to the corresponding server so that the server executes the technical case according to the case information.

[0009] Obtain the execution result returned by the server, store the execution result in the database in the data layer, and obtain the running status of the operating system based on the execution result in the database.

[0010] Optionally, obtaining the server address and case information based on the parsing and processing of the first task by the interface automation module includes:

[0011] The interface automation module parses the first task to obtain transaction code information and case information;

[0012] The server address is obtained from the service directory connected to the interface automation module based on the transaction code information. The service directory stores the mapping relationship between the transaction code information and the server address.

[0013] After the encryption switch of the interface automation module is turned on, the encryption key is obtained from the key management center connected to the interface automation module to encrypt the case information, thus obtaining the encrypted case information.

[0014] Optionally, the business service layer further includes a work platform interaction module and a work platform, and the method further includes:

[0015] The second task is obtained through the operation platform interaction module. The second task is used to instruct the monitoring of the technical baseline. The second task includes baseline information.

[0016] The second task is sent to the job platform, so that the job platform obtains the execution script based on the baseline information and sends the execution script to the client, so that the client executes the execution script and obtains the execution result.

[0017] The system obtains the execution result returned by the operation platform, stores the execution result in the database in the data layer, and obtains the running status of the operation system based on the execution result in the database.

[0018] Optionally, after sending the second task to the work platform, the method further includes:

[0019] A query thread is started, which accesses the job platform at a preset period to request the job platform to return the execution result;

[0020] The query thread is terminated after the callback from the job platform.

[0021] Optionally, obtaining the operating status of the operating system based on the execution results in the database includes:

[0022] Excluding times when there is no data, the execution results of the same type are aggregated in chronological order to obtain a pipeline time-space graph, which records the execution results of the most recent N times;

[0023] Based on the results of the most recent N executions, the operating status of the operating system is obtained; where N is a natural number greater than or equal to 3.

[0024] Optionally, obtaining the operating status of the operating system based on the results of the most recent N executions includes:

[0025] If the most recent execution result is execution failure, then the running status of the corresponding execution item is determined to be execution failure, and the execution item is a technical case or technical baseline;

[0026] If the most recent execution result was successful, and there was at least one execution failure, then the running status of the corresponding execution item is determined to be "running exception has been recovered";

[0027] If all N executions result in success, then the running status of the corresponding execution item is determined to be successful.

[0028] Optionally, after storing the execution result in the database in the data layer, the method further includes:

[0029] The execution results stored in the database are processed using Elastic Search's index lifecycle strategy.

[0030] On the other hand, this application provides a device for monitoring operating status, comprising:

[0031] The acquisition module is used to acquire a first task through the interface automation module, wherein the first task is used to instruct the monitoring of technical cases;

[0032] The processing module is used to obtain the server address and case information according to the parsing and processing of the first task by the interface automation module, and send the case information to the corresponding server according to the server address, so that the server executes the technical case according to the case information;

[0033] The processing module is also used to obtain the execution result returned by the server, store the execution result in the database in the data layer, and obtain the running status of the operating system based on the execution result in the database.

[0034] Optionally, the processing module is specifically used for:

[0035] The interface automation module parses the first task to obtain transaction code information and case information;

[0036] The server address is obtained from the service directory connected to the interface automation module based on the transaction code information. The service directory stores the mapping relationship between the transaction code information and the server address.

[0037] After the encryption switch of the interface automation module is turned on, the encryption key is obtained from the key management center connected to the interface automation module to encrypt the case information, thus obtaining the encrypted case information.

[0038] Optionally, the acquisition module is specifically used for:

[0039] The second task is obtained through the operation platform interaction module. The second task is used to instruct the monitoring of the technical baseline. The second task includes baseline information.

[0040] The second task is sent to the job platform, so that the job platform obtains the execution script based on the baseline information and sends the execution script to the client, so that the client executes the execution script and obtains the execution result.

[0041] The processing module is also used to obtain the execution result returned by the operation platform, store the execution result in the database in the data layer, and obtain the running status of the operation system based on the execution result in the database.

[0042] Optionally, the processing module is specifically used for:

[0043] A query thread is started, which accesses the job platform at a preset period to request the job platform to return the execution result;

[0044] The query thread is terminated after the callback from the job platform.

[0045] Optionally, the acquisition module is specifically used for:

[0046] Excluding times when there is no data, the execution results of the same type are aggregated in chronological order to obtain a pipeline time-space graph, which records the execution results of the most recent N times;

[0047] Based on the results of the most recent N executions, the operating status of the operating system is obtained; where N is a natural number greater than or equal to 3.

[0048] Optionally, the processing module is specifically used for:

[0049] If the most recent execution result is execution failure, then the running status of the corresponding execution item is determined to be execution failure, and the execution item is a technical case or technical baseline;

[0050] If the most recent execution result was successful, and there was at least one execution failure, then the running status of the corresponding execution item is determined to be "running exception has been recovered";

[0051] If all N executions result in success, then the running status of the corresponding execution item is determined to be successful.

[0052] Optionally, the processing module is specifically used for:

[0053] The execution results stored in the database are processed using Elastic Search's index lifecycle strategy.

[0054] A third aspect of this application provides an electronic device comprising:

[0055] Processor and memory;

[0056] The memory stores instructions that the computer executes;

[0057] The processor executes computer execution instructions stored in memory, causing the electronic device to perform any of the methods in the first aspect.

[0058] A fourth aspect of this application provides a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, are used to determine a driver for implementing a hardware peripheral as described in any of the first aspects.

[0059] A fifth aspect of this application provides a computer program product including a computer program that, when executed by a processor, implements the method as described in any of the first aspects.

[0060] This embodiment provides a method, apparatus, device, and storage medium for monitoring system operation status. The method obtains a first task through an interface automation module; based on the parsing and processing of the first task by the interface automation module, it obtains the server address and case information; according to the server address, it sends the case information to the corresponding server, enabling the server to execute a technical case based on the case information; it obtains the execution result returned by the server, stores the execution result in a database in the data layer, and obtains the operating status of the operating system based on the execution result in the database. This method judges the system's operating status by the execution result of the technical case executed by the server, promptly detects system faults, and solves the problem of using platform-provided software to identify whether the system is normal only through the interface, without being able to confirm the internal state of the system, thus providing a more comprehensive understanding of the system's operating status. Attached Figure Description

[0061] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

[0062] Figure 1 A diagram illustrating a specific application scenario for the operational status monitoring method provided in this application;

[0063] Figure 2 The method flow for monitoring the operating status provided in the embodiments of this application Figure 1 ;

[0064] Figure 3 The method flow for monitoring the operating status provided in the embodiments of this application Figure 2 ;

[0065] Figure 4 The method flow for monitoring the operating status provided in the embodiments of this application Figure 3 ;

[0066] Figure 5 The method flow for monitoring the operating status provided in the embodiments of this application Figure 4 ;

[0067] Figure 6 A schematic diagram of the structure of a monitoring device for operating status provided in an embodiment of this application;

[0068] Figure 7 This is a hardware structure diagram of the monitoring device for operating status provided in an embodiment of this application.

[0069] The accompanying drawings illustrate specific embodiments of this application, which will be described in more detail below. These drawings and descriptions are not intended to limit the scope of the concept in any way, but rather to illustrate the concept of this application to those skilled in the art through reference to particular embodiments. Detailed Implementation

[0070] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims.

[0071] Figure 1 A diagram illustrating a specific application scenario of the operational status monitoring method provided in this application. For example... Figure 1As shown, the overall architecture of the job system comprises two layers: a business service layer and a data layer. The business service layer mainly includes three modules: the job platform interaction module, the job platform itself, and the interface automation module, along with multiple server-side components. This layer also contains several microservice components, such as Eureka, a configuration center, and the P4 service directory. The data layer is divided into two parts: a relational database and a non-relational database. The relational database primarily stores basic data and some business result data; the non-relational database uses Elastic Search document database, mainly used for the aggregation and analysis of system business data.

[0072] This application provides a method for monitoring the operating status of the aforementioned operating system. By using an interface automation module to parse and forward tasks containing technical cases, the corresponding server executes the technical cases. The execution results of the technical cases are used to determine the operating status of the system, promptly identify the location of system faults, and solve the problem of using the platform's built-in software to identify whether the system is normal only through the interface, without being able to confirm the internal status of the system. This provides a more comprehensive understanding of the system's operating status.

[0073] The technical solution of this application and how the technical solution of this application solves the above-mentioned technical problems are described in detail below with specific embodiments. These specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments. The embodiments of this application will now be described with reference to the accompanying drawings.

[0074] Figure 2 The method flow for monitoring the operating status provided in the embodiments of this application Figure 1 .like Figure 2 As shown, the method in this embodiment is applied to the above-mentioned Figure 1 The operating system shown includes a business service layer and a data layer. The business service layer includes an interface automation module and multiple server-side components, including:

[0075] S201. Obtain the first task through the interface automation module. The first task is used to instruct the monitoring of technical cases.

[0076] In this embodiment, the job system adopts a microservice architecture based on Spring Boot. The job system includes a business service layer and a data layer. The business service layer mainly includes functional modules responsible for runtime status monitoring, server-side execution of services, and other microservice components responsible for system auxiliary business. The data layer is mainly responsible for data storage and analysis. To test the runtime status of the server-side in the job system using technical examples, it is necessary to obtain tasks containing technical examples from external sources, i.e., the first task. The job system interacts with external sources through an interface automation module.

[0077] In this embodiment, the interface automation module obtains a first task containing case information from the outside to monitor the server's running status in the operation system. The first task is used to instruct the monitoring of technical cases. The technical cases indicated by the first task can be one or more. A technical case is the entire process of the server performing a certain function.

[0078] S202. Based on the parsing and processing of the first task by the interface automation module, obtain the server address and case information, and send the case information to the corresponding server according to the server address so that the server can execute the technical case according to the case information.

[0079] In this embodiment, the interface automation module parses the first task to obtain the case information and the address of the server executing the technical case. The technical case can then be sent to the corresponding server. This case information includes details about the technical case, such as the case identifier, case data, and server environment information. Upon receiving the case information, the server executes the technical case accordingly.

[0080] The operating system is deployed on a cloud platform, specifically using container technology. Container technology is a new software delivery method that packages applications and their runtime environments into a standard image format. This ensures the uniformity of the application and its runtime environment, and allows it to run as a container on a Docker-enabled environment, regardless of the host machine's environment. Therefore, the multiple servers on the operating system have different runtime environments. When executing technical test cases, the interface automation module first parses the first task to check if it contains the corresponding environment information for the server. If the corresponding environment information exists, the test case information is forwarded to the corresponding server.

[0081] Technical cases are pre-recorded. The server's execution of a technical case can result in success, failure, or an exception. For example, for a server responsible for file management, one technical case might contain all the operations instructing the server to transfer a specified file to another server. After receiving the case information, the server automatically executes the operation to transfer the specified file to the other server. After the operation is complete, the server returns the execution result to the job system, indicating whether the file transfer was successful or if the file is being used by another application and requires a retry. Therefore, the execution of a single technical case sometimes cannot fully reflect the server's operational status. Those skilled in the art will understand that for most servers, testing multiple technical cases is necessary. When the first task includes multiple technical cases, the job system's scheduled task module can handle the batch processing of the technical cases.

[0082] S203. Obtain the execution result returned by the server, store the execution result in the database in the data layer, and obtain the running status of the job system based on the execution result in the database.

[0083] In this embodiment, the purpose of the operating system obtaining the execution results returned by the server is to obtain the execution status of the technical cases executed by the server and to determine the running status of the server based on the execution results. Since server status determination typically requires the execution of multiple technical cases, and also for the overall analysis of the operating system's status, the operating system first stores the execution results in the database in the data layer, and then analyzes and processes the execution results in the database during subsequent operations. Simultaneously, after obtaining the execution results returned by the server, if the execution result is a failure exception, relevant technical personnel can be notified via SMS or email, ensuring that the server-side fault is immediately known and accelerating the troubleshooting process.

[0084] Elastic Search is a distributed, highly scalable, and real-time search and data analytics engine. It easily enables the search, analysis, and exploration of big data. Leveraging Elastic Search's horizontal scalability makes data more valuable in production environments. The implementation of Elastic Search mainly involves the following steps: First, users submit data to the Elastic Search database. Then, the tokenization controller segments the corresponding sentences into tokens, storing the weights and segmentation results. When a user searches for data, the results are ranked and scored according to their weights, and then the results are presented to the user.

[0085] In this embodiment, the data layer of the operational system can use Elastic Search document database as a non-relational database. Elastic Search's aggregation analysis module is used to aggregate and analyze the execution results of technical cases. During routine inspections or troubleshooting by relevant technical personnel, in addition to information related to failed technical cases, they can also query previous case lists and case execution logs, accelerating fault location.

[0086] In this embodiment, the scheduled task module in the job system, in addition to batch processing, is also responsible for updating the execution status of technical cases before storing the execution results in the database in the data layer. This ensures that the data entered into the Elastic Search document database is valuable and worthy of aggregation and analysis by the Elastic Search aggregation and analysis module. Specifically, when some technical cases cannot be executed by the server due to non-server-side reasons, such as the case information not containing the corresponding server-side environment information, the scheduled task module will modify the execution record to prevent the execution information of this technical case from entering the database and affecting the Elastic Search aggregation and analysis. When the statistical score data obtained by the Elastic Search aggregation and analysis module needs to be batch processed, it can also be processed by the scheduled task module before being written to the Elastic Search document database.

[0087] This embodiment provides a method for monitoring the operational status. The method obtains a first task through an interface automation module; based on the parsing and processing of the first task by the interface automation module, it obtains the server address and case information; according to the server address, it sends the case information to the corresponding server, enabling the server to execute the technical case based on the case information; it obtains the execution result returned by the server, stores the execution result in a database in the data layer, and obtains the operational status of the operating system based on the execution result in the database. This method judges the system's operational status by the execution result of the technical case executed by the server, promptly detects system faults, and solves the problem of using platform-provided software to identify whether the system is normal only through the interface, without being able to confirm the internal status of the system, thus providing a more comprehensive understanding of the system's operational status.

[0088] Figure 3 The method flow for monitoring the operating status provided in the embodiments of this application Figure 2 .like Figure 3 As shown, in this embodiment... Figure 2 In the illustrated embodiment, the process of obtaining the server address and case information based on the parsing and processing of the first task by the interface automation module is described in detail, including:

[0089] S301. The interface automation module parses the first task to obtain transaction code information and case information;

[0090] In this embodiment, the transaction code represents the encoding of the business type in the job system. Different business types require different servers to complete the task, therefore there is a mapping relationship between the transaction code and the server address. The interface automation module parses the first task to obtain case information and transaction code information.

[0091] S302. Obtain the server address from the service directory connected to the interface automation module based on the transaction code information. The service directory stores the mapping relationship between the transaction code information and the server address.

[0092] In this embodiment, the service directory is the P4V version control tool. P4V, short for Perforce version control tool, is based on a client-server architecture with a central server. Other clients connect to the server via a network. In this embodiment, the server stores the mapping relationship between transaction code information and server addresses. After the interface automation module obtains the transaction code information through parsing, it needs to retrieve the corresponding server address from the Perforce server based on the mapping relationship between the transaction code information and the server address in order to obtain the server address corresponding to the execution technology case.

[0093] S303. After the encryption switch of the interface automation module is turned on, the encryption key is obtained from the key management center connected to the interface automation module to encrypt the case information and obtain the encrypted case information.

[0094] In this embodiment, the interface automation module has an encryption switch. When the encryption switch is turned on, the interface automation module can encrypt the case information. Since the operating system in this embodiment is applied in the financial field, the purpose of encrypting the case information is to ensure the security of communication data and prevent the leakage of sensitive information.

[0095] The key management center is a crucial component of the public key infrastructure (PKI). It is responsible for providing key services to CAs (Certification Authorities), including key generation, storage, backup, update, recovery, and querying, to address the key management challenges arising from large-scale cryptographic applications in distributed enterprise environments. In this embodiment, when the encryption / decryption switch of the interface automation module is turned on, it retrieves the encryption key from the key management center and uses it to encrypt the case information, resulting in the encrypted case information.

[0096] This embodiment provides a method for monitoring operational status. The method uses an interface automation module to parse a first task, obtaining transaction code information and case information. Based on the transaction code information, it retrieves the server address from the service directory connected to the interface automation module. After the encryption switch of the interface automation module is turned on, it obtains an encryption key from the key management center connected to the interface automation module to encrypt the case information, resulting in encrypted case information. This method achieves both parsing and confidentiality of case information by using the interface automation module to obtain the server address and encrypting the case information.

[0097] Figure 4 The method flow for monitoring the operating status provided in the embodiments of this application Figure 3 .like Figure 4 As shown, in this embodiment... Figure 2 Based on the illustrated embodiments, combined with Figure 1 The business service layer also includes a work platform interaction module and a work platform, and the process of judging the system's operating status by executing a second task is explained in detail. This process includes:

[0098] S401. Obtain the second task through the operation platform interaction module. The second task is used to instruct the monitoring of the technical baseline. The second task includes baseline information.

[0099] In this embodiment, based on monitoring the server-side operation status of the job system through the execution of technical cases, the operation status of the job system is monitored according to the technical baseline. The technical baseline refers to the standard for normal server operation. The baseline information of the technical baseline consists of detection items for the technical baseline, including basic environment detection, SA security component detection, NFT component detection, middleware detection, database service detection, Luban batch processing detection, and online green light detection. Among them, the NFT component is responsible for file transfer, the middleware is the platform for deploying services, and the online green light refers to whether the detection system is registered. The job platform interaction module is responsible for interacting with the job platform. The second task can be pre-set and stored in the job system, retrieved by the job platform interaction module, and sent to the job platform.

[0100] S402, Send the second task to the work platform;

[0101] In this embodiment, the work platform interacts with the server. Therefore, the second task is first sent from the work platform interaction module to the work platform.

[0102] S403. Start the query thread. The query thread accesses the work platform at a preset period to request the work platform to return the execution result.

[0103] In this embodiment, in order to obtain the execution result of the second task in a timely manner, the job platform interaction module does not wait for the callback result of the job platform. Instead, it starts an active query thread through the thread pool, which can be configured with query interval and query count. The current query thread is bound to the second task and stored in Redis or other distributed cache.

[0104] S404. The work platform obtains the execution script based on the baseline information and sends the execution script to the client, so that the client executes the execution script and obtains the execution result;

[0105] In this embodiment, the detection items and execution scripts in the baseline information are related, and the baseline information also includes the server address of the execution detection item. The job platform obtains the corresponding execution script based on the baseline information and sends the execution script to the corresponding server based on the server address of the execution detection item. The server executes the execution script to obtain the execution result. Those skilled in the art will understand that after the job platform interaction module sends the second task to the job platform, the process of the job platform interaction module starting the active query thread and the job platform sending the execution script to the client based on the baseline information occurs simultaneously.

[0106] S405. Terminate the query thread after the work platform callback;

[0107] In this embodiment, the job platform interaction module terminates the active query thread after the job platform receives the callback result.

[0108] S406. Obtain the execution results returned by the job platform, store the execution results in the database in the data layer, and obtain the running status of the job system based on the execution results in the database.

[0109] In this embodiment, similar to the execution result in the technical case, after obtaining the execution result returned by the job platform, the job system stores the execution result in the Elastic Search document database in the data layer, and performs aggregate analysis of the execution result of the technical baseline detection item by using the aggregation analysis module of ElasticSearch.

[0110] This embodiment provides a method for monitoring the operational status. The method obtains a second task through a job platform interaction module; after sending the second task to the job platform, a query thread is started. The query thread accesses the job platform at preset intervals to request execution results; the job platform obtains and executes the execution script based on baseline information, obtaining the execution result; after a callback from the job platform, the query thread is terminated; the execution result returned by the job platform is obtained, stored in a database in the data layer, and the operational status of the job system is obtained based on the execution result in the database. This method monitors the system's technical baseline by executing the second task through the job platform, while simultaneously starting a thread to periodically query the task execution result, allowing the job platform to obtain the task execution result after task submission.

[0111] Figure 5 The method flow for monitoring the operating status provided in the embodiments of this application Figure 4 .like Figure 5 As shown, in this embodiment... Figure 2 Based on the illustrated embodiment, the process of obtaining the operating status of the operating system from the execution results in the database is described in detail. This process includes:

[0112] S501. Use Elastic Search's index lifecycle strategy to process the execution results stored in the database;

[0113] In this embodiment, Elastic Search's index lifecycle strategy divides data into four phases based on the current time: hot, warm, cold, and delete. Data in the hot phase is the most recent data. Data in the warm, cold, and delete phases is more recent than data in the hot phase, and this relationship increases sequentially. For example, hot phase data is data from within one day, warm phase data is data from within one month, cold phase data is data from within three months, and delete phase data is data from within six months. Different strategies are applied to different phases. Because data is backed up, it exists in segments within the backups. A data backup consists of multiple smaller segments, and data is backed up in these segments. In the warm phase, the replicas and segments are set to 1. This means that backups of smaller segments from previous warm phase data are deleted, and multiple smaller segments are combined into one larger segment for backup. In the cold phase, the data is set to be queried but not manipulated. In the delete phase, the data is the data that needs to be deleted.

[0114] S502. Exclude the time when there is no data, aggregate the execution results of the same type in chronological order to obtain the pipeline time-space graph, which records the execution results of the most recent N times;

[0115] In this embodiment, since the execution results of technical cases and technical baselines are scattered over time, in order to improve aggregation efficiency, it is necessary to exclude the time when there is no data, and then aggregate the execution results of the same type in chronological order to obtain the pipeline spatiotemporal graph. In the specific implementation process, the execution results of technical cases and technical baselines are first aggregated into the same category, and then aggregated according to the server category. The resulting pipeline spatiotemporal graph is the execution results of a single server that are N most recent times backward from the current time node.

[0116] S503. If the most recent execution result is execution failure, then the running status of the corresponding execution item is determined to be execution failure, and the execution item is a technical case or technical baseline.

[0117] In this embodiment, the operating status of the operating system is obtained based on the results of the most recent N executions; where N is a natural number greater than or equal to 3. Here, the most recent execution result is used as the primary benchmark to determine the operating status of the execution item. Those skilled in the art will understand that the operating status of the execution item can refer to multiple execution results. For example, if one of the most recent two execution results is an execution failure, then the operating status of the corresponding execution item is determined to be an execution failure.

[0118] S504. If the most recent execution result is successful, and there is at least one execution failure, then the running status of the corresponding execution item is determined to be "running exception has been recovered".

[0119] S505. If all N executions result in success, then the running status of the corresponding execution item is determined to be successful.

[0120] This embodiment provides a method for monitoring the operational status. This method processes execution results stored in the database using Elastic Search's index lifecycle strategy; it excludes periods without data and aggregates execution results of the same type in chronological order to obtain a pipeline spatiotemporal graph. The pipeline spatiotemporal graph records the N most recent execution results. If the most recent execution result is a failure, the corresponding execution item is determined to be in a failed operational status, and the execution item is identified as a technical case or technical baseline. If the most recent execution result is a success, and there are at least one failure, the corresponding execution item is determined to be in a recovered operational status. If all N execution results are successes, the corresponding execution item is determined to be in a successful operational status. This method eliminates the possibility of data accumulation by employing an index lifecycle strategy, improving disk space utilization; and by determining the system's operational status based on the N most recent execution results, the results are more scientific and reasonable.

[0121] Figure 6 This is a schematic diagram of a monitoring device for operational status provided in an embodiment of this application. The device in this embodiment can be in the form of software and / or hardware. For example... Figure 6 As shown in the embodiment of this application, a monitoring device 600 for operational status is provided and applied to an operating system. The operating system includes a business service layer and a data layer. The business service layer includes an interface automation module and multiple servers, including an acquisition module 601 and a processing module 602.

[0122] The acquisition module 601 is used to acquire the first task through the interface automation module. The first task is used to instruct the monitoring of the technical case.

[0123] The processing module 602 is used to obtain the server address and case information based on the parsing and processing of the first task by the interface automation module, and send the case information to the corresponding server based on the server address so that the server can execute the technical case according to the case information.

[0124] The processing module 602 is also used to obtain the execution result returned by the server, store the execution result in the database in the data layer, and obtain the running status of the job system based on the execution result in the database.

[0125] In one possible implementation, the processing module is specifically used for:

[0126] The interface automation module parses the first task to obtain transaction code information and case information;

[0127] The server address is obtained from the service directory connected to the interface automation module based on the transaction code information. The service directory stores the mapping relationship between the transaction code information and the server address.

[0128] After the encryption switch of the interface automation module is turned on, the encryption key is obtained from the key management center connected to the interface automation module to encrypt the case information and obtain the encrypted case information.

[0129] In one possible implementation, the acquisition module is further used to: acquire a second task through the operation platform interaction module, the second task being used to instruct the monitoring of the technical baseline, the second task including baseline information;

[0130] The second task is sent to the job platform so that the job platform can obtain the execution script based on the baseline information and send the execution script to the client so that the client can execute the execution script and obtain the execution result.

[0131] The processing module is also used to obtain the execution results returned by the job platform, store the execution results in the database in the data layer, and obtain the running status of the job system based on the execution results in the database.

[0132] In one possible implementation, the processing module is specifically used for:

[0133] Start a query thread. The query thread will access the job platform at a preset period to request the job platform to return the execution results.

[0134] The query thread is terminated after the job platform callback.

[0135] In one possible implementation, the acquisition module is specifically used for:

[0136] Excluding times when there is no data, aggregate the execution results of the same type in chronological order to obtain the pipeline time-space graph, which records the execution results of the most recent N times;

[0137] Based on the results of the most recent N executions, obtain the operating status of the operating system; where N is a natural number greater than or equal to 3.

[0138] In one possible implementation, the processing module is specifically used for:

[0139] If the most recent execution result is execution failure, then the running status of the corresponding execution item is determined to be execution failure, and the execution item is a technical case or technical baseline;

[0140] If the most recent execution result was successful, and there was at least one execution failure, then the running status of the corresponding execution item is determined to be "running exception has been recovered";

[0141] If all N executions result in success, then the running status of the corresponding execution item is determined to be successful.

[0142] In one possible implementation, the processing module is specifically used for:

[0143] The execution results stored in the database are processed using Elastic Search's index lifecycle strategy.

[0144] The monitoring device for operating status provided in this embodiment can be used to execute the above method embodiment. Its implementation principle and technical effect are similar, and will not be described again here.

[0145] Figure 7 This is a hardware structure diagram of the monitoring device for operational status provided in an embodiment of this application. Figure 7 As shown, the monitoring device 700 for this operational status includes:

[0146] Processor 701 and memory 702;

[0147] The memory stores instructions that the computer executes;

[0148] The processor executes computer execution instructions stored in memory 702, causing the electronic device to perform the operating status monitoring method described above.

[0149] It should be understood that the processor 701 described above can be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), etc. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the method disclosed in this invention can be directly implemented by a hardware processor, or implemented by a combination of hardware and software modules within the processor. The memory 702 may include high-speed random access memory (RAM), and may also include non-volatile memory (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.

[0150] This application also provides a computer-readable storage medium storing computer-executable instructions, which are used to monitor the running state when the computer-executable instructions are executed by a processor.

[0151] This application also provides a computer program product, including a computer program that, when executed by a processor, implements a method for monitoring the running status.

[0152] The collection, storage, use, processing, transmission, provision, and disclosure of financial data or user data involved in the technical solution of this application all comply with the provisions of relevant laws and regulations and do not violate public order and good morals.

[0153] Other embodiments of this application will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of this application that follow the general principles of this application and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of this application are indicated by the following claims.

[0154] It should be understood that this application is not limited to the precise structure described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of this application is limited only by the appended claims.

Claims

1. A method of monitoring the operating state, characterized in that The method is applied to an operation system, the operation system comprising a business service layer and a data layer, wherein the business service layer comprises an interface automation module and a plurality of service ends, and the method comprises: acquiring a first task through the interface automation module, the first task being used to instruct monitoring of a technical case; acquiring a service end address and case information according to analysis processing of the first task by the interface automation module, and sending the case information to a corresponding service end according to the service end address, so that the service end executes the technical case according to the case information; acquiring an execution result returned by the service end, storing the execution result into a database in the data layer, and acquiring a running state of the operation system according to the execution result in the database; the acquiring of the service end address and the case information according to the analysis processing of the first task by the interface automation module comprises: analyzing the first task through the interface automation module to acquire transaction code information and case information; acquiring the service end address from a service directory connected to the interface automation module according to the transaction code information, the service directory storing a mapping relationship between transaction code information and service end addresses; after a cryptographic switch of the interface automation module is opened, acquiring a cryptographic key from a key management center connected to the interface automation module, encrypting the case information to obtain encrypted case information.

2. The method of claim 1, wherein, The business service layer further comprises a job platform interaction module and a job platform, and the method further comprises: acquiring a second task through the job platform interaction module, the second task being used to instruct monitoring of a technical baseline, the second task comprising baseline information; sending the second task to the job platform, so that the job platform acquires an execution script according to the baseline information, and sends the execution script to a client, so that the client executes the execution script to obtain an execution result; acquiring the execution result returned by the job platform, storing the execution result into a database in the data layer, and acquiring a running state of the operation system according to the execution result in the database.

3. The method of claim 2, wherein, After the sending of the second task to the job platform, the method further comprises: starting a query thread, the query thread accessing the job platform at a preset period to request the job platform to return an execution result; terminating the query thread after the job platform is called back.

4. The method according to claim 1 or 2, characterized in that, The acquiring of the running state of the operation system according to the execution result in the database comprises: excluding time without data, aggregating execution results of the same type in time sequence to obtain a flow line space-time diagram, the flow line space-time diagram recording N latest execution results; acquiring a running state of the operation system according to the N latest execution results; wherein N is a natural number greater than or equal to 3.

5. The method of claim 4, wherein, The acquiring of the running state of the operation system according to the N latest execution results comprises: if the latest execution result is an execution failure, determining that a running state of a corresponding execution item is a running failure, the execution item being a technical case or a technical baseline; If the last execution result is success and there is at least one execution failure, it is determined that the running state of the corresponding execution item is running abnormally recovered. If the N execution results are all success, it is determined that the running state of the corresponding execution item is running success.

6. The method of claim 1 or 2, wherein, After storing the execution result into the database in the data layer, the method further comprises: adopting the index life cycle strategy of Elastic Search to process the execution result stored in the database.

7. A running state monitoring apparatus characterized by comprising: comprises: an acquisition module, configured to acquire a first task through an interface automation module, the first task being used to instruct monitoring of a technical case; a processing module, configured to acquire a service end address and case information according to parsing processing of the first task by the interface automation module, and send the case information to a corresponding service end according to the service end address, so that the service end executes the technical case according to the case information; the processing module is further configured to acquire an execution result returned by the service end, store the execution result into a database in a data layer, and acquire a running state of a job system according to the execution result in the database; the processing module is specifically configured to parse the first task through the interface automation module, acquire transaction code information and case information, acquire the service end address from a service directory connected with the interface automation module according to the transaction code information, and the service directory stores a mapping relationship between transaction code information and service end addresses; after an encryption switch of the interface automation module is turned on, acquire an encryption key from a key management center connected with the interface automation module, encrypt the case information to obtain encrypted case information.

8. An electronic device comprising: a processor and a memory; the memory stores computer execution instructions; the processor executes the computer execution instructions stored in the memory, so that the electronic device executes the method in any one of claims 1 to 6.

9. A computer-readable storage medium, characterized in that, The computer readable storage medium stores computer execution instructions, and the computer execution instructions are executed by the processor to implement the running state monitoring method in any one of claims 1 to 6.

10. A computer program product, comprising a computer program, which is executed by a processor to implement the method in any one of claims 1 to 6.

Images