Business monitoring method, device, computer system and computer readable storage medium
By obtaining and analyzing business log information, dividing business nodes, and generating event information, general monitoring of complex business scenarios is achieved, and the problems of non-universal monitoring and lack of cross-system capabilities in the existing technology are solved, and monitoring efficiency and intuitiveness are improved.
Patent Information
- Application Number
- CN202110028631.4
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2021-01-08
- Publication Date
- 2024-12-06
- Estimated Expiration
- 2041-01-08
AI Technical Summary
The existing business monitoring solutions are not universal enough and are seriously customized, making it difficult to achieve effective monitoring in complex business scenarios, and lack cross-system monitoring capabilities and intuitiveness.
By obtaining the target log information and configuration information of the monitored business, dividing business nodes, generating business node event information, and monitoring based on this information, we realize general monitoring of complex business scenarios, using custom log components to collect log information, and building business Keyword index relationships are stored in the database, supporting cross-system business exception query and display.
It realizes general monitoring of complex business scenarios, decouples the monitoring process and business systems, provides cross-system business exception monitoring capabilities, improves problem-checking efficiency and intuitiveness, and reduces R&D costs.
Smart Images

Figure CN113760641B_ABST
Abstract
Description
Technical Field
[0001] The present disclosure relates to the field of computer technology, and more particularly, to a service monitoring method, a service monitoring device, a computer system, a computer-readable storage medium, and a computer program product. Background Art
[0002] With the rapid development of the Internet, microservices are becoming popular, and businesses are becoming complex and diverse. How to quickly detect and discover system business anomalies has become crucial.
[0003] In the process of implementing the concept of the present disclosure, the inventors found that there are at least the following problems in the relevant technology: the existing business monitoring implementation solutions are not universal enough, are heavily customized, and are not conducive to business anomaly monitoring in complex business scenarios. Summary of the Invention
[0004] In view of this, the present disclosure provides a service monitoring method, a service monitoring device, a computer system, a computer-readable storage medium, and a computer program product.
[0005] One aspect of the present disclosure provides a business monitoring method, comprising: obtaining target log information of at least one monitored interface in a monitored business, wherein the monitored business is divided into multiple business nodes and the multiple business nodes have an association relationship; obtaining configuration information of the monitored business, wherein the configuration information includes a mapping relationship between each of the business nodes and at least one monitored interface; determining a target business node corresponding to the target log information based on the configuration information; generating business node event information based on the target log information and the target business node; and monitoring the monitored business based on the business node event information.
[0006] According to an embodiment of the present disclosure, the above-mentioned business monitoring method also includes: obtaining an access operation for connecting the business of different systems to the business monitoring platform; and in response to the access operation, inputting the application instance information of the business of the different systems into the business monitoring platform so as to connect the business of the different systems to the business monitoring platform.
[0007] According to an embodiment of the present disclosure, the above-mentioned business monitoring method further includes: dividing and arranging business nodes of the business processes of the different systems according to the business scenarios of the different systems.
[0008] According to an embodiment of the present disclosure, obtaining target log information of at least one monitored interface in a monitored business includes: collecting log information according to a custom log component used to collect log information of the monitored business; when the log information belongs to a preset log level, determining whether the log information is the log information corresponding to the monitored interface; and using the log information corresponding to the monitored interface as the target log information.
[0009] According to an embodiment of the present disclosure, monitoring the monitored business based on the business node event information includes: obtaining the target business node and the target execution status of the target business node in the business node event information, wherein the target execution status includes success and exception; when the target execution status is success, determining that the target business node is displayed with a first display effect; when the target execution status is abnormal, determining that the target business node is displayed with a second display effect.
[0010] According to an embodiment of the present disclosure, the above-mentioned business monitoring method also includes: obtaining business keywords related to the monitored business; constructing an index relationship between the business keywords and the business node event information; and storing the index relationship in a database so as to query the execution status information of the monitored business based on the business keywords.
[0011] According to an embodiment of the present disclosure, the above-mentioned service monitoring method further includes: determining service identification information or associated information according to the service keyword; and querying execution status information of the monitored service according to the service identification information or associated information.
[0012] Another aspect of the present disclosure provides a business monitoring device, including: a first acquisition module, used to obtain target log information of at least one monitored interface in a monitored business, wherein the monitored business is divided into multiple business nodes, and the multiple business nodes have an association relationship; a second acquisition module, used to obtain configuration information of the monitored business, wherein the configuration information includes a mapping relationship between each of the business nodes and at least one monitored interface; a determination module, used to determine the target business node corresponding to the target log information based on the configuration information; a generation module, used to generate business node event information based on the target log information and the target business node; and a monitoring module, used to monitor the monitored business based on the business node event information.
[0013] Another aspect of the present disclosure provides a computer system comprising: one or more processors; and a memory for storing one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors implement the business monitoring method described above.
[0014] Another aspect of the present disclosure provides a computer-readable storage medium having computer-executable instructions stored thereon, which are used to implement the service monitoring method described above when the instructions are executed.
[0015] Another aspect of the present disclosure provides a computer program product, which includes computer-executable instructions. When the instructions are executed, the computer program product is used to implement the service monitoring method described above.
[0016] According to an embodiment of the present disclosure, by adopting the following technical means: obtaining target log information of at least one monitored interface in a monitored business, wherein the monitored business is divided into multiple business nodes, and the multiple business nodes have an association relationship; obtaining configuration information of the monitored business, wherein the configuration information includes a mapping relationship between each business node and at least one monitored interface; determining a target business node corresponding to the target log information based on the configuration information; generating business node event information based on the target log information and the target business node; and monitoring the monitored business based on the business node event information. Since the monitored business is monitored through log information and business nodes, the technical problem that the existing business monitoring is not universal enough is at least partially overcome, thereby realizing a universal business monitoring method and achieving the technical effect of being able to monitor various complex business scenarios. BRIEF DESCRIPTION OF THE DRAWINGS
[0017] The above and other objects, features and advantages of the present disclosure will become more apparent through the following description of the embodiments of the present disclosure with reference to the accompanying drawings, in which:
[0018] Figure 1 Schematically illustrates an exemplary system architecture to which a service monitoring method according to an embodiment of the present disclosure can be applied;
[0019] Figure 2 The following schematically shows a flow chart of a service monitoring method according to an embodiment of the present disclosure;
[0020] Figure 3 The following schematically shows an application access flow chart according to an embodiment of the present disclosure;
[0021] Figure 4 The following schematically shows a flow chart of business abnormality data collection according to an embodiment of the present disclosure;
[0022] Figure 5The following schematically shows a flow chart of receiving abnormal service data according to an embodiment of the present disclosure;
[0023] Figure 6 Schematically shows the overall design diagram of a business monitoring platform constructed according to the business monitoring method of an embodiment of the present disclosure;
[0024] Figure 7 The following schematically shows a flowchart of a business exception query according to an embodiment of the present disclosure;
[0025] Figure 8 Schematically shows a business anomaly display diagram according to an embodiment of the present disclosure;
[0026] Figure 9 Schematically shows a diagram showing detailed information of business anomalies according to an embodiment of the present disclosure;
[0027] Figure 10 A block diagram schematically illustrates a service monitoring device according to an embodiment of the present disclosure; and
[0028] Figure 11 The block diagram schematically shows a computer system suitable for implementing the service monitoring method according to an embodiment of the present disclosure. DETAILED DESCRIPTION
[0029] Hereinafter, embodiments of the present disclosure will be described with reference to the accompanying drawings. However, it should be understood that these descriptions are merely exemplary and are not intended to limit the scope of the present disclosure. In the detailed description below, for ease of explanation, many specific details are set forth to provide a comprehensive understanding of the embodiments of the present disclosure. However, it is apparent that one or more embodiments may also be implemented without these specific details. In addition, in the following description, descriptions of well-known structures and technologies are omitted to avoid unnecessary confusion of the concepts of the present disclosure.
[0030] The terms used herein are only for describing specific embodiments and are not intended to limit the present disclosure. The terms "comprise," "include," etc. used herein indicate the presence of the features, steps, operations, and / or components, but do not exclude the presence or addition of one or more other features, steps, operations, or components.
[0031] All terms used herein (including technical and scientific terms) have the meanings commonly understood by those skilled in the art unless otherwise defined. It should be noted that the terms used herein should be interpreted as having a meaning consistent with the context of this specification and should not be interpreted in an idealized or overly rigid manner.
[0032] When expressions such as “at least one of A, B, and C, etc.” are used, they should generally be interpreted in accordance with the meaning commonly understood by those skilled in the art (e.g., “a system having at least one of A, B, and C” should include but is not limited to systems having A alone, B alone, C alone, A and B, A and C, B and C, and / or A, B, and C, etc.). When expressions such as “at least one of A, B, or C, etc.” are used, they should generally be interpreted in accordance with the meaning commonly understood by those skilled in the art (e.g., “a system having at least one of A, B, or C” should include but is not limited to systems having A alone, B alone, C alone, A and B, A and C, B and C, and / or A, B, and C, etc.).
[0033] Currently, there are many different business monitoring systems, but the internal implementation solutions are roughly the same. For example, each business system implements a separate business monitoring system based on its own business characteristics, evaluates the required monitoring points, and collects abnormal data or business alarms in the core business modules; or implements a general business monitoring platform and provides corresponding data collection APIs for business systems to access. After receiving the abnormal alarm, relevant personnel confirm the business module to which the abnormality belongs and coordinate multiple related systems to investigate the abnormality.
[0034] In the process of realizing the concept disclosed herein, the inventors discovered that the existing business monitoring implementation solutions have the following main deficiencies: they are not general enough, are highly customized, and are heavily coupled with specific businesses. Each business system needs to implement its own business monitoring system, which increases R&D and maintenance costs; the application access code is highly invasive, especially for old systems, which require many changes and pose greater risks; business anomalies between business systems are disconnected, making cross-system business monitoring impossible; there is a lack of an overall business process perspective, which is not intuitive enough and is not convenient for non-R&D users to troubleshoot problems.
[0035] Embodiments of the present disclosure provide a service monitoring method, service monitoring device, computer system, computer-readable storage medium, and computer program product. The method includes obtaining target log information of at least one monitored interface in a monitored service, wherein the monitored service is divided into multiple service nodes, and the multiple service nodes have an association relationship; obtaining configuration information of the monitored service, wherein the configuration information includes a mapping relationship between each service node and at least one monitored interface; determining a target service node corresponding to the target log information based on the configuration information; generating service node event information based on the target log information and the target service node; and monitoring the monitored service based on the service node event information.
[0036] Figure 1The exemplary system architecture 100 to which the business monitoring method according to an embodiment of the present disclosure can be applied is schematically shown. It should be noted that, Figure 1 The examples shown are merely examples of system architectures to which the embodiments of the present disclosure may be applied, to help those skilled in the art understand the technical content of the present disclosure, but do not mean that the embodiments of the present disclosure may not be used in other devices, systems, environments or scenarios.
[0037] like Figure 1 As shown, the system architecture 100 according to this embodiment may include terminal devices 101, 102, 103, a network 104, and a server 105. The network 104 is used as a medium for providing communication links between the terminal devices 101, 102, 103 and the server 105. The network 104 may include various connection types, such as wired and / or wireless communication links, etc.
[0038] Users can use terminal devices 101, 102, and 103 to interact with server 105 via network 104 to receive or send messages, etc. Various communication client applications can be installed on terminal devices 101, 102, and 103, such as shopping applications, web browser applications, search applications, instant messaging tools, email clients, and / or social platform software.
[0039] The terminal devices 101 , 102 , and 103 may be various electronic devices having a display screen and supporting web browsing, including but not limited to smart phones, tablet computers, laptop computers, and desktop computers.
[0040] The server 105 may be a server that provides various services, such as a background management server that supports websites browsed by users using the terminal devices 101, 102, and 103. The background management server may analyze and process received data such as user requests, and feed back processing results (e.g., web pages, information, or data obtained or generated based on user requests) to the terminal device.
[0041] It should be noted that the service monitoring method provided in the embodiment of the present disclosure can generally be executed by the server 105. Accordingly, the service monitoring device provided in the embodiment of the present disclosure can generally be set in the server 105. The service monitoring method provided in the embodiment of the present disclosure can also be executed by a server or server cluster that is different from the server 105 and can communicate with the terminal devices 101, 102, 103 and / or the server 105. Accordingly, the service monitoring device provided in the embodiment of the present disclosure can also be set in a server or server cluster that is different from the server 105 and can communicate with the terminal devices 101, 102, 103 and / or the server 105. Alternatively, the service monitoring method provided in the embodiment of the present disclosure can also be executed by the terminal devices 101, 102, or 103, or can also be executed by other terminal devices different from the terminal devices 101, 102, or 103. Accordingly, the service monitoring device provided in the embodiment of the present disclosure can also be set in the terminal devices 101, 102, or 103, or can be set in other terminal devices different from the terminal devices 101, 102, or 103.
[0042] For example, the monitored service may be originally stored in any one of the terminal devices 101, 102, or 103 (for example, the terminal device 101, but not limited thereto), or stored on at least one external storage device and imported into the terminal device 101. The terminal device 101 may then locally execute the service monitoring method provided by the embodiment of the present disclosure, or send the monitored service to other terminal devices, servers, or server clusters, and the other terminal devices, servers, or server clusters that receive the monitored service may execute the service monitoring method provided by the embodiment of the present disclosure.
[0043] It should be understood that Figure 1 The number of terminal devices, networks and servers in the embodiment is merely illustrative. Any number of terminal devices, networks and servers may be provided as required.
[0044] Figure 2 The flowchart of the service monitoring method according to the embodiment of the present disclosure is schematically shown.
[0045] like Figure 2 As shown, the method includes operations S201 to S205.
[0046] In operation S201 , target log information of at least one monitored interface in a monitored service is obtained, wherein the monitored service is divided into a plurality of service nodes, and the plurality of service nodes are associated with each other.
[0047] According to an embodiment of the present disclosure, the above-mentioned monitored business may, for example, include businesses with various complex business processes, wherein the business process is, for example, a series of activities completed jointly by different business function modules in order to realize a specific business, and there is a certain sequence between the activities. The above-mentioned monitored interface may, for example, be an interface method that needs to be monitored in the monitored business. The above-mentioned business nodes may, for example, be business nodes obtained by dividing the entire business process according to business function modules, and the association relationship between the nodes may, for example, be determined by the logical relationship between the business function modules in the business process. The above-mentioned business nodes may also, for example, be business nodes obtained by dividing the entire business process according to activity type, and the association relationship between the nodes may, for example, be determined by the sequence of activities in the business process.
[0048] In operation S202, configuration information of the monitored service is acquired, where the configuration information includes a mapping relationship between each service node and at least one monitored interface.
[0049] According to the embodiments of the present disclosure, business nodes can be obtained by dividing them according to business function modules or activity types. Since each business function module or business activity can include one or more interface methods, one or more interface methods (i.e., the above-mentioned monitored interfaces) can be monitored through a business node. By configuring business node information for the interface method to be monitored (for example, it may include information such as the interface method, the business node to which it belongs, and the business function description), the association between the node and the actual business scenario (such as the monitored interface in the business) is realized, so that a mapping relationship between the business node and the interface method to be monitored can be established, and the above-mentioned configuration information can be obtained, providing a basis for the implementation of subsequent business monitoring.
[0050] In operation S203 , a target service node corresponding to the target log information is determined according to the configuration information.
[0051] According to an embodiment of the present disclosure, since the target log information may be log information for the monitored interface, the business node corresponding to the target log information of the corresponding monitored interface, that is, the above-mentioned target business node, can be determined based on the mapping relationship between the business node and the monitored interface in the configuration information.
[0052] In operation S204 , service node event information is generated according to the target log information and the target service node.
[0053] According to an embodiment of the present disclosure, the above-mentioned business node event information may be, for example, information corresponding to a node event generated by a business node during a business process processing, wherein the node event may include, for example, an abnormal event, a success event, etc. The business node event information may include, for example, business-related information, information in the log, and information about the node itself. The format of the business node event information may be, for example:
[0054] NodeEvent#{"domainId": business domain id, "appId": application id, "sceneId": process id, "nodeId": business node id, "flowChartId": flow chart id, "executeStatus": execution status, "bizId": "business id", "content": "exception information", "params": "input parameters", "result": "output parameters", "associateKey": "association key", "createTime": "creation time", "modifyTime": "modification time"}
[0055] Among them, the application id is, for example, the id (identifier) corresponding to the application to which the business node belongs, the process id is, for example, the id corresponding to the business process to which the business node belongs, the business node id is, for example, the id corresponding to the corresponding business node, the flowchart id is, for example, the id corresponding to the business process node orchestration diagram, the execution status is, for example, the execution status of the corresponding business node, which may include exception, success, unexecuted and other states, the business id is, for example, the business keyword associated with the business process, which is used for subsequent queries and searches, and the association key can be, for example, the unique association key for a business request, which is used to connect multiple business systems in series.
[0056] In operation S205 , the monitored service is monitored according to the service node event information.
[0057] According to the embodiments of the present disclosure, the processing details of each service node can be monitored according to the detailed content in the service node event information, thereby monitoring the processing flow of the entire monitored service.
[0058] Through the above-mentioned embodiments of the present disclosure, since the business system is divided into multiple business nodes, and business node event information is constructed by collecting logs, each business node in the business system can be monitored. The monitoring method does not need to invade the business system, thereby achieving decoupling of the monitoring process and the business system, and can be further applied to various complex business scenarios to realize business anomaly monitoring in various business scenarios.
[0059] Reference below Figures 3 to 9 , combined with specific embodiments Figure 2 The method shown is further explained.
[0060] Figure 3 The following schematically shows an application access flow chart according to an embodiment of the present disclosure.
[0061] like Figure 3 As shown, it shows the operations before performing the above-mentioned business monitoring method, including operations S301 to S302.
[0062] In operation S301, the business system is connected.
[0063] It should be noted that the monitored services may be services from multiple different systems. To ensure the accuracy of service monitoring, it is necessary to monitor the multiple systems simultaneously.
[0064] According to the embodiments of the present disclosure, the system that needs to perform business monitoring must first access the application through the business monitoring platform management terminal and enter relevant application information, such as: appId, token (an identifier used to identify the accessible application demonstration), and information such as the business domain to which it belongs.
[0065] To achieve the above purpose, the operation S301 may, for example, include: obtaining an access operation for connecting the services of different systems to the business monitoring platform; and in response to the access operation, inputting the application instance information of the services of different systems into the business monitoring platform so as to connect the services of different systems to the business monitoring platform.
[0066] In operation S302 , business process orchestration is performed.
[0067] According to an embodiment of the present disclosure, after the business accesses the business monitoring platform, the business scenario is drawn to realize the orchestration of the business process. The orchestration may, for example, include node division of the business process and orchestration of multiple business nodes involved in the business process according to dependency relationships.
[0068] To achieve the above-mentioned purpose, the operation S302 may, for example, include: determining the node division method and orchestration method for the business scenario according to the business scenarios of different systems; obtaining a division operation for dividing the business scenario into business nodes, wherein the division operation may, for example, include a node creation operation input by a user; obtaining an orchestration operation for implementing the orchestration of dependencies between business nodes, wherein the orchestration operation may, for example, include a connection operation between certain nodes determined by a user input based on dependencies between nodes; and in response to the division operation and the orchestration operation, the business node division and orchestration of the business processes of the businesses of different systems can be implemented in the business monitoring platform.
[0069] Through the above-mentioned embodiments of the present disclosure, since the business process node method is adopted, all business processes that need to be monitored can be divided according to business nodes, and the obtained business nodes are respectively attributed to each business system. Through process orchestration, the entire business system is connected in series, and business anomalies can be displayed from the perspective of the overall process, realizing the visualization and intuitiveness of business anomalies and the ability to perform business monitoring across systems.
[0070] According to an embodiment of the present disclosure, after the application accesses the business monitoring platform, the above-mentioned operation S201 may, for example, include: collecting log information according to a custom log component used to collect log information of the monitored business; when the log information belongs to a preset log level, determining whether the log information is the log information corresponding to the monitored interface; and using the log information corresponding to the monitored interface as the target log information.
[0071] Figure 4 The flowchart of business abnormality data collection according to an embodiment of the present disclosure is schematically shown.
[0072] like Figure 4 As shown, it shows the specific implementation process of the above operation S201, including operations S401 to S408.
[0073] It should be noted that, in order to support the method corresponding to the above operation S201, this method also introduces a log collection client to realize the collection of the above target log information.
[0074] In operation S401, a log component type logback / log4j is automatically located, where logback and log4j belong to different types of log components.
[0075] In operation S402, a custom log Appender is created. Appender, as a core subcomponent in the log component, can define the destination for outputting log information.
[0076] In operation S403, the existing Logger of the application is scanned and a custom Appender is added. As another core subcomponent in the log component, the Logger is responsible for generating logs and can classify and filter log information.
[0077] In operation S404, the service log is printed.
[0078] According to an embodiment of the present disclosure, an application may output log information of different levels (for example, debug, info, warn, Error, Fatal, etc.) according to an existing log printing method without any modification.
[0079] In operation S405 , the Appender log interception is customized.
[0080] According to an embodiment of the present disclosure, for the above operations S401 to S405, due to the different applications connected, the log components used during log collection may also be different. Therefore, after the application is started, the log collection client will first automatically locate the log component (logback / log4j) used by the application and create a custom log Appender for log collection. At the same time, it will scan the existing Logger of the application and append the custom Appender. All subsequent Logger log prints will be output to the custom Appender to implement log interception. After the custom Appender intercepts the log information, for example, the intercepted log information can be filtered through the following operations S406 to S407 to obtain the required target log information.
[0081] In operation S406 , whether a log level is specified, such as Error.
[0082] According to an embodiment of the present disclosure, if the result of the judgment of this operation is no, that is, the intercepted log information is not of the specified log level, the log information is filtered and not collected. If the result of the judgment of this operation is yes, that is, the intercepted log information is of the specified log level, it is necessary to further determine whether the log information is configured with the corresponding service node information, that is, operation S407.
[0083] In operation S407, whether service node information is configured.
[0084] According to an embodiment of the present disclosure, if the result of this operation is negative, that is, the intercepted log information is not configured with corresponding business node information, then the log information is also filtered and not collected. If the result of this operation is positive, that is, the intercepted log information is configured with corresponding business node information, then the corresponding business node event information can be constructed based on the above configuration information.
[0085] In operation S408, a service exception event is constructed and sent to MQ (Message Queue).
[0086] According to an embodiment of the present disclosure, the abnormal business event is, for example, a part of the above-mentioned business node event information, and the information can be reported to the business monitoring platform by sending MQ, for example.
[0087] Through the above-mentioned embodiments of the present disclosure, a custom log Appender is adopted and appended to the existing Logger of the application for log interception and reporting, thereby realizing a solution for non-invasive log interception, business exception collection and automatic reporting, further solving the problem that traditional business exception monitoring is not universal, and can be applied to various complex business scenarios.
[0088] It should be noted that the above-mentioned non-invasive log interception can also be achieved through bytecode modification technology. The difference is that the bytecode modification technology requires modifying the log printing bytecode, adding new log interception code, and printing error logs by adding annotations. The annotations can include the node ID associated with the corresponding log information.
[0089] Figure 5 The flowchart of receiving abnormal business data according to an embodiment of the present disclosure is schematically shown.
[0090] like Figure 5 As shown, a series of operations after the business monitoring platform receives the business node event information are shown, including operations S501 to S506.
[0091] In operation S501 , a service abnormality event is received.
[0092] In operation S502 , the business abnormality event is analyzed.
[0093] In operation S503, it is determined whether to generate an alarm.
[0094] According to embodiments of the present disclosure, this operation is determined based on business configuration. For example, if the business configuration specifies that certain abnormal events do not require business alerts, then even if these events are monitored, no alert will be triggered. Conversely, an alert will be triggered. Based on this rule, business process monitoring can be customized.
[0095] In operation S504, the service monitoring alarm is generated.
[0096] According to an embodiment of the present disclosure, this operation is implemented if the result of operation S503 is yes.
[0097] In operation S505 , the business keyword storage index relationship is parsed.
[0098] According to an embodiment of the present disclosure, for example, the business keyword can be obtained by parsing the business ID in the business node event information, and the index relationship between the business keyword and its corresponding business node event record (that is, the event details corresponding to the business keyword) can be constructed through the word segmentation algorithm in ES (Elasticsearch, a non-relational database). The index relationship can eventually be persistently stored in ES for subsequent business process status queries.
[0099] It should be noted that the service node event record may be, for example, the service node event information described above, or may be more detailed information further obtained based on the service node event information described above.
[0100] In operation S506 , a service node exception record is constructed and persisted to HBase.
[0101] According to an embodiment of the present disclosure, the business node exception record can be obtained based on the above-mentioned business node event record, for example. By binding the business node exception record to the corresponding business node and then persistently storing it in HBase, detailed queryable information can be provided for abnormal events in subsequent business process status queries.
[0102] It should be noted that the business node event records can also be bound to the corresponding business node and persistently stored in HBase, so that each event can provide queryable detailed information during subsequent business process status queries. The storage of the business node event records can also be replaced by a database or other storage service, which is not limited here.
[0103] According to the above-mentioned embodiment of the present disclosure, by binding the business node event record to the business node and persistently storing the business node event record in HBase, the purpose of monitoring the monitored business according to the business node event information in the above-mentioned operation S205 can be easily achieved. On this basis, the operation S205 can also include, for example: obtaining the target business node and the target execution status of the target business node in the business node event information, wherein the target execution status includes success and exception; when the target execution status is successful, determining that the target business node is displayed with a first display effect; when the target execution status is abnormal, determining that the target business node is displayed with a second display effect.
[0104] According to an embodiment of the present disclosure, the above-mentioned target execution status may also only include exceptions. In this case, if there is a business node in a business process whose corresponding execution status is abnormal, the business node will be displayed with the second display effect, and the execution status of the business node before the business node can be directly determined to be successful, so that the business node before the business node is displayed with the first display effect. At the same time, the business node after the business node can also be directly determined to be in an unexecuted state, and the business node after the business node can be displayed with the third display effect.
[0105] It should be noted that the first, second and third display effects can be distinguished by color (for example, green, red, gray, etc.), or by other rendering animations, which are not limited here.
[0106] Through the above-mentioned embodiments of the present disclosure, since business abnormality events are bound to business nodes, business abnormality data can be reported to the designated business nodes, and the business node status source can also correspond to the business abnormality events. By combining the orchestration operation of the aforementioned business nodes and designing business nodes with different color labels according to their status, the business nodes where the business process is stuck can be visually displayed, thereby achieving the purpose of more intuitively displaying business monitoring results.
[0107] In combination with the above embodiments of the present disclosure, Figure 6 The overall design diagram of the business monitoring platform constructed according to the business monitoring method of the embodiment of the present disclosure is schematically shown.
[0108] like Figure 6 As shown, the business monitoring platform may include, for example, a business monitoring management terminal, a business monitoring engine, and a log collection client. Among them, the business monitoring management terminal implements the application access to the system that needs to be business monitored and the business node division and orchestration of the business process that needs to be monitored; the log collection client may be introduced by each application instance of the business system, and by configuring the corresponding business node information for the interface method that needs to be collected, the log collection client may automatically start intercepting business exception logs and reporting to the message middleware after the application is started; the business monitoring engine may store the relevant application information (such as the above-mentioned appId, token, and the business domain information) entered during the application access process in a database (such as Mysql), and may also monitor and receive business exception events of the message middleware, and may parse the business exception events to further implement business alarms and analysis storage, for example, it may include implementing the above-mentioned Figure 5 The related operations in the embodiment described above can also search for keywords during the query process to query business abnormality data.
[0109] according to Figure 6 In the illustrated embodiment, a user (business, product, or R&D) can log in to the business monitoring platform and query the execution status of the corresponding business process based on business keywords or other business-related information to determine whether an abnormality occurs in the business process.
[0110] According to one embodiment of the present disclosure, for example, relevant queries can be performed based on business keywords. The process may include, for example: obtaining business keywords related to the monitored business; constructing an index relationship between the business keywords and business node event information; and storing the index relationship in a database so as to query the execution status information of the monitored business based on the business keywords.
[0111] According to another embodiment of the present disclosure, for example, related queries can also be performed based on other relevant information of the business. The process may include, for example: determining business identification information or associated information based on business keywords; and querying the execution status information of the monitored business based on the business identification information or associated information.
[0112] Figure 7 The following schematically shows a flowchart of a business anomaly query according to an embodiment of the present disclosure.
[0113] like Figure 7 As shown, for example, it can be a process of business anomaly query based on the above-mentioned business monitoring platform or based on the above-mentioned business monitoring method, including operations S701 to S705.
[0114] In operation S701 , a business domain and a business process are selected.
[0115] In operation S702 , the selected business process diagram is acquired.
[0116] According to an embodiment of the present disclosure, a unique business process node orchestration diagram can be determined through the business domain and the business process, that is, a unique business process diagram can be determined.
[0117] In operation S703 , a service keyword is input to query the service id / traceid.
[0118] According to an embodiment of the present disclosure, the business keyword can be, for example, a keyword extracted from business exception information, log information, or business node event information, and the business id and traceid (i.e., the above-mentioned association key) corresponding to the keyword can be queried through the business keyword.
[0119] In operation S704, the ES is queried according to the keyword to obtain the service node Rowkey.
[0120] According to an embodiment of the present disclosure, the above-mentioned business node Rowkey is, for example, primary key information of the business node corresponding to the corresponding keyword queried based on the index relationship between the keyword and the business node event record stored in the ES.
[0121] In operation S705 , abnormal data of each service node is queried according to the service node Rowkey.
[0122] According to an embodiment of the present disclosure, detailed records of corresponding business nodes can be queried from HBase based on the above-mentioned business node Rowkey, thereby obtaining detailed abnormal data of the abnormal business node.
[0123] Figure 8 A business anomaly display diagram according to an embodiment of the present disclosure is schematically shown.
[0124] according to Figure 8 In the embodiment shown, for the above operation S701, after the user selects the business domain (e.g., corresponding to the above business domain id) as overseas transactions and the monitoring scenario (i.e., the business process to be monitored, e.g., corresponding to the above process id) as the EPT order process in Indonesia, the business monitoring engine can determine based on this the business process diagram (e.g., corresponding to the above process diagram id) obtained in the above operation S702, for example, Figure 8 A business process diagram that shows the structure of business nodes and relationships between nodes.
[0125] Next, the user can further enter the business keyword to query the process status. In combination with the above embodiment, the user can first query the business keyword to obtain the corresponding business id and traceid, and then obtain the event information corresponding to each business node in the business process diagram based on the business id or traceid. By displaying the business node in different colors according to the type of event information of each business node, the user can query and obtain the specific business monitoring results including the execution status of each business node. For example, the user can Figure 8 Enter the business ID in the business code, or Figure 8 Enter the traceid in the associated key. Since both the business id and the traceid correspond to specific business processes, the business monitoring results corresponding to the above business keywords can be obtained.
[0126] like Figure 8 The process display result is the monitoring result of the business with business code 1025780305 in the EPT order process of Indonesia for overseas transactions. Figure 8 In the example, the "Accept Order Request" node is displayed in green, the "Place EPT Order" node is displayed in red, and the remaining nodes are displayed in gray. The user can analyze that the events corresponding to the "Accept Order Request" node have all been successfully executed, but an exception occurred when the business reached the "Place EPT Order" node, causing the business process to be unable to proceed and the remaining nodes to fail to be executed.
[0127] By clicking Figure 8 You can further view the detailed execution information of each business node by clicking on the corresponding business node. Figure 8 In the "Place EPT Order" node, you can view the detailed abnormal information corresponding to the node, such as Figure 9 shown.
[0128] Figure 9 A diagram schematically illustrates detailed information display of business anomalies according to an embodiment of the present disclosure.
[0129] like Figure 9As shown, by clicking the View Log button on the right, you can further view the input and output parameter information of the method where the business exception occurs, so as to further determine the cause of the exception and facilitate exception troubleshooting.
[0130] Through the above-mentioned embodiments of the present disclosure, the problems of business anomaly monitoring in complex business scenarios being non-universal, non-intuitive, and lacking cross-system monitoring capabilities have been solved. On the one hand, application access is simple, and it can be non-invasive when collecting anomalies. At the same time, without modifying the existing application code, a log interception solution can be introduced to collect business anomaly logs, thereby decoupling the monitoring system from the business system and solving the problem of non-universality. On the other hand, complex business scenarios are divided and orchestrated according to business nodes, and business anomaly events are bound to business nodes. Business nodes can use different color labels according to event status to achieve visual presentation of business process execution status, which can effectively assist in product and business problem troubleshooting, improve problem troubleshooting efficiency, release R&D resources, and achieve visualization and intuition of business anomalies. On the other hand, by nodeizing business processes, business nodes are respectively assigned to each business system, connecting the entire business system in series, and displaying business anomalies from the perspective of the overall process, thus achieving the ability to monitor business across systems.
[0131] Figure 10 The block diagram of the service monitoring device according to the embodiment of the present disclosure is schematically shown.
[0132] like Figure 10 As shown, the service monitoring device 1000 includes a first acquisition module 1010 , a second acquisition module 1020 , a first determination module 1030 , a generation module 1040 and a monitoring module 1050 .
[0133] A first acquisition module 1010 is configured to acquire target log information of at least one monitored interface in a monitored service, wherein the monitored service is divided into a plurality of service nodes, and the plurality of service nodes are associated with each other;
[0134] A second acquisition module 1020 is configured to acquire configuration information of the monitored service, wherein the configuration information includes a mapping relationship between each service node and at least one monitored interface;
[0135] A first determining module 1030 is configured to determine a target service node corresponding to the target log information according to the configuration information;
[0136] A generating module 1040 is configured to generate service node event information according to target log information and target service node; and
[0137] The monitoring module 1050 is configured to monitor the monitored service according to the service node event information.
[0138] According to an embodiment of the present disclosure, the above-mentioned service monitoring device further includes a third acquisition module and an access module.
[0139] The third acquisition module is used to acquire an access operation for accessing services of different systems to the service monitoring platform.
[0140] The access module is used to input application instance information of services of different systems into the service monitoring platform in response to the access operation, so as to access the services of different systems to the service monitoring platform.
[0141] According to an embodiment of the present disclosure, the above-mentioned service monitoring device further includes an orchestration module.
[0142] The orchestration module is used to divide and orchestrate the business nodes of the business processes of different systems according to the business scenarios of different systems.
[0143] According to an embodiment of the present disclosure, the first acquisition module includes a collection unit, a judgment unit and a definition unit.
[0144] The collection unit is used to collect log information according to the custom log component used to collect log information of the monitored business.
[0145] The judging unit is used to judge whether the log information is the log information corresponding to the monitored interface when the log information belongs to the preset log level.
[0146] The definition unit is used to use the log information corresponding to the monitored interface as the target log information.
[0147] According to an embodiment of the present disclosure, the monitoring module includes an acquiring unit, a first determining unit and a second determining unit.
[0148] The acquiring unit is configured to acquire the target service node and the target execution status of the target service node in the service node event information, wherein the target execution status includes success and exception.
[0149] The first determining unit is configured to determine, when the target execution status is success, that the target service node is displayed with a first display effect.
[0150] The second determining unit is configured to determine, when the target execution state is abnormal, that the target service node is displayed with a second display effect.
[0151] According to an embodiment of the present disclosure, the above-mentioned service monitoring device further includes a fourth acquisition module, a construction module and a first query module.
[0152] The fourth acquisition module is used to acquire business keywords related to the monitored business.
[0153] The construction module is used to construct the index relationship between business keywords and business node event information.
[0154] The first query module is used to store the index relationship in the database so as to query the execution status information of the monitored business according to the business keyword.
[0155] According to an embodiment of the present disclosure, the above-mentioned service monitoring device further includes a second determination module and a second query module.
[0156] The second determining module is used to determine the service identification information or associated information according to the service keyword.
[0157] The second query module is used to query the execution status information of the monitored service according to the service identification information or the associated information.
[0158] According to the modules and units of the embodiments of the present invention, any multiple or at least part of the functions of any multiple thereof can be implemented in one module. According to the modules and units of the embodiments of the present invention, any one or more can be split into multiple modules for implementation. According to the modules and units of the embodiments of the present invention, any one or more can be at least partially implemented as a hardware circuit, such as a field programmable gate array (FPGA), a programmable logic array (PLA), a system on a chip, a system on a substrate, a system on a package, an application specific integrated circuit (ASIC), or can be implemented by hardware or firmware of any other reasonable way of integrating or packaging the circuit, or implemented in any one of the three implementation methods of software, hardware and firmware or in an appropriate combination of any several thereof. Alternatively, according to the modules and units of the embodiments of the present invention, one or more can be at least partially implemented as a computer program module, which can perform the corresponding function when the computer program module is run.
[0159] For example, any of the first acquisition module 1010, the second acquisition module 1020, the first determination module 1030, the generation module 1040, and the monitoring module 1050 can be combined into one module / unit for implementation, or any of the modules / units can be split into multiple modules / units. Alternatively, at least part of the functionality of one or more of these modules / units can be combined with at least part of the functionality of other modules / units and implemented in one module / unit. According to an embodiment of the present disclosure, at least one of the first acquisition module 1010, the second acquisition module 1020, the first determination module 1030, the generation module 1040, and the monitoring module 1050 can be at least partially implemented as a hardware circuit, such as a field programmable gate array (FPGA), a programmable logic array (PLA), a system on a chip, a system on a substrate, a system on a package, an application specific integrated circuit (ASIC), or can be implemented by hardware or firmware in any other reasonable manner of integrating or packaging the circuit, or implemented in any one of the three implementation modes of software, hardware, and firmware, or in an appropriate combination of any of them. Alternatively, at least one of the first acquisition module 1010 , the second acquisition module 1020 , the first determination module 1030 , the generation module 1040 and the monitoring module 1050 may be at least partially implemented as a computer program module, which may perform corresponding functions when executed.
[0160] It should be noted that the service monitoring device part in the embodiment of the present disclosure corresponds to the service monitoring method part in the embodiment of the present disclosure. The description of the service monitoring device part specifically refers to the service monitoring method part and will not be repeated here.
[0161] Figure 11 The block diagram schematically shows a computer system suitable for implementing the service monitoring method according to an embodiment of the present disclosure. Figure 11 The computer system shown is only an example and should not limit the functions and scope of use of the embodiments of the present disclosure.
[0162] like Figure 11As shown, the computer system 1100 according to an embodiment of the present disclosure includes a processor 1101, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 1102 or a program loaded from a storage part 1108 into a random access memory (RAM) 1103. The processor 1101 may include, for example, a general-purpose microprocessor (e.g., a CPU), an instruction set processor and / or a related chipset and / or a special-purpose microprocessor (e.g., an application-specific integrated circuit (ASIC)), etc. The processor 1101 may also include an onboard memory for caching purposes. The processor 1101 may include a single processing unit or multiple processing units for executing different actions of the method flow according to an embodiment of the present disclosure.
[0163] Various programs and data required for the operation of system 1100 are stored in RAM 1103. Processor 1101, ROM 1102, and RAM 1103 are connected to each other via bus 1104. Processor 1101 executes the various operations of the method flow according to the embodiment of the present disclosure by executing the programs in ROM 1102 and / or RAM 1103. It should be noted that the programs may also be stored in one or more memories other than ROM 1102 and RAM 1103. Processor 1101 may also execute the various operations of the method flow according to the embodiment of the present disclosure by executing the programs stored in the one or more memories.
[0164] According to an embodiment of the present disclosure, system 1100 may further include an input / output (I / O) interface 1105, which is also connected to bus 1104. System 1100 may also include one or more of the following components connected to I / O interface 1105: an input section 1106 including a keyboard, mouse, etc.; an output section 1107 including devices such as a cathode ray tube (CRT), a liquid crystal display (LCD), and speakers; a storage section 1108 including a hard disk; and a communication section 1109 including a network interface card such as a LAN card or a modem. Communication section 1109 performs communication processing via a network such as the Internet. Drive 1110 is also connected to I / O interface 1105 as needed. Removable media 1111, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed in drive 1110 as needed, so that computer programs read from the removable media can be installed into storage section 1108 as needed.
[0165] According to an embodiment of the present disclosure, the method flow according to an embodiment of the present disclosure can be implemented as a computer software program. For example, an embodiment of the present disclosure includes a computer program product, which includes a computer program carried on a computer-readable storage 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 1109, and / or installed from the removable medium 1111. When the computer program is executed by the processor 1101, the above-mentioned functions defined in the system of the embodiment of the present disclosure are executed. According to an embodiment of the present disclosure, the system, equipment, device, module, unit, etc. described above can be implemented by a computer program module.
[0166] The present disclosure also provides a computer-readable storage medium, which may be included in the device / apparatus / system described in the above embodiments, or may exist independently and not be incorporated into the device / apparatus / system. The computer-readable storage medium carries one or more programs, and when executed, implements the method according to the embodiments of the present disclosure.
[0167] According to an embodiment of the present disclosure, a computer-readable storage medium may be a non-volatile computer-readable storage medium. For example, it may include, but is not limited to: 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), a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination thereof. In the present disclosure, a computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, apparatus, or device.
[0168] For example, according to an embodiment of the present disclosure, the computer-readable storage medium may include the ROM 1102 and / or the RAM 1103 described above and / or one or more memories other than the ROM 1102 and the RAM 1103 .
[0169] An embodiment of the present disclosure also includes a computer program product, which includes a computer program, which contains program code for executing the method provided by the embodiment of the present disclosure. When the computer program product runs on an electronic device, the program code is used to enable the electronic device to implement the business monitoring method provided by the embodiment of the present disclosure.
[0170] When the computer program is executed by the processor 1101, the above functions defined in the system / device of the embodiment of the present disclosure are performed. According to the embodiment of the present disclosure, the system, device, module, unit, etc. described above can be implemented by a computer program module.
[0171] In one embodiment, the computer program may be stored on a tangible storage medium such as an optical storage device or a magnetic storage device. In another embodiment, the computer program may be transmitted and distributed in the form of a signal on a network medium, downloaded and installed via the communication portion 1109, and / or installed from removable media 1111. The program code contained in the computer program may be transmitted using any appropriate network medium, including but not limited to wireless, wired, or any suitable combination thereof.
[0172] According to an embodiment of the present disclosure, the program code for executing the computer program provided by the embodiment of the present disclosure can be written in any combination of one or more programming languages. Specifically, these computer programs can be implemented using high-level procedural and / or object-oriented programming languages, and / or assembly / machine languages. Programming languages include, but are not limited to, languages such as Java, C++, python, "C" or similar programming languages. The program code can be executed entirely on the user computing device, partially on the user device, partially on a remote computing device, or entirely on a remote computing device or server. In cases involving a remote computing device, the remote computing device can be connected to the user computing device through any type of network, including a local area network (LAN) or a wide area network (WAN), or can be connected to an external computing device (for example, using an Internet service provider to connect via the Internet).
[0173] The flowcharts and block diagrams in the accompanying drawings illustrate the possible architectures, functions, and operations of the systems, methods, and computer program products according to various embodiments of the present disclosure. In this regard, each box in the flowchart or block diagram may represent a module, program segment, or portion of code, which contains one or more executable instructions for implementing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the boxes may occur in an order different from that marked in the accompanying drawings. For example, two boxes shown in succession may actually be executed substantially in parallel, or they may 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 flowchart, as well as the combination of boxes in the block diagram or flowchart, may be implemented using a dedicated hardware-based system that performs the specified function or operation, or may be implemented using a combination of dedicated hardware and computer instructions. It will be understood by those skilled in the art that the features described in the various embodiments and / or claims of the present disclosure may be combined and / or coupled in various ways, even if such combinations or couplings are not explicitly described in the present disclosure. In particular, without departing from the spirit and teachings of the present disclosure, the features described in the various embodiments and / or claims of the present disclosure may be combined and / or coupled in various ways, and all such combinations and / or couplings fall within the scope of the present disclosure.
[0174] The embodiments of the present disclosure are described above. However, these embodiments are for illustrative purposes only and are not intended to limit the scope of the present disclosure. Although each embodiment has been described separately above, this does not mean that the measures in each embodiment cannot be used in combination to advantage. The scope of the present disclosure is defined by the appended claims and their equivalents. Without departing from the scope of the present disclosure, those skilled in the art may make various substitutions and modifications, which should all fall within the scope of the present disclosure.
Claims
1. A business monitoring method, comprising: Acquire target log information of at least one monitored interface in a monitored service, wherein the monitored service is divided into a plurality of service nodes, and the plurality of service nodes are associated with each other; Acquire configuration information of the monitored service, wherein the configuration information includes a mapping relationship between each of the service nodes and at least one monitored interface; Determine a target service node corresponding to the target log information according to the configuration information; Generate business node event information according to the target log information and the target business node, wherein the business node event information includes: business domain id, business process id, business process node orchestration diagram id, business id, and execution status information; and Monitoring the monitored service according to the service node event information includes: In response to receiving the target business domain id and the target business process id, determining a target business process node orchestration graph id associated with the target business domain id and the target business process id, and displaying a business process graph represented by the target business process node orchestration graph id; In response to receiving a service keyword, querying to obtain a target service ID corresponding to the service keyword, and acquiring target service node event information corresponding to each target service node in the service process diagram according to the target service ID or the target service process ID; The target service nodes are presented in different colors according to the types of event information of the target service nodes, and a service monitoring result including the execution status of each target service node is obtained.
2. The method according to claim 1, further comprising: Obtain access operations for connecting services of different systems to the service monitoring platform; as well as In response to the access operation, application instance information of the services of the different systems is input into the service monitoring platform, so as to access the services of the different systems to the service monitoring platform.
3. The method according to claim 2, further comprising: According to the business scenarios of the different systems, the business processes of the businesses of the different systems are divided and arranged into business nodes.
4. The method according to claim 1, wherein: Obtaining target log information of at least one monitored interface in the monitored service includes: Collecting log information according to a custom log component for collecting log information of the monitored business; In the case where the log information belongs to a preset log level, determining whether the log information is log information corresponding to the monitored interface; and The log information corresponding to the monitored interface is used as the target log information.
5. The method according to claim 1, wherein: Monitoring the monitored service according to the service node event information includes: Acquire the target service node and the target execution status of the target service node in the service node event information, wherein the target execution status includes success and exception; When the target execution status is successful, determining that the target service node is displayed with a first display effect; When the target execution state is abnormal, it is determined that the target service node is displayed with a second display effect.
6. The method according to claim 1, further comprising: Acquire a service keyword related to the monitored service; Constructing an index relationship between the service keyword and the service node event information; as well as The index relationship is stored in a database so as to query the execution status information of the monitored service according to the service keyword.
7. The method according to claim 6, further comprising: Determine the business identification information or associated information according to the business keyword; as well as The execution status information of the monitored service is queried according to the service identification information or the associated information.
8. A service monitoring device, comprising: A first acquisition module is used to acquire target log information of at least one monitored interface in a monitored service, wherein the monitored service is divided into a plurality of service nodes, and the plurality of service nodes are associated with each other; A second acquisition module, used to acquire configuration information of the monitored service, wherein the configuration information includes a mapping relationship between each of the service nodes and at least one monitored interface; A determination module, configured to determine a target service node corresponding to the target log information according to the configuration information; A generating module, configured to generate service node event information according to the target log information and the target service node, wherein the service node event information includes: service domain ID, service process ID, service process node orchestration diagram ID, service ID, and execution status information; and A monitoring module, used to monitor the monitored service according to the service node event information, including: In response to receiving the target business domain id and the target business process id, determining a target business process node orchestration graph id associated with the target business domain id and the target business process id, and displaying a business process graph represented by the target business process node orchestration graph id; In response to receiving a service keyword, querying to obtain a target service ID corresponding to the service keyword, and acquiring target service node event information corresponding to each target service node in the service process diagram according to the target service ID or the target service process ID; The target service nodes are presented in different colors according to the types of event information of the target service nodes, and a service monitoring result including the execution status of each target service node is obtained.
9. A computer system comprising: one or more processors; a memory 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 7.
10. A computer-readable storage medium having executable instructions stored thereon, which, when executed by a processor, enables the processor to implement the method according to any one of claims 1 to 7.
11. A computer program product comprising computer executable instructions, which when executed are used to implement the method of any one of claims 1 to 7.
Citation Information
Patent Citations
Business system monitoring method and system
CN107992398A
Monitoring method, device and system, electronic equipment and computer readable storage medium
CN110471824A
Cluster environment user log real-time monitoring method and device
CN110990213A
Method for displaying current to-do task and subsequent to-do workflow
CN111192004A
Business process monitoring method, apparatus and device, and computer readable medium
CN111858621A
