Abnormality monitoring method and device

Abstract

The invention discloses an exception monitoring method and device, and relates to the technical field of computers. A specific embodiment of the method comprises the following steps: intercepting an execution request of a business process, and determining a process identifier of the business process according to the execution request; in the execution process of the business process, obtaining execution results of a plurality of nodes corresponding to the process identifier; according to the execution result and an exception recognition expression, determining an exceptional target node in the plurality of nodes so as to perform exception processing on the target node; wherein the exception recognition expression corresponds to the process identifier in the configuration library and is used for recognizing whether the node is abnormal or not. According to the embodiment, the execution result of each node in the process is intercepted, and the abnormal node is accurately positioned according to the execution result and the exception identification expression, so that the abnormal node is checked and processed in time, and normal operation of a service is ensured.

Description

Technical Field

[0001] The present invention relates to the field of big data technology, and in particular to an abnormality monitoring method and device. Background Art

[0002] In a distributed microservice system, the relationship between service modules is complex, and multiple services are often called to complete a business process. When an exception occurs in the execution of a called service, the exception monitoring mechanism equipped by the called service automatically issues an alarm, such as using an API (Application Programming Interface) alarm.

[0003] In the process of implementing the present invention, the inventors found that there are at least the following problems in the related art:

[0004] Since the calling service cannot perceive the abnormality of the called service, the calling service will not issue an abnormality alarm even though the calling service has not responded to the calling request. In addition, for abnormalities caused by the calling request not reaching the called service due to network abnormalities, neither the called service nor the calling service will issue an alarm prompt, which makes it impossible to discover and handle some abnormalities in time. The only way is to check the entire process to determine the abnormal service when the process execution times out. Summary of the invention

[0005] In view of this, an embodiment of the present invention provides an exception monitoring method and device, which intercepts the execution request of a business process and determines the process identifier of the business process according to the execution request; during the execution of the business process, obtains the execution results of multiple nodes corresponding to the process identifier; according to the execution result and the abnormal identification expression corresponding to the process identifier in the configuration library for identifying whether the node is abnormal, determines the target node where the abnormality occurs among the multiple nodes, so as to perform abnormal processing on the target node. Thus, by intercepting the execution results of each node in the process, according to the execution results and the abnormal identification expression, the abnormal node is accurately located, so as to realize timely investigation and processing of the abnormal node, thereby ensuring the normal operation of the business.

[0006] To achieve the above objective, according to one aspect of an embodiment of the present invention, a method for monitoring an abnormality is provided.

[0007] An exception monitoring method according to an embodiment of the present invention includes: intercepting an execution request of a business process, and determining a process identifier of the business process according to the execution request; during the execution of the business process, obtaining the execution results of multiple nodes corresponding to the process identifier; based on the execution results and an exception identification expression, determining a target node in which an exception occurs among the multiple nodes, so as to perform exception processing on the target node; wherein the exception identification expression corresponds to the process identifier in the configuration library, and is used to identify whether a node is abnormal.

[0008] Optionally, determining the target node where the abnormality occurs among the multiple nodes based on the execution result and the abnormality identification expression corresponding to the process identifier in the configuration library for identifying whether the node is abnormal includes: determining whether the execution result meets the normal return value according to the normal return values ​​of the multiple nodes indicated by the abnormality identification expression; and determining the node corresponding to the execution result that does not meet the corresponding normal return value as the target node.

[0009] Optionally, determining the target node where the abnormality occurs among the multiple nodes according to the execution result and the abnormality identification expression corresponding to the process identifier in the configuration library and used to identify whether the node is abnormal includes: determining, according to the execution result, a first abnormal node whose execution result includes an abnormality identifier among the multiple nodes; determining, according to the calling relationship between the multiple nodes indicated by the abnormality identification expression, a second abnormal node that directly or indirectly calls the first abnormal node from the multiple nodes; and using the first abnormal node and the second abnormal node as the target nodes.

[0010] Optionally, determining the process identifier of the business process based on the execution request includes: extracting process information of the business process from the execution request; matching the process information with process configuration information in the configuration library; and when the process information and the process configuration information are successfully matched, determining the process identifier corresponding to the successfully matched process configuration information in the configuration library as the process identifier of the business process.

[0011] Optionally, the method provided by the embodiment of the present invention further includes at least one of the following:

[0012] If the process information and the process configuration information are not matched successfully, extracting a process identifier and a node identifier from the process information; registering the business process in the configuration library according to the process identifier and the node identifier;

[0013] Determine whether the execution time of the business process exceeds the preset duration indicated in the exception identification strategy; if it exceeds the preset duration, determine the target node according to the currently acquired execution result and the exception identification expression.

[0014] Optionally, the method provided by the embodiment of the present invention further includes: determining an exception identification expression corresponding to the business process according to the process information; and registering the exception identification expression and the process identifier in the configuration library accordingly.

[0015] Optionally, the method provided by an embodiment of the present invention is applied to an online family doctor consultation system, and the method includes: intercepting an execution request of the system's medical consultation form creation process, and determining the process identifier of the medical consultation form creation process based on the execution request; during the execution of the medical consultation form creation process, obtaining the execution results of multiple nodes corresponding to the process identifier; the multiple nodes include saving user medical record information, checking the current fee payment status or whether membership services are available, and creating a consultation card.

[0016] To achieve the above objective, according to another aspect of an embodiment of the present invention, an abnormality monitoring device is provided.

[0017] An exception monitoring device according to an embodiment of the present invention includes: a request interception module, which is used to intercept the execution request of a business process and determine the process identifier of the business process according to the execution request; a result acquisition module, which is used to obtain the execution results of multiple nodes corresponding to the process identifier during the execution of the business process; an exception analysis module, which is used to determine the target node where the exception occurs among the multiple nodes according to the execution result and the exception identification expression, so as to perform exception processing on the target node; wherein the exception identification expression corresponds to the process identifier in the configuration library and is used to identify whether the node is abnormal.

[0018] To achieve the above objective, according to another aspect of an embodiment of the present invention, an electronic device for abnormality monitoring is provided.

[0019] An electronic device for abnormality monitoring according to an embodiment of the present invention comprises: one or more processors; a storage device for storing one or more programs, and when the one or more programs are executed by the one or more processors, the one or more processors implement an abnormality monitoring method according to an embodiment of the present invention.

[0020] To achieve the above objective, according to another aspect of an embodiment of the present invention, a computer-readable storage medium is provided.

[0021] A computer-readable storage medium according to an embodiment of the present invention stores a computer program, and when the program is executed by a processor, an abnormality monitoring method according to an embodiment of the present invention is implemented.

[0022] One embodiment of the above invention has the following advantages or beneficial effects: by intercepting the execution request of the business process, and determining the process identifier of the business process according to the execution request; during the execution of the business process, obtaining the execution results of multiple nodes corresponding to the process identifier; according to the execution result and the abnormal identification expression, determining the target node where the abnormality occurs among the multiple nodes, so as to perform abnormal processing on the target node; wherein the abnormal identification expression corresponds to the process identifier in the configuration library, and is used to identify whether the node is abnormal. Thus, by intercepting the execution results of each node in the process, according to the execution results and the abnormal identification expression, the abnormal node is accurately located, so as to realize timely investigation and processing of the abnormal node, thereby ensuring the normal operation of the business.

[0023] The further effects of the above-mentioned non-conventional optional manner will be described below in conjunction with the specific implementation manner. BRIEF DESCRIPTION OF THE DRAWINGS

[0024] The accompanying drawings are used to better understand the present invention and do not constitute an improper limitation of the present invention.

[0025] Figure 1 is a schematic diagram of the main steps of an abnormality monitoring method according to an embodiment of the present invention;

[0026] Figure 2 is a schematic diagram of main steps of determining a process identifier and a node identifier of an abnormality monitoring method according to an embodiment of the present invention;

[0027] Figure 3 is a schematic diagram of the main steps of determining abnormal nodes in an abnormal monitoring method according to an embodiment of the present invention;

[0028] Figure 4 is a schematic diagram of the main steps of determining abnormal nodes in an abnormal monitoring method according to an embodiment of the present invention;

[0029] Figure 5 is a schematic diagram of main steps of an abnormality monitoring method according to an embodiment of the present invention;

[0030] Figure 6 is a schematic diagram of main modules of an abnormality monitoring device according to an embodiment of the present invention;

[0031] Figure 7 is an exemplary system architecture diagram to which embodiments of the present invention may be applied;

[0032] Figure 8 It is a schematic diagram of the structure of a computer system of a terminal device or a server suitable for implementing an embodiment of the present invention. DETAILED DESCRIPTION

[0033] The following is a description of exemplary embodiments of the present invention in conjunction with the accompanying drawings, including various details of the embodiments of the present invention to facilitate understanding, which should be considered as merely exemplary. Therefore, it should be recognized by those of ordinary skill in the art that various changes and modifications may be made to the embodiments described herein without departing from the scope and spirit of the present invention. Similarly, for clarity and conciseness, the description of well-known functions and structures is omitted in the following description.

[0034] It should be noted that the collection, collection, updating, analysis, processing, use, transmission, storage and other aspects of user personal information involved in the technical solution of this disclosure are in compliance with the provisions of relevant laws and regulations, are used for legitimate purposes, and do not violate public order and good morals. Necessary measures are taken for user personal information to prevent illegal access to user personal information data and maintain the security of user personal information, network security and national security.

[0035] It should be pointed out that the embodiments of the present invention and the technical features therein may be combined with each other without conflict.

[0036] Figure 1 Schematic diagram of main steps of an abnormality monitoring method according to an embodiment of the present invention.

[0037] like Figure 1 As shown, the abnormal monitoring method of the embodiment of the present invention mainly includes the following steps:

[0038] Step S101: intercepting an execution request of a business process, and determining a process identifier of the business process according to the execution request.

[0039] The embodiment of the present invention takes the application of the exception monitoring method to a distributed microservice system (hereinafter referred to as a distributed system) as an example to elaborate on the exception monitoring method. In the process of executing a business process in a distributed system, the exception monitoring system that executes the exception monitoring method can intercept process information, determine the name of the business process (process identifier) ​​and the nodes involved in the business process according to the process information, and intercept and save the execution results corresponding to each node (such as the return value of the node, whether the node execution is abnormal, and / or whether the node responds) during the execution of the business process, and finally determine which nodes are abnormal and / or which nodes may be abnormal according to the saved execution results and the exception identification strategy (abnormal identification expression), so as to check and process the abnormal nodes and / or the nodes that may be abnormal, so as to ensure the subsequent normal operation of the distributed system.

[0040] The exception monitoring system can adopt the AOP aspect system (AOP system). In the configuration library of the AOP aspect system, each business process and the node (method) corresponding to the process are configured as a process identifier and a node identifier, and each business process is configured with an exception identification strategy, that is, an exception identification expression. The AOP system can obtain the business process execution request of the distributed system through log monitoring and log interception methods, and determine the process identifier of the business process according to the execution request, so that after obtaining the execution result of the business process, the execution result and the process identifier are saved in the log list in correspondence. The system operation and maintenance personnel can directly determine the execution result including the exception identifier, such as the error code, or the node of the exception through the log list. However, this directly determined abnormal node is only a part of the abnormal nodes that can be determined by this method. Other types of abnormal nodes need to be determined based on the execution results and the abnormal identification expression.

[0041] In one embodiment of the present invention, the method is applied to an online family doctor consultation system, and the method includes: intercepting the execution request of the medical consultation form creation process of the system, and determining the process identifier of the medical consultation form creation process according to the execution request; during the execution of the medical consultation form creation process, obtaining the execution results of multiple nodes corresponding to the process identifier; the multiple nodes include user medical record information preservation, checking the current fee payment status or whether membership services can be enjoyed, and creating a medical consultation card. Among them, the medical consultation card refers to a data message including user medical record information, which is used to send to the doctor so that the doctor can diagnose and prescribe according to the user medical record information included therein.

[0042] The distributed system to which the method of the embodiment of the present invention is applied may be an online family doctor consultation system (referred to as the family doctor system). The abnormal monitoring method of the embodiment of the present invention is introduced below by taking the family doctor system as an example. The family doctor system is an online medical system that provides online users with pharmaceutical services, consultation services, post-diagnosis follow-up services, etc. in an Internet medical scenario. The system can also provide users with different types of membership services, such as quarterly membership and annual membership according to time periods, and can also be divided into 20 consultation service members, unlimited consultation service members, etc. according to the number of consultations. It can be understood that the medical services and membership services provided by the family doctor system include but are not limited to the types described above.

[0043] The family doctor system includes multiple service modules, such as consultation and contract service module, user profile creation module, consultation form creation module, user referral module and / or service replacement module, etc. Referral means assigning the user to a doctor in the corresponding department based on the user's consultation information; replacement means changing the service type after the user purchases one medical service.

[0044] By intercepting the execution request of the business process of the family doctor system, according to the execution request, such as the execution request of the consultation service contract process, the user file creation process, the consultation form creation process, the user referral process and / or the service renewal process, the process identifier is determined, such as signing, creating a file, creating a consultation form, referral and / or renewal. Each business process includes multiple nodes, among which the nodes included in the consultation form creation process are user medical record information preservation (node ​​A), checking the current fee payment status (node ​​B) or whether membership services can be enjoyed (node ​​C) and creating a consultation card (node ​​D).

[0045] It is understandable that the process identifier may include a user identifier, which is used to distinguish multiple identical business processes running in a distributed system. For example, in a family doctor system, there are 8 users signing processes running simultaneously, and the corresponding process identifier can be represented as user 1 signing, user 2 signing, user 3 signing... The representation method of other process identifiers can be the same.

[0046] In one embodiment of the present invention, determining the process identifier of the business process based on the execution request includes: extracting process information of the business process from the execution request; matching the process information with process configuration information in the configuration library; and when the process information and the process configuration information are successfully matched, determining the process identifier corresponding to the successfully matched process configuration information in the configuration library as the process identifier of the business process.

[0047] After intercepting the execution request of the medical service process of the family doctor system, the process information of the process is extracted from the execution request, such as the process information of the service contract signing process, which includes the process identifier of the service contract signing process (such as user 1 signing the contract) and the node information of the service contract signing process, such as relevant information of the contract saving node, relevant information of the user file saving node, relevant information of the file data synchronization node and relevant information of the user reminder message sending node.

[0048] Based on the process information, the process of determining the process identifier is as follows: first, determine whether the medical service process has been registered (configured) in the configuration library, that is, by comparing the process information with the process configuration information in the configuration library. If the comparison is consistent, it can be confirmed that the intercepted current business process has been registered (configured) in the configuration library, and the corresponding process identifier in the configuration library can be used as the process identifier of the current business process; if the comparison is inconsistent, it can be confirmed that the current business process has not been registered (configured) in the configuration library. At this time, the current business process needs to be registered (configured) in the configuration library.

[0049] For example, the intercepted medical service process is a service contract signing process. The process information of the process includes relevant information of user 1, relevant information of the service contract signing process, relevant information of the contract signing saving node, relevant information of the user file saving node, relevant information of the file data synchronization node, and relevant information of the user reminder message sending node, etc. The process information is compared with the configuration information in the configuration library. If the service contract signing process has been registered (configured) in the configuration library, the "User 1 Contract Signing" in the configuration library can be successfully matched with the process information. At this time, "User 1 Contract Signing" is used as the process identifier of the current business process. If the service contract signing process has not been registered (configured) in the configuration library, "User 1 Contract Signing" does not exist in the configuration library, so the process configuration information in the configuration library cannot be successfully matched with the process information of the service contract signing process. At this time, the service contract signing process needs to be registered (configured) in the configuration library.

[0050] In one embodiment of the present invention, the method further includes: when the process information fails to match the process configuration information, extracting a process identifier and a node identifier from the process information; and registering the business process into the configuration library based on the process identifier and the node identifier.

[0051] In the case that the service contract signing process of the home medical system has not been registered (configured) in the configuration library, the process identifier and node identifier are extracted from the intercepted process information, and the process identifier and node identifier are configured in the configuration library, that is, the service contract signing process is registered in the configuration library. For example, the process identifier, such as "User 1 signing", and the node identifier, such as "Contract saving", "User file saving", "Data synchronization" and "Message reminder" are extracted from the process information of the service contract signing process, such as relevant information of User 1, relevant information of the service contract signing process, relevant information of the contract saving node, relevant information of the user file saving node, relevant information of the file data synchronization node and relevant information of the user reminder message sending node, etc., and then "Contract saving", "User file saving", "Data synchronization" and "Message reminder" are configured in the configuration library in correspondence with "User 1 signing".

[0052] The following uses the family doctor system as an example to introduce how to determine the process identifier of the medical service process in the abnormal monitoring method.

[0053] Figure 2 It is a schematic diagram of the main steps of determining the process identifier and the node identifier of the abnormal monitoring method according to an embodiment of the present invention.

[0054] like Figure 2 As shown, the determination process identifier and node identifier of the abnormal monitoring method of the embodiment of the present invention mainly includes the following steps:

[0055] Step S201: intercepting an execution request of a medical service process, and extracting process information from the intercepted process execution request;

[0056] Step S202: Determine whether the process information matches the process configuration information in the configuration library. If yes, execute step S203; if not, execute step S204;

[0057] Step S203: Determine the successfully matched process identifier and the corresponding node identifier in the configuration library as the process identifier and node identifier of the medical service process;

[0058] Step S204: extracting the process identifier and the node identifier from the process information;

[0059] Step S205: configuring the extracted process identifier and node identifier into the configuration library;

[0060] Step S206: Using the extracted process identifier and node identifier as the process identifier and node identifier of the medical service process.

[0061] In one embodiment of the present invention, the method further includes: determining an exception identification expression corresponding to the business process according to the process information; and registering the exception identification expression and the process identifier in the configuration library accordingly.

[0062] After configuring the process identifier and node identifier of the current business process to the configuration library, it is also necessary to configure an exception identification expression for the current business process to determine whether the process is executed abnormally and determine the abnormal node (target node) after the current business process is executed. The abnormal identification expression can represent the normal return values ​​corresponding to the multiple nodes corresponding to the process, that is, the data returned by each node of the process under normal circumstances. The execution result corresponding to each node is compared with the corresponding normal return value. The node corresponding to the consistent execution result is a normal node, and the node corresponding to the inconsistent execution result is an abnormal node. For example, the nodes corresponding to the consultation form creation process are user medical record information preservation (node ​​A), checking the current fee payment status (node ​​B) or whether membership services can be enjoyed (node ​​C) and creating a consultation card (node ​​D). The abnormal identification expression corresponding to the consultation form creation process can be: (node ​​A return data is not empty and node B return value is 1 and node D status value is normal) or (node ​​A return data is not empty and node C return value is 1 and node D status value is normal). After obtaining the execution results of node A, node B, node C, and node D, determine whether the execution results conform to the normal return values ​​of each node indicated by the exception identification expression. If so, determine that the node is a normal node; if not, determine that the node is an abnormal node and needs to be checked and processed.

[0063] The exception identification expression can also represent the calling relationship between multiple nodes corresponding to the business process. For example, the calling relationship between nodes A, B, C and D corresponding to the medical consultation form creation process is D—>B—>A (node ​​B calls node A, node D calls node B) or D—>C—>A (node ​​C calls node A, node D calls node C). If the execution result of node A in the execution result is abnormal, it can be determined that nodes D and B or nodes D and C are also abnormal nodes based on the calling relationship, and nodes A, D and B or nodes A, D and C are checked and processed.

[0064] Step S102: During the execution of the business process, the execution results of multiple nodes corresponding to the process identifier are obtained.

[0065] In the process of executing the medical service process in the home medical system, the execution results of multiple nodes corresponding to the process identifier are obtained from the configuration library according to the process identifier of the current process. For example, if the current business is the process of creating a consultation form for user 2, according to the process identifier of the process, such as "user 2 consultation form creation", the node identifier corresponding to the node corresponding to "user 2 consultation form creation" is determined from the configuration library, such as user 2 medical record information preservation (node ​​A identifier), user 2 fee payment (node ​​B identifier) ​​or user 2 membership service (node ​​C identifier) ​​and user 2 consultation card creation (node ​​D identifier), and the corresponding execution results are obtained according to the node identifiers corresponding to nodes A, B, C and D.

[0066] Step S103: According to the execution result and the exception identification expression, determine the target node where the exception occurs among the multiple nodes, so as to perform exception processing on the target node; wherein the exception identification expression corresponds to the process identifier in the configuration library and is used to identify whether the node is abnormal.

[0067] In one embodiment of the present invention, determining the target node where the abnormality occurs among the multiple nodes based on the execution result and the abnormality identification expression corresponding to the process identifier in the configuration library for identifying whether the node is abnormal includes: determining whether the execution result meets the normal return value according to the normal return values ​​of the multiple nodes indicated by the abnormality identification expression; and determining the node corresponding to the execution result that does not meet the corresponding normal return value as the target node.

[0068] According to the execution results corresponding to the medical service process of the family doctor system, the execution results of each node are compared with the normal return value indicated by the abnormal identification expression to determine whether the comparison results are consistent. The node corresponding to the execution result with consistent comparison results can be determined as a normal node, and the node corresponding to the execution result with inconsistent comparison results is an abnormal node (target node).

[0069] For example, the exception identification expression corresponding to the consultation form creation process is: (node ​​A return data is not empty and node B return value is 1 and node D status value is normal) or (node ​​A return data is not empty and node C return value is 1 and node D status value is normal). After obtaining the execution results of nodes A, B, C and D, determine whether the return data (execution result) of node A is empty. If it is empty, node A is an abnormal node; determine whether the return value (execution result) of node B is 1. If it is 1, node B is a normal node; determine whether the status value (execution result) of node D is normal (normal can be set to 1 and abnormal to 0). If the status value is 1, node D is determined to be a normal node. If the status value is 0, node D is determined to be an abnormal node.

[0070] It can be understood that for nodes whose execution results contain exception identifiers, such as "exception", they can be directly determined as abnormal nodes; for nodes whose execution results do not contain exception identifiers, such as "exception", whether they are abnormal nodes is determined by the normal return value indicated by the exception identification expression.

[0071] The following uses the family doctor system as an example to introduce how to determine abnormal nodes in the medical service process in the abnormal monitoring method.

[0072] Figure 3 4 is a schematic diagram of the main steps of determining abnormal nodes in the abnormal monitoring method according to an embodiment of the present invention.

[0073] like Figure 3 As shown, the abnormal node determination method of the abnormal monitoring method of the embodiment of the present invention mainly includes the following steps:

[0074] Step S301: Obtaining execution results of multiple nodes corresponding to the medical service process;

[0075] Step S302: Determine whether the execution result contains an abnormality mark, if yes, execute step S304; if no, execute step S303;

[0076] Step S303: Determine that multiple nodes are all normal nodes;

[0077] Step S304: determining the node corresponding to the execution result containing the abnormal identification as an abnormal node;

[0078] Step S305: compare the execution result not including the exception identifier with the normal return value indicated by the exception identification expression to determine whether the comparison results are consistent. If yes, execute step S306; if not, execute step S307;

[0079] Step S306: Determine that the node corresponding to the execution result that does not include an abnormal flag is a normal node;

[0080] Step S307: Determine that the node corresponding to the execution result that does not include the abnormal identification is an abnormal node.

[0081] In one embodiment of the present invention, the determining, according to the execution result and the abnormal identification expression corresponding to the process identifier in the configuration library for identifying whether the node is abnormal, the target node where the abnormality occurs among the multiple nodes includes: determining, according to the execution result, a first abnormal node whose execution result includes an abnormal identification among the multiple nodes; determining, according to the calling relationship between the multiple nodes indicated by the abnormal identification expression, a second abnormal node that directly or indirectly calls the first abnormal node from the multiple nodes; and using the first abnormal node and the second abnormal node as the target nodes.

[0082] The abnormal node can also be determined based on the calling relationship between multiple nodes corresponding to the medical service process indicated by the abnormal identification expression, such as the calling relationship between nodes A, B, C and D corresponding to the consultation form creation process is D—>B—>A or D—>C—>A. According to the obtained execution result, where the execution result of node A includes an abnormal identification, such as exception, it can be determined that node A is abnormal. Since node B directly calls node A and node D indirectly calls node A, it can be determined that nodes D and B are also abnormal nodes. Similarly, nodes D and C are also abnormal nodes. System maintenance personnel are required to check and process nodes A, D and B or nodes A, D and C.

[0083] The following uses the family doctor system as an example to introduce how to determine abnormal nodes in the medical service process in the abnormal monitoring method.

[0084] Figure 4 4 is a schematic diagram of the main steps of determining abnormal nodes in the abnormal monitoring method according to an embodiment of the present invention.

[0085] like Figure 4 As shown, the method for processing waybills according to the embodiment of the present invention mainly includes the following steps:

[0086] Step S401: Obtaining execution results of multiple nodes corresponding to the medical service process;

[0087] Step S402: Determine whether the execution result contains an abnormality mark, if yes, execute step S404; if no, execute step S403;

[0088] Step S403: Determine that multiple nodes are all normal nodes;

[0089] Step S404: determining that the node corresponding to the execution result containing the abnormal identification is an abnormal node;

[0090] Step S405: determining the node that directly or indirectly calls the abnormal node according to the calling relationship between the multiple nodes indicated by the abnormal identification expression;

[0091] Step S406: Determine the node that directly or indirectly calls the abnormal node as an abnormal node.

[0092] It can be understood that the above-mentioned embodiments of determining abnormal nodes (target nodes) are all performed when at least one execution result includes an abnormal identification, such as "exception". When all execution results do not include an abnormal identification and the business process ends normally within a preset time, it can be determined that multiple nodes are normal nodes. Therefore, there is no need to determine the abnormal nodes based on the execution results and the abnormal identification expression.

[0093] In one embodiment of the present invention, the method also includes: determining whether the execution time of the business process exceeds the preset duration indicated in the exception identification strategy; if it exceeds the preset duration, determining the target node based on the currently acquired execution result and the exception identification expression.

[0094] When the home medical system executes a medical service process, a situation may occur: the abnormal monitoring system only obtains the execution results of some nodes of multiple nodes, and the obtained execution results do not include the abnormal identification, so it is impossible to determine whether the current state of the process is abnormal based on the execution results. At this time, it is possible to determine whether the process is abnormal by judging whether the process execution time has exceeded. The execution time of the process is compared with the preset duration. If it exceeds the preset duration, it is determined that the business process is abnormal. At this time, according to the process identification of the business process, its corresponding node identification is determined, thereby determining the multiple nodes corresponding to the node identification, and the multiple nodes are checked and processed according to the abnormal identification expression corresponding to the process.

[0095] The following uses the family doctor system as an example to introduce the main steps of the abnormal monitoring method. Figure 5 As shown, the abnormal monitoring method of the embodiment of the present invention mainly includes the following steps:

[0096] Step S501: intercepting an execution request of a medical service process, and determining a process identifier of the process according to the execution request.

[0097] Extract the process information of the medical service process from the execution request; match the process information with the process configuration information in the configuration library; if the process information and the process configuration information match successfully, determine the process identifier corresponding to the successfully matched process configuration information in the configuration library as the process identifier of the medical service process; if the process information and the process configuration information do not match successfully, extract the process identifier from the process information.

[0098] Step S502: Determine multiple nodes corresponding to the medical service process.

[0099] When the process information matches the process configuration information in the configuration library successfully, the node identifier corresponding to the successfully matched process identifier in the configuration library is used as the node identifier corresponding to the medical service process; when the process information does not match the process configuration information successfully, the node identifier is extracted from the process information as the node identifier of the medical service process.

[0100] Step S503: Determine the abnormality identification expression corresponding to the medical service process.

[0101] If the medical service process has been registered in the configuration library, the corresponding abnormal identification expression is determined in the configuration library according to the process identifier of the medical service process. If the medical service process has not been registered in the configuration library, the abnormal identification expression corresponding to the medical service process is determined from the process information.

[0102] Step S504: Obtain execution results corresponding to multiple nodes.

[0103] During the process of executing the medical service process in the home medical system, the execution results corresponding to the node identifiers are intercepted according to the node identifiers.

[0104] Step S505: Determine whether the execution results of all nodes have been obtained, if yes, execute step S506; if not, execute step S508.

[0105] Step S506: Determine whether the execution result contains an abnormal identification, if yes, execute step S509; if no, execute step S507.

[0106] When the execution results of multiple nodes do not include an abnormality mark, it can be determined that the process ends normally. When the execution results of multiple nodes include an abnormality mark, it is determined that an abnormality occurs in the process.

[0107] Step S507: Determine that all of the multiple nodes are normal nodes.

[0108] Step S508: Determine whether the execution time of the medical service process has exceeded the preset time. If yes, execute step S509; if not, execute step S504.

[0109] If the process execution time exceeds the preset time, it can be determined that the process is abnormal; if it does not exceed the preset time, the unobtained execution results can be obtained.

[0110] Step S509: Determine the target node according to the acquired execution result and the abnormal identification expression.

[0111] According to the abnormal monitoring method of the embodiment of the present invention, it can be seen that by intercepting the execution request of the business process, and determining the process identifier of the business process according to the execution request; in the execution process of the business process, obtaining the execution results of multiple nodes corresponding to the process identifier; according to the execution result and the abnormal identification expression, determining the target node where the abnormality occurs among the multiple nodes, so as to perform abnormal processing on the target node; wherein the abnormal identification expression corresponds to the process identifier in the configuration library, and is used to identify whether the node is abnormal. Thus, by intercepting the execution results of each node in the process, according to the execution results and the abnormal identification expression, the abnormal node is accurately located, so as to realize timely investigation and processing of the abnormal node, thereby ensuring the normal operation of the business.

[0112] Figure 6 Schematic diagram of main modules of an abnormality monitoring device according to an embodiment of the present invention.

[0113] like Figure 6 As shown, the abnormality monitoring device 600 of the embodiment of the present invention includes:

[0114] The request interception module 601 is used to intercept the execution request of the business process and determine the process identifier of the business process according to the execution request;

[0115] A result acquisition module 602 is used to acquire the execution results of multiple nodes corresponding to the process identifier during the execution of the business process;

[0116] The exception analysis module 603 is used to determine the target node where the exception occurs among the multiple nodes according to the execution result and the exception identification expression, so as to perform exception processing on the target node; wherein the exception identification expression corresponds to the process identifier in the configuration library and is used to identify whether the node is abnormal.

[0117] In one embodiment of the present invention, the exception analysis module 603 is also used to determine whether the execution result meets the normal return value according to the normal return values ​​of the multiple nodes indicated by the exception identification expression; and determine the node corresponding to the execution result that does not meet the corresponding normal return value as the target node.

[0118] In one embodiment of the present invention, the exception analysis module 603 is further used to determine, according to the execution result, a first abnormal node whose execution result includes an abnormal identifier among the multiple nodes; determine, according to the calling relationship between the multiple nodes indicated by the abnormal identification expression, a second abnormal node that directly or indirectly calls the first abnormal node from the multiple nodes; and use the first abnormal node and the second abnormal node as the target nodes.

[0119] In one embodiment of the present invention, the request interception module 601 is also used to extract the process information of the business process from the execution request; match the process information with the process configuration information in the configuration library; and when the process information and the process configuration information are successfully matched, determine the process identifier corresponding to the successfully matched process configuration information in the configuration library as the process identifier of the business process.

[0120] In one embodiment of the present invention, the request interception module 601 is also used to extract the process identifier and the node identifier from the process information when the process information fails to match the process configuration information; and register the business process in the configuration library based on the process identifier and the node identifier.

[0121] In one embodiment of the present invention, the exception analysis module 603 is also used to determine whether the execution time of the business process exceeds the preset duration indicated in the exception identification strategy; if it exceeds the preset duration, the target node is determined based on the currently acquired execution result and the exception identification expression.

[0122] In one embodiment of the present invention, the request interception module 601 is further used to determine the exception identification expression corresponding to the business process according to the process information; and register the exception identification expression and the process identifier in the configuration library accordingly.

[0123] In one embodiment of the present invention, the device is applied to an online family doctor consultation system, and the request interception module 601 is also used to intercept the execution request of the medical consultation form creation process of the system, and determine the process identifier of the medical consultation form creation process according to the execution request; the result acquisition module 602 is also used to obtain the execution results of multiple nodes corresponding to the process identifier during the execution of the medical consultation form creation process; the multiple nodes include user medical record information preservation, checking the current fee payment status or whether membership services are available, and creating a medical consultation card.

[0124] According to the abnormal monitoring device of the embodiment of the present invention, it can be seen that by intercepting the execution request of the business process, and determining the process identifier of the business process according to the execution request; in the execution process of the business process, obtaining the execution results of multiple nodes corresponding to the process identifier; according to the execution result and the abnormal identification expression, determining the target node where the abnormality occurs among the multiple nodes, so as to perform abnormal processing on the target node; wherein the abnormal identification expression corresponds to the process identifier in the configuration library, and is used to identify whether the node is abnormal. Thus, by intercepting the execution results of each node in the process, according to the execution results and the abnormal identification expression, the abnormal node is accurately located, so as to realize timely investigation and processing of the abnormal node, thereby ensuring the normal operation of the business.

[0125] Figure 7 An exemplary system architecture 700 to which the abnormality monitoring method or abnormality monitoring device according to the embodiment of the present invention can be applied is shown.

[0126] like Figure 7 As shown, the system architecture 700 may include user terminal devices 701, 702, 703, networks 704, 708, distributed system servers 705, 706 and 707, and an abnormality monitoring system server 709. The networks 704, 708 are media for providing communication links between the user terminal devices 701, 702, 703, the distributed system servers 705, 706 and 707, and the abnormality monitoring system server 709. The networks 704, 708 may include various connection types, such as wired, wireless communication links or optical fiber cables, etc.

[0127] The user can use the user terminal devices 701, 702, 703 to interact with the distributed system servers 705, 706 and 707 through the network 704 to receive or send messages, etc. The terminal devices 701, 702, 703 can be installed with a distributed system client, and the interaction with the distributed system servers 705, 706 and 707 is realized through the client. The abnormality monitoring system server 709 is used to monitor the abnormalities that occur during the interaction between the user terminal devices 701, 702, 703 and the distributed system servers 705, 706 and 707.

[0128] The user terminal devices 701, 702, 703 may be various electronic devices with display screens and supporting web browsing, including but not limited to smart phones, tablet computers, laptop portable computers, desktop computers, etc. The abnormal monitoring system server 709 may also be other types of electronic devices, including but not limited to smart phones, tablet computers, laptop portable computers, desktop computers, etc.

[0129] The abnormal monitoring system server 709 may be a server that provides various services, such as a server that provides support for interactive data analysis between the user terminal devices 701, 702, 703 and the distributed system servers 705, 706, and 707. The abnormal monitoring system server 709 may analyze and process the received business process execution request and other data, and feed back the processing results (such as the target node) to the operation and maintenance personnel of the distributed system servers 705, 706, and 707.

[0130] It should be noted that the abnormality monitoring method provided in the embodiment of the present invention is generally executed by the server 709 , and accordingly, the abnormality monitoring device is generally arranged in the server 709 .

[0131] It should be understood that Figure 7 The number of terminal devices, networks and servers in the embodiment is only for illustration. Any number of terminal devices, networks and servers may be provided according to implementation requirements.

[0132] Reference below Figure 8 , which shows a schematic diagram of the structure of a computer system 800 of a terminal device suitable for implementing an embodiment of the present invention. Figure 8 The terminal device shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present invention.

[0133] like Figure 8 As shown, the computer system 800 includes a central processing unit (CPU) 801, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 802 or a program loaded from a storage part 808 into a random access memory (RAM) 803. In the RAM 803, various programs and data required for the operation of the system 800 are also stored. The CPU 801, the ROM 802, and the RAM 803 are connected to each other via a bus 804. An input / output (I / O) interface 805 is also connected to the bus 804.

[0134] The following components are connected to the I / O interface 805: an input section 806 including a keyboard, a mouse, etc.; an output section 807 including a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker, etc.; a storage section 808 including a hard disk, etc.; and a communication section 809 including a network interface card such as a LAN card, a modem, etc. The communication section 809 performs communication processing via a network such as the Internet. A drive 810 is also connected to the I / O interface 805 as needed. A removable medium 811, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed on the drive 810 as needed, so that a computer program read therefrom is installed into the storage section 808 as needed.

[0135] In particular, according to the embodiments disclosed in the present invention, the process described above with reference to the flowchart can be implemented as a computer software program. For example, the embodiments disclosed in the present invention include a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program includes a program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from the network through the communication part 809, and / or installed from the removable medium 811. When the computer program is executed by the central processing unit (CPU) 801, the above-mentioned functions defined in the system of the present invention are executed.

[0136] It should be noted that the computer-readable medium shown in the present invention may be a computer-readable signal medium or a computer-readable storage medium or any combination of the above two. The computer-readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present invention, a computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in combination with an instruction execution system, device or device. In the present invention, a computer-readable signal medium may include a data signal propagated in a baseband or as part of a carrier wave, which carries a computer-readable program code. This propagated data signal may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. Computer-readable signal media may also be any computer-readable medium other than computer-readable storage media, which may send, propagate or transmit a program for use by or in conjunction with an instruction execution system, apparatus or device. The program code contained on the computer-readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wire, optical cable, RF, etc., or any suitable combination of the above.

[0137] The flow chart and block diagram in the accompanying drawings illustrate the possible architecture, function and operation of the system, method and computer program product according to various embodiments of the present invention. In this regard, each box in the flow chart or block diagram can represent a module, a program segment, or a part of a code, and the above-mentioned module, program segment, or a part of a code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order from the order marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram or flow chart, and the combination of the boxes in the block diagram or flow chart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0138] The modules involved in the embodiments of the present invention may be implemented in software or hardware. The modules described may also be set in a processor, for example, it may be described as: a processor includes a request interception module, a result acquisition module, and an exception analysis module. The names of these modules do not constitute a limitation on the modules themselves in some cases, for example, the exception analysis module may also be described as "a module for determining a target node in which an exception occurs among the multiple nodes".

[0139] As another aspect, the present invention also provides a computer-readable medium, which may be included in the device described in the above embodiment; or it may exist independently without being assembled into the device. The above computer-readable medium carries one or more programs, and when the above one or more programs are executed by a device, the device includes: intercepting the execution request of the business process, and determining the process identifier of the business process according to the execution request; during the execution of the business process, obtaining the execution results of multiple nodes corresponding to the process identifier; according to the execution results and the exception identification expression, determining the target node where the exception occurs among the multiple nodes, so as to perform exception processing on the target node; wherein the exception identification expression corresponds to the process identifier in the configuration library, and is used to identify whether the node is abnormal.

[0140] According to the technical solution of the embodiment of the present invention, by intercepting the execution request of the business process, and determining the process identifier of the business process according to the execution request; in the execution process of the business process, obtaining the execution results of multiple nodes corresponding to the process identifier; according to the execution result and the abnormal identification expression, determining the target node where the abnormality occurs among the multiple nodes, so as to perform abnormal processing on the target node; wherein the abnormal identification expression corresponds to the process identifier in the configuration library, and is used to identify whether the node is abnormal. Thus, by intercepting the execution results of each node in the process, according to the execution results and the abnormal identification expression, the abnormal node is accurately located, so as to realize timely investigation and processing of the abnormal node, thereby ensuring the normal operation of the business.

[0141] The above specific implementations do not constitute a limitation on the protection scope of the present invention. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions may occur depending on design requirements and other factors. Any modification, equivalent substitution and improvement made within the spirit and principle of the present invention shall be included in the protection scope of the present invention.

Claims

1. An abnormality monitoring method, characterized in that: include: Intercepting an execution request of a business process, and determining a process identifier of the business process according to the execution request; During the execution of the business process, obtaining the execution results of multiple nodes corresponding to the process identifier; According to the execution result and the exception identification expression, the target node where the exception occurs among the multiple nodes is determined to perform exception processing on the target node; wherein the exception identification expression corresponds to the process identifier in the configuration library and is used to identify whether the node is abnormal.

2. The method according to claim 1, characterized in that The step of determining, according to the execution result and the abnormality identification expression, a target node where an abnormality occurs among the multiple nodes comprises: According to the normal return values ​​of the multiple nodes indicated by the abnormal identification expression, determining respectively whether the execution result conforms to the normal return value; The node corresponding to the execution result that does not meet the corresponding normal return value is determined as the target node.

3. The method according to claim 1, characterized in that The step of determining, according to the execution result and the abnormality identification expression, a target node where an abnormality occurs among the multiple nodes comprises: According to the execution result, determining a first abnormal node among the multiple nodes whose execution result includes an abnormality identifier; According to the calling relationship between the multiple nodes indicated by the abnormal identification expression, determining a second abnormal node that directly or indirectly calls the first abnormal node from the multiple nodes; The first abnormal node and the second abnormal node are used as the target nodes.

4. The method according to claim 1, characterized in that: The determining the process identifier of the business process according to the execution request includes: Extracting process information of the business process from the execution request; Matching the process information with the process configuration information in the configuration library; In the case where the process information matches the process configuration information successfully, the process identifier corresponding to the successfully matched process configuration information in the configuration library is determined as the process identifier of the business process.

5. The method according to claim 4, characterized in that Also includes at least one of the following: If the process information and the process configuration information fail to match, extracting a process identifier and a node identifier from the process information; Registering the business process into the configuration library according to the process identifier and the node identifier; Determining whether the execution time of the business process exceeds the preset time indicated in the anomaly identification strategy; When the preset time period is exceeded, the target node is determined according to the currently acquired execution result and the abnormality identification expression.

6. The method according to claim 5, characterized in that Also includes: Determine, according to the process information, an exception identification expression corresponding to the business process; The exception identification expression and the process identifier are registered correspondingly in the configuration library.

7. The method according to claim 1, characterized in that The method is applied to an online family doctor consultation system, and the method comprises: Intercepting an execution request of a medical questionnaire creation process of the system, and determining a process identifier of the medical questionnaire creation process according to the execution request; During the execution of the medical consultation form creation process, the execution results of multiple nodes corresponding to the process identifier are obtained; the multiple nodes include saving user medical record information, checking the current fee payment status or whether membership services are available, and creating medical consultation cards.

8. An abnormality monitoring device, characterized in that: include: A request interception module, used to intercept an execution request of a business process and determine a process identifier of the business process according to the execution request; A result acquisition module, used to acquire the execution results of multiple nodes corresponding to the process identifier during the execution of the business process; An exception analysis module is used to determine the target node where the exception occurs among the multiple nodes based on the execution result and the exception identification expression, so as to perform exception processing on the target node; wherein the exception identification expression corresponds to the process identifier in the configuration library and is used to identify whether the node is abnormal.

9. An electronic device for abnormal monitoring, characterized in that: include: one or more processors; a storage device for storing one or more programs, When the one or more programs are executed by the one or more processors, the one or more processors implement the method according to any one of claims 1 to 8.

10. A computer readable medium having a computer program stored thereon, characterized in that: When the program is executed by a processor, the method according to any one of claims 1 to 8 is implemented.

Images