A process state management method and system based on a hybrid cloud architecture

Abstract

The embodiment of the application provides a process state management method and system based on a hybrid cloud architecture, and relates to the technical field of application management. The method comprises the following steps: an operation and maintenance platform receives a business application selected by a user to obtain corresponding application information; a detection start instruction is sent to a corresponding execution machine according to the application information; the execution machine searches an application cluster according to the received detection start instruction to determine whether an application state detection task and a log self-checking task exist; the application cluster obtains and executes an application state detection script to obtain collection information and send the collection information to the execution machine; and the execution machine sends the collection information to the operation and maintenance platform. The method provides a unique interface for the operation and maintenance platform to centrally and uniformly manage business processes under the hybrid cloud architecture, and solves the problems that the existing method cannot uniformly check process states and cannot timely discover application abnormal problems.

Description

Technical Field

[0001] This application relates to the field of application management technology, and more specifically, to a process state management method and system based on a hybrid cloud architecture. Background Technology

[0002] The cloud provider's servers monitor for faults and send alarms to notify users and relevant operations and maintenance personnel. After receiving a valid alarm, the operations or maintenance personnel will log in to the machine to check for service failures and restart the service to determine whether the service has been restored.

[0003] This method cannot provide real-time data access or a unified view of process status. There may be a delay in receiving alerts, or alerts may be missed, leading to delayed service recovery, reduced service availability, and a poor user experience. Summary of the Invention

[0004] The purpose of this application is to provide a process state management method, execution method and device based on a hybrid cloud architecture. Under the hybrid cloud architecture, the operation and maintenance platform provides a unique interface to centrally and uniformly manage business processes, solving the problems of existing methods being unable to uniformly view application process status and unable to detect application anomalies in a timely manner.

[0005] This application provides a process state management method based on a hybrid cloud architecture, the method comprising:

[0006] The operations and maintenance platform receives the business applications selected by the user in order to obtain the corresponding application information;

[0007] Based on the application information, a detection start command is sent to the corresponding execution machine;

[0008] The execution machine searches the application cluster according to the received detection start instruction to determine whether there are application status detection tasks and log self-check tasks.

[0009] The application cluster acquires and executes the application status detection script to obtain collected information and sends the collected information to the execution machine.

[0010] The execution machine sends the collected information to the operation and maintenance platform.

[0011] In the above implementation process, the operation and maintenance platform is used to centrally and uniformly manage the business processes under various hybrid cloud architectures, centrally distribute tasks, and promptly detect anomalies, thus solving the problems of existing methods being unable to uniformly view process status and promptly detect application anomalies.

[0012] Furthermore, the operation and maintenance platform receives the business application selected by the user to obtain the corresponding application information, including:

[0013] Receive any business application selected by the user from a pre-set application list;

[0014] Obtain the corresponding cloud region, application name, application ID, and port information based on the business application.

[0015] In the above implementation process, the operation and maintenance platform provides unified management of various business applications and can send different business applications to the corresponding execution machines.

[0016] Furthermore, the collected information includes application status information, and the method further includes:

[0017] The operation and maintenance platform periodically queries the cloud time-series database based on the application list to obtain and display the application's process time, process status, port status, host information, and application status information.

[0018] In the above implementation process, by periodically querying the cloud time-series database, the process time, application process status, application port status (on demand), host information (IP), and execution result information can be obtained and displayed to the user.

[0019] Furthermore, the execution machine, based on the received detection start instruction, searches the application cluster to determine whether application status detection tasks and log self-check tasks exist, including:

[0020] If it exists, the application cluster pulls the latest application status detection script to update the version of the application status detection script;

[0021] The application status detection task and log self-check task are written into a scheduled task for periodic execution.

[0022] In the above implementation process, the functional scripts of the application cluster are updated to have the latest version, which solves the problem that it is difficult to trace the historical version when the operation and maintenance personnel modify them back and forth on their respective cloud servers, and the problem that different versions of process status management scripts exist on different hosts in the same cloud vendor or the same cloud type.

[0023] Furthermore, the execution machine, based on the received detection start instruction, searches the application cluster to determine whether application status detection tasks and log self-check tasks exist, including:

[0024] If it does not exist, the application cluster will pull the latest application status detection script to preserve the version of the application status detection script;

[0025] The application status detection task and log self-check task are written into a scheduled task for periodic execution.

[0026] If the above implementation process does not exist, the latest application status detection script needs to be retrieved.

[0027] Furthermore, the execution of the application status detection script includes:

[0028] The application cluster backups and updates the execution daemon to obtain application process survival information, process port information, process startup time and host information;

[0029] The application health status is monitored by a daemon process, and the monitoring results are returned to the execution machine. In this implementation, the health status of business applications in the application cluster is obtained in a timely manner through application status flag information.

[0030] Furthermore, the method also includes:

[0031] The execution machine will send the shutdown command received from the operation and maintenance platform to the application cluster, so that the application cluster can shut down its own application status detection task and log self-check task.

[0032] In the above implementation process, upon receiving the shutdown command, it terminates its own application status detection task and log self-check task.

[0033] This application also provides a process state management system based on a hybrid cloud architecture, the system comprising:

[0034] The operation and maintenance platform provides a unique interface and communicates with execution machines in various cloud environments to manage application process information in a unified manner under a hybrid cloud architecture.

[0035] The execution machine is communicatively connected to the corresponding application cluster and is used to receive the start or stop instructions sent by the operation and maintenance platform, and to distribute the start or stop instructions to the corresponding application cluster.

[0036] The application cluster is used to determine whether there is a detection task based on the detection start instruction. If there is, it calls and executes the corresponding function script and sends the execution result to the execution machine.

[0037] In the above implementation process, the operation and maintenance platform is used to centrally and uniformly manage the business processes under various hybrid cloud architectures, centrally distribute tasks, and promptly detect anomalies, thus solving the problems of existing methods being unable to uniformly view process status and promptly detect application anomalies.

[0038] Furthermore, the functional script includes an application status detection script:

[0039] The operation and maintenance platform is used to receive the business application selected by the user to obtain the corresponding application information; and to send a detection start command to the corresponding execution machine according to the application information.

[0040] The execution machine is used to search the application cluster according to the received detection start instruction to determine whether there are application status detection tasks and log self-check tasks.

[0041] The application cluster acquires and executes the application status detection script to obtain collected information and sends the collected information to the execution machine.

[0042] In the above implementation process, the application status is monitored through application status detection tasks and log self-check tasks.

[0043] Furthermore, the application cluster is also used for:

[0044] Backup and update the execution daemon to obtain application process liveness information, process port information, process startup time and host information;

[0045] The application health status is monitored by a daemon process, and the application health status monitoring results are returned to the execution machine.

[0046] In the above implementation process, the health status of business applications in the application cluster is obtained in a timely manner through the application status flag information.

[0047] This application also provides an electronic device, which includes a memory and a processor. The memory stores a computer program, and the processor runs the computer program to enable the computer device to perform the process state management method based on the hybrid cloud architecture described above.

[0048] This application also provides a readable storage medium storing computer program instructions. When the computer program instructions are read and executed by a processor, the process state management method based on the hybrid cloud architecture described above is performed. Attached Figure Description

[0049] To more clearly illustrate the technical solutions of the embodiments of this application, the accompanying drawings used in the embodiments of this application will be briefly introduced below. It should be understood that the following drawings only show some embodiments of this application and should not be regarded as a limitation of the scope. For those skilled in the art, other related drawings can be obtained based on these drawings without creative effort.

[0050] Figure 1 A flowchart illustrating a process state management method based on a hybrid cloud architecture, provided for an embodiment of this application;

[0051] Figure 2 This application provides a flowchart for obtaining application information in an embodiment of the present application.

[0052] Figure 3 A timing diagram for unified management of application process status under a hybrid cloud architecture, provided for embodiments of this application;

[0053] Figure 4 A flowchart illustrating the execution process of the detection start command by the application cluster provided in this embodiment of the application;

[0054] Figure 5 The execution flowchart of the application status detection script provided in the embodiments of this application;

[0055] Figure 6 This is a flowchart illustrating the daemon process determination process provided in an embodiment of this application.

[0056] Figure 7 This is a structural block diagram of a process state management system based on a hybrid cloud architecture, provided in an embodiment of this application.

[0057] icon:

[0058] 100 - Operation and maintenance platform; 200 - Execution machine; 300 - Application cluster. Detailed Implementation

[0059] The technical solutions in the embodiments of this application will now be described with reference to the accompanying drawings.

[0060] It should be noted that similar reference numerals and letters in the following figures indicate similar items; therefore, once an item is defined in one figure, it does not need to be further defined and explained in subsequent figures. Furthermore, in the description of this application, terms such as "first," "second," etc., are used only to distinguish descriptions and should not be construed as indicating or implying relative importance.

[0061] Example 1

[0062] Please refer to Figure 1 , Figure 1 This document presents a flowchart of a process state management method based on a hybrid cloud architecture, as provided in an embodiment of this application. This method is applied to a hybrid cloud architecture, which refers to a centralized and unified management of business processes through an operations and maintenance platform 100 in application environments with different cloud vendors or public-private hybrid cloud environments. Specifically, in a hybrid cloud architecture, the operations and maintenance platform provides a unique deployment interface to control various execution machines 200 in the cloud. It utilizes SSH (Secure Shell) to remotely execute shell scripts for unified task distribution, leverages the cloud storage provided by each cloud vendor for script management, and centrally stores collected data in a time-series database to improve the real-time performance of queries.

[0063] The method specifically includes the following steps:

[0064] Step S100: The operation and maintenance platform 100 receives the business application selected by the user to obtain the corresponding application information;

[0065] Step S200: Send a detection start command to the corresponding execution machine 200 according to the application information;

[0066] Step S300: The execution machine 200 searches the application cluster 300 according to the received detection start instruction to determine whether there are application status detection tasks and log self-check tasks.

[0067] Step S400: The application cluster 300 executes the application status detection script to obtain the collected information and sends the collected information to the execution machine 200;

[0068] Step S500: The execution machine 200 sends the collected information to the operation and maintenance platform 100.

[0069] The execution machine 200 stores the collected information in the cloud time-series database of the operation and maintenance platform 100. Therefore, the operation and maintenance platform 100 can periodically query the cloud time-series database according to the application information in the application list to obtain the collection information corresponding to the application information from the cloud time-series database and display the collection information. The collection information may include, but is not limited to, the application's process time, the application's process status, the application's port status, host information, and the application status information.

[0070] like Figure 2 The diagram shown is a flowchart for obtaining application information. Step S100 may specifically include:

[0071] Step S101: Receive any business application selected by the user according to the pre-set application list;

[0072] Step S102: Obtain the corresponding cloud region, application name, application ID, and port information based on the business application.

[0073] like Figure 3The diagram illustrates the sequence of events for unified management of application process status under a hybrid cloud architecture. Specifically, the user selects a business application name, such as "users," from the application list provided by the data center CMDB (Configuration Management Database) of the operations and maintenance platform 100. The operations and maintenance platform 100 obtains the corresponding cloud region, application name, application ID, and port information based on the user-selected application name. Then, it calls an interface based on the cloud region, application name, application ID, and port information to send a detection start / stop command to the execution machine 200 in the specified cloud. During this process, the user can optionally listen to the business application port. Listening is intended to prevent the business application from appearing "dead," i.e., the business application process exists, but the business application port does not.

[0074] The instructions sent by the operation and maintenance platform 100 include detection start instructions and detection stop instructions. After receiving the detection start instruction, the execution machine 200 in the corresponding cloud server uses remote commands to start searching the application cluster 300 (the N servers where the monitored business application is located) to determine whether there are status detection tasks and log self-check tasks for JAVA classes and C++ services with application names / ports (status detection logs are automatically retained for 20 days).

[0075] like Figure 4 The diagram shows the execution process of the detection start command for application cluster 300, which includes:

[0076] Step S301: If it exists, the application cluster 300 pulls the latest application status detection script to update the version of the application status detection script.

[0077] Step S302: If it does not exist, the application cluster 300 pulls the latest application status detection script to retain the version of the application status detection script;

[0078] Step S303: Write the application status detection task and log self-check task into a scheduled task for periodic execution.

[0079] Specifically, if there are status detection tasks and log self-check tasks, based on the detection start command, application cluster 300 will pull the latest application status detection script from cloud storage and update the version of the application status detection script.

[0080] If not in the status detection and log self-check tasks, Application Cluster 300 will retrieve the latest application detection script from cloud storage (such as Alibaba Cloud) based on cloud region parameters, i.e., the address information. This will preserve the version of the application detection script, thus obtaining the latest application status detection script, and will write the status detection and log self-check tasks into the scheduled tasks. The application status detection script here is a functional script; it can also be a business status collection task script or other functional scripts, without any restrictions.

[0081] If the command is to shut down, the application cluster 300 will delete the status detection task and log self-check task from the system's crond scheduled tasks.

[0082] If it is a shutdown command, no operation will be performed and the log self-check task will be returned directly if the status detection task and log self-check task do not exist.

[0083] The execution result is fed back to the operation and maintenance platform 100 via the API interface to determine whether the switch command was executed successfully.

[0084] The application environment of the daemon process is shown in Table 1. It is compatible with C++ and Java applications in a multi-cloud environment. At the same time, it can be applied to complex business scenarios and manage environments such as Prod, SIT, UAT and DEV. Table 2 shows the application business of the daemon process.

[0085] Table 1 Environmental Dimensions

[0086] Prod 173 875 SIT 160 271 UAT 77 93 DEV 67 90 Other 9 0

[0087] Table 2 Business Dimensions

[0088] Meiju 166 1186 International Homes 31 73 Gateway Cloud 17 39 OEM 15 22 devops 5 9

[0089] For application health monitoring, the application cluster 300 backups and updates the execution daemon process to detect the health status of business applications and obtain application status information such as application process survival information, process port information, process startup time and host information.

[0090] like Figure 5 The diagram shown is the execution flowchart of the application status detection script, which includes the following steps:

[0091] Step S401: The application cluster 300 backs up and updates the execution daemon process to obtain application process survival information, process port information, process startup time and host information;

[0092] Step S402: Monitor the application health status through the daemon process to determine whether the business application is running in a single process and obtain the application status flag information;

[0093] Step S403: The execution machine 200 receives the application status flag information returned by the application cluster 300. The application status flag information includes 0, 1 and 2, where 0 represents normal, 1 represents abnormal and 2 represents collection failure.

[0094] Specifically, the execution machine 200 sends instructions to the application cluster 300 based on cloud region parameters (address information), causing the application cluster 300 to retrieve the guardian task script (application status detection script) from cloud storage and execute it. For example, it retrieves parameters such as application process time, application process status, application port status (on demand), and host information (e.g., IP address) every minute. The monitoring period can be set as needed and is not limited here. If the guardian process already exists, a backup operation is performed first, and the guardian version is updated.

[0095] like Figure 6 The diagram shows the daemon process's judgment flowchart. Application cluster 300 uses the daemon process to monitor the running status of business applications, determining whether the applications are running and their health status. This health status is flagged using status flags and uploaded to the execution machine 200 on the cloud server, generating a health status log. Alarms can be generated based on this log information. Furthermore, based on application port sniffing, an alarm should also be sent if a port appears to be dead.

[0096] The system uses process status detection and application port sniffing to determine if the business application is abnormal. A status flag value of 0 represents normal, 1 represents abnormal, and 2 represents data collection failure. For example, it checks if the application exists, if the process port exists, and if the service process count is 1. If all are true, the application is normal. If an abnormality is detected, the system restarts and sends a flag of 1 to the execution machine (200) to issue an alarm notification. This notifies the developers to check the service and determine if the program is running as a single process after startup to prevent multiple instances of the service from starting. If the application is normal (single process), a normal flag of 0 is sent directly.

[0097] It can also detect whether a Java service has dumped. If a Java application dumps, a core file will be printed in the business application directory.

[0098] Using shell commands and regular expressions, the system retrieves the application's process time, process status, port status (as needed), and host information (such as IP address), as well as the application's startup status flag (application status information), based on the application name. This information is then uploaded to the data acquisition interface of the data acquisition service deployed on the execution machine 200 (the above information can be transmitted via private or public network).

[0099] The service collection interface deployed on machine 200 sends the aforementioned collection information directly to the cloud time-series database InfluxDB where the operation and maintenance platform 100 is located.

[0100] Every 30 seconds, the Operation and Maintenance Platform 100 will query the Operation and Maintenance Time Series Database based on the application list of business applications and display the application's process time, process status, port status (on demand), and host information (IP address). The interval is adjustable and is not limited here. The application status is determined based on the uploaded status flags and displayed on the front end of the Operation and Maintenance Platform 100 so that users can view the status of each application.

[0101] Regularly monitor the health status of services (business applications) and collect application health information promptly (for business quality analysis). If a service anomaly occurs, restart the service immediately. In the event of continuous alarms, the operations platform can directly contact the corresponding development or operations personnel, effectively ensuring service stability, improving user experience, and preventing issues related to untimely service recovery. Simultaneously, the collected application health information can be used for business health quality analysis and data operations.

[0102] By using the 100 Operations and Maintenance Platform for unified management and application process status monitoring, the problems of operation and maintenance personnel modifying their respective cloud servers, making it difficult to trace historical versions, and the existence of different versions of process status management scripts on different hosts within the same cloud provider or cloud type, as well as the difficulty in checking application status due to OOM (out of memory) crashes or abnormal operation shutdowns, requiring personnel to manually check the service status on machine nodes of different cloud providers or cloud types.

[0103] In summary, by unifying the management of application process information under a multi-cloud architecture, we can achieve real-time monitoring of service process status, prevent application instance downtime under massive microservice applications, and address the pain point of business failure, thus ensuring the stable operation of multiple instances.

[0104] The 100 operation and maintenance platform centrally manages business processes under various hybrid cloud architectures, centrally distributes tasks, and performs health monitoring. This enables timely detection of anomalies and addresses the limitations of existing methods in uniformly viewing process status and promptly identifying application anomalies.

[0105] In practice, users only need to click a switch on the 100-page operation and maintenance platform to enable multi-cloud application monitoring. The application cluster 300 can promptly start the service and send alarms, facilitating subsequent troubleshooting. This eliminates the need for operations and development personnel to search through outage lists and manually retrieve them, and also avoids checking application process status via jump servers in various clouds, saving on manual management costs, reducing management complexity, and improving service SLA and user experience.

[0106] Example 2

[0107] This application provides a process state management system based on a hybrid cloud architecture, such as... Figure 7 The diagram shown is a structural block diagram of a process state management system based on a hybrid cloud architecture. This system includes:

[0108] The operation and maintenance platform 100 provides a unique interface and communicates with the execution machines 200 in various cloud environments to uniformly manage application process information under the hybrid cloud architecture.

[0109] The execution machine 200 is communicatively connected to the corresponding application cluster 300, and is used to receive the start or stop instructions sent by the operation and maintenance platform 100, and distribute the start or stop instructions to the corresponding application cluster 300.

[0110] The application cluster 300 is used to determine whether there is a detection task based on the detection start instruction. If there is, it calls and executes the corresponding function script and sends the execution result to the execution machine 200.

[0111] For example, the functional scripts include application status detection scripts:

[0112] The operation and maintenance platform 100 is used to receive the business application selected by the user to obtain the corresponding application information; and to send a detection start command to the corresponding execution machine 200 according to the application information.

[0113] The execution machine 200 is used to search the application cluster 300 according to the received detection start instruction to determine whether there are application status detection tasks and log self-check tasks.

[0114] If it exists, then the application cluster 300 will obtain and execute the application status detection script to obtain the collected information and send the collected information to the execution machine 200.

[0115] Application Cluster 300 is also used for:

[0116] Backup and update the execution daemon to obtain application process liveness information, process port information, process startup time and host information;

[0117] The application health status is monitored by a daemon process to determine whether the business application is running in a single process and to obtain application status flag information.

[0118] The application status flag information is sent to the execution machine 200. The application status flag information includes 0, 1 and 2, where 0 represents normal, 1 represents abnormal and 2 represents acquisition failure.

[0119] The specific execution process has been described in detail in Example 1, and will not be repeated here.

[0120] This application also provides an electronic device, which includes a memory and a processor. The memory is used to store a computer program, and the processor runs the computer program to enable the computer device to execute the process state management method based on the hybrid cloud architecture described in Embodiment 1.

[0121] This application also provides a readable storage medium storing computer program instructions. When the computer program instructions are read and executed by a processor, the process state management method based on a hybrid cloud architecture described in Embodiment 1 is executed.

[0122] In the several embodiments provided in this application, it should be understood that the disclosed apparatus and methods can also be implemented in other ways. The apparatus embodiments described above are merely illustrative. For example, the flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of apparatus, methods, and computer program products according to various embodiments of this application. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions marked in the blocks may occur in a different order than those marked in the drawings. For example, two consecutive blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in a block diagram and / or flowchart, and combinations of blocks in block diagrams and / or flowcharts, can be implemented using a dedicated hardware-based system that performs the specified function or action, or using a combination of dedicated hardware and computer instructions.

[0123] In addition, the functional modules in the various embodiments of this application can be integrated together to form an independent part, or each module can exist independently, or two or more modules can be integrated to form an independent part.

[0124] If the aforementioned functions are implemented as software functional modules and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0125] The above description is merely an embodiment of this application and is not intended to limit the scope of protection of this application. Various modifications and variations can be made to this application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of protection of this application. It should be noted that similar reference numerals and letters in the following figures indicate similar items; therefore, once an item is defined in one figure, it does not need to be further defined and explained in subsequent figures.

[0126] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the technical scope disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

[0127] It should be noted that, in this document, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

Claims

1. A process state management method based on a hybrid cloud architecture, characterized in that, The operations and maintenance platform provides a unique interface and communicates with execution machines in various cloud environments to uniformly manage application process information under a hybrid cloud architecture. The method includes: The operations and maintenance platform receives the business applications selected by the user in order to obtain the corresponding application information; Based on the application information, a detection start command is sent to the corresponding execution machine; The execution machine searches the application cluster according to the received detection start instruction to determine whether there are application status detection tasks and log self-check tasks. If present, the application cluster executes an application status detection script to obtain the collected information and sends the collected information to the execution machine; The execution machine sends the collected information to the operation and maintenance platform. Specifically, the execution machine stores the collected information in the cloud time-series database of the operation and maintenance platform. The operation and maintenance platform periodically queries the cloud time-series database according to the application list to obtain and display the application's process time, application's process status, application's port status, host information, and / or application status information. The collected information includes the application's process time, application's process status, application's port status, host information, and application status information.

2. The process state management method based on a hybrid cloud architecture according to claim 1, characterized in that, The operation and maintenance platform receives the business application selected by the user to obtain the corresponding application information, including: Receive any business application selected by the user from a pre-set application list; Obtain the corresponding cloud region, application name, application ID, and port information based on the business application.

3. The process state management method based on a hybrid cloud architecture according to claim 1, characterized in that, The execution machine searches the application cluster according to the received detection start command to determine whether there are application status detection tasks and log self-check tasks, including: If it exists, the application cluster pulls the latest application status detection script to update the version of the application status detection script; The application status detection task and log self-check task are written into a scheduled task for periodic execution.

4. The process state management method based on a hybrid cloud architecture according to claim 1, characterized in that, The execution machine searches the application cluster according to the received detection start command to determine whether there are application status detection tasks and log self-check tasks, including: If it does not exist, the application cluster will pull the latest application status detection script to preserve the version of the application status detection script; The application status detection task and log self-check task are written into a scheduled task for periodic execution.

5. The process state management method based on a hybrid cloud architecture according to claim 1, characterized in that, The execution of the application status detection script includes: The application cluster backups and updates the execution daemon to obtain application process survival information, process port information, process startup time and host information; The application health status is monitored by a daemon process, and the application health status monitoring results are returned to the execution machine.

6. The process state management method based on a hybrid cloud architecture according to claim 1, characterized in that, The method further includes: The execution machine will send the detection shutdown command received from the operation and maintenance platform to the application cluster, so that the application cluster can shut down its own application status detection task and log self-check task.

7. A process state management system based on a hybrid cloud architecture, characterized in that, The system includes: The operation and maintenance platform provides a unique interface and communicates with execution machines in various cloud environments to manage application process information in a unified manner under a hybrid cloud architecture. The execution machine is communicatively connected to the corresponding application cluster and is used to receive detection start or detection stop instructions sent by the operation and maintenance platform, and to distribute the detection start or detection stop instructions to the corresponding application cluster. The application cluster is used to determine whether a detection task exists based on the detection start command. If it exists, it calls and executes the corresponding functional script and sends the execution result to the execution machine. The functional script includes an application status detection script. The operation and maintenance platform is used to receive the business application selected by the user to obtain the corresponding application information; and sends the detection start command to the corresponding execution machine based on the application information. The execution machine is used to search the application cluster according to the received detection start instruction to determine whether there are application status detection tasks and log self-check tasks. If present, the application cluster acquires and executes the application status detection script to obtain collected information and sends the collected information to the execution machine. The execution machine then sends the collected information to the operation and maintenance platform. Specifically, the execution machine stores the collected information in the cloud time-series database of the operation and maintenance platform. The operation and maintenance platform periodically queries the cloud time-series database based on the application list to obtain and display the application's process time, application's process status, application's port status, host information, and / or application status information. The collected information includes the application's process time, application's process status, application's port status, host information, and application status information.

8. The process state management system based on a hybrid cloud architecture according to claim 7, characterized in that, The application cluster is also used for: Backup and update the execution daemon to obtain application process liveness information, process port information, process startup time and host information; The application health status is monitored by a daemon process, and the application health status monitoring results are returned to the execution machine.

9. An electronic device, characterized in that, The electronic device includes a memory and a processor, the memory being used to store a computer program, and the processor running the computer program to cause the computer device to perform the process state management method based on a hybrid cloud architecture according to any one of claims 1 to 6.

10. A readable storage medium, characterized in that, The readable storage medium stores computer program instructions, which are read and executed by a processor to perform the process state management method based on a hybrid cloud architecture as described in any one of claims 1 to 6.

Images