A service monitoring method, device, medium and program product
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- BEIJING YOUTEJIE INFORMATION TECH
- Filing Date
- 2026-03-09
- Publication Date
- 2026-06-16
Smart Images
Figure CN122220180A_ABST
Abstract
Description
Technical Field
[0001] This invention relates to the field of computer technology, and in particular to a business monitoring method, device, medium, and program product. Background Technology
[0002] In a distributed system architecture, a complete business transaction often requires the collaboration of multiple heterogeneous systems. How to achieve effective business monitoring in a distributed system architecture has become one of the key research directions.
[0003] Currently, existing business monitoring methods typically employ distributed tracing technology. This involves generating a unique tracing identifier to link the call paths of the same request across different systems, creating a complete business chain, and then using this complete chain for monitoring. However, in complex real-world production environments, different systems may use different tracing protocols. This causes the tracing identifier to be reset or changed when the same business transaction switches between different systems, making it difficult to maintain a consistent trace using a single identifier. Furthermore, when a system introduces message queues for asynchronous communication, the call relationship between message producers and consumers follows a "store-and-forward" pattern. Traditional time-series-based tracing methods cannot effectively correlate asynchronous events, causing the chain to break at the message queue. Therefore, existing technologies struggle to reconstruct complete business transaction chains in complex, heterogeneous environments, resulting in poor accuracy in business monitoring. Summary of the Invention
[0004] This invention provides a business monitoring method, device, medium, and program product, which can accurately reconstruct the complete business transaction chain in complex heterogeneous environments and improve the accuracy of business monitoring.
[0005] According to one aspect of the present invention, a business monitoring method is provided, comprising: Obtain the business identifier and business primary key corresponding to the target business, and obtain the target tracking identifier based on the business identifier and the business primary key; Based on the target tracking identifier, obtain the target link data corresponding to the target service, and establish an initial service link based on the target link data; Based on the business primary key, a message queue node is added to the initial business link to generate the target business link, and business indicator data is obtained based on the target business link.
[0006] According to another aspect of the present invention, a business monitoring device is provided, comprising: The identifier acquisition module is used to acquire the business identifier and business primary key corresponding to the target business, and to acquire the target tracking identifier based on the business identifier and the business primary key; The link establishment module is used to obtain target link data corresponding to the target service based on the target tracking identifier, and to establish an initial service link based on the target link data; The data acquisition module is used to add a message queue node to the initial business link based on the business primary key to generate a target business link, and to acquire business indicator data based on the target business link.
[0007] According to another aspect of the present invention, an electronic device is provided, the electronic device comprising: At least one processor; and A memory communicatively connected to the at least one processor; wherein, The memory stores a computer program that can be executed by the at least one processor, which enables the at least one processor to perform the business monitoring method according to any embodiment of the present invention.
[0008] According to another aspect of the present invention, a computer-readable storage medium is provided, the computer-readable storage medium storing a computer program, the computer program being configured to cause a processor to execute and implement the business monitoring method described in any embodiment of the present invention.
[0009] According to another aspect of the present invention, a computer program product is provided, comprising a computer program that, when executed by a processor, implements the business monitoring method described in any embodiment of the present invention.
[0010] The technical solution of this invention involves obtaining the business identifier and business primary key corresponding to the target business, and obtaining the target tracking identifier based on the business identifier and business primary key; obtaining the target link data corresponding to the target business based on the target tracking identifier, and establishing an initial business link based on the target link data; adding a message queue node to the initial business link based on the business primary key to generate the target business link, and obtaining business indicator data based on the target business link; by setting the business identifier and business primary key to determine the tracking identifier of the target business in different systems, and adding a message queue node to the initial business link based on the business primary key to generate a complete business link, accurate reconstruction of the complete business transaction link in a complex heterogeneous environment can be achieved, thereby improving the accuracy of business monitoring.
[0011] It should be understood that the description in this section is not intended to identify key or essential features of the embodiments of the present invention, nor is it intended to limit the scope of the invention. Other features of the invention will become readily apparent from the following description. Attached Figure Description
[0012] To more clearly illustrate the technical solutions in the embodiments of the present invention, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.
[0013] Figure 1 This is a flowchart of a business monitoring method provided according to Embodiment 1 of the present invention; Figure 2 This is a flowchart of a business monitoring method provided according to Embodiment 2 of the present invention; Figure 3 This is a schematic diagram of the structure of a business monitoring device according to Embodiment 3 of the present invention; Figure 4 This is a schematic diagram of the structure of an electronic device that implements the service monitoring method of this invention. Detailed Implementation
[0014] To enable those skilled in the art to better understand the present invention, the technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings of the embodiments of the present invention. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort should fall within the scope of protection of the present invention.
[0015] It should be noted that the terms "first," "second," "target," etc., used in the specification, claims, and accompanying drawings of this invention are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such terms can be used interchangeably where appropriate so that embodiments of the invention described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.
[0016] Example 1 Figure 1This is a flowchart of a business monitoring method provided in Embodiment 1 of the present invention. This embodiment is applicable to situations involving monitoring business transactions and calculating indicators. The method can be executed by a business monitoring device, which can be implemented in hardware and / or software. Typically, the business monitoring device can be configured in an electronic device, such as a computer or server. Figure 1 As shown, the method includes: S110. Obtain the business identifier and business primary key corresponding to the target business, and obtain the target tracking identifier based on the business identifier and the business primary key.
[0017] The target business can be a business transaction requiring business monitoring and metric calculation; this embodiment does not specifically limit the type of target business. In this embodiment, a virtual business space can be pre-constructed, and multiple identifier associations can be established. Specifically, a globally unique business identifier can be generated for each business request at the business entry gateway. Subsequently, when a business request flows through different middleware or systems, even if a new trace identifier (TraceIdentity, Trace ID) is generated, the business identifier will be passed down downstream as a custom tag through a proxy or software development kit, i.e., a business identifier field is added to the business messages at each stage. Additionally, for scenarios where passing the identifier is not possible (such as legacy systems), a business primary key can be introduced to establish an association table between the business primary key and the Trace ID. Typically, the business primary key can be an order identifier, which can be generated by the order system, etc.
[0018] In this embodiment, firstly, the raw link data of the target service can be collected through system logs, etc. Then, the service identifier and service primary key corresponding to the target service can be identified from the raw link data. Next, based on the raw link data, different Trace IDs corresponding to the service identifier and service primary key can be identified as target tracing identifiers. Each link data entry can include fields such as system identifier, service identifier, service primary key, tracing identifier, and timestamp; the tracing identifier is a mandatory field. It should be noted that the service identifier, service primary key, and tracing identifier fields may not appear simultaneously in a single link data entry; these fields can be freely combined in different link data entries, determined by the link data definitions of different systems.
[0019] Obtaining the target tracking identifier based on the business identifier and the business primary key may include: Based on the business identifier and the business primary key, intermediate link data is obtained by filtering from the original link data, and the target tracking identifier is identified from the intermediate link data.
[0020] In this embodiment, when obtaining the target tracking identifier, the intermediate link data containing the current business identifier or business primary key can be filtered from the original link data first, and then the tracking identifier field of each intermediate link data can be extracted to identify all the target tracking identifiers.
[0021] S120. Based on the target tracking identifier, obtain the target link data corresponding to the target service, and establish an initial service link based on the target link data.
[0022] Specifically, link data containing target tracking identifiers can be filtered from the raw link data to obtain target link data. Standardization processing, such as field filtering and deduplication, is then performed on the acquired target link data to obtain standard link data. Next, the business operation and execution time corresponding to each standard link data can be identified, and these business operations are combined according to their execution time order to generate an initial business link. The correspondence between business operations and link data can be pre-defined, and the business operation corresponding to the link data can be identified based on this correspondence.
[0023] Establishing an initial service link based on the target link data may include: Based on the target link data, synchronous call event data and asynchronous call event data are obtained; based on the synchronous call event data and the asynchronous call event data, each business execution path and its corresponding execution time are obtained, and each business execution path is deduplicated and sorted according to the execution time to establish an initial business link.
[0024] In the target business, calls between services can include synchronous calls and asynchronous calls. In this embodiment, synchronous call event data and asynchronous call event data can be obtained from the target link data based on preset call type determination rules. The call type determination rules can be as follows: if service A calls service B and immediately receives a response, it is determined to be a synchronous call; if service A sends a call message and immediately returns, and then service B consumes the call message, it is determined to be an asynchronous call.
[0025] Subsequently, based on the synchronous call event data, each synchronous call operation can be identified and combined into a synchronous call path according to the order of its timestamps. Simultaneously, based on the asynchronous call event data, each asynchronous call operation can be identified and combined into an asynchronous call path according to the order of its timestamps. Next, the synchronous and asynchronous call paths can be determined as business execution paths, such as synchronous retries and asynchronous compensation, and the execution time corresponding to each business execution path can be determined based on its timestamp. Finally, the business execution paths can be deduplicated and sorted according to the execution time and preset pruning and merging rules to generate the final initial business chain. For example, the preset pruning and merging rules could involve deduplicating identical business execution paths within a preset time window, retaining only one business execution path, and then combining the deduplicated business execution paths according to the order of their execution times to generate the initial business chain.
[0026] S130. Based on the business primary key, add a message queue node to the initial business link to generate a target business link, and obtain business indicator data based on the target business link.
[0027] It is worth noting that in asynchronous scenarios, the producer does not directly send request information to the consumer. Instead, it first sends the request information to a message queue, which then asynchronously forwards it to the consumer. This can lead to a break in the business chain. To address this, this embodiment identifies the associated message queue sending and receiving nodes in the initial business chain based on the business primary key and a preset time window threshold. A message queue node is then added between these two nodes to generate a complete business chain as the target business chain. Finally, based on the target business chain, business metrics data can be calculated according to preset metric calculation rules. For example, business metrics may include business success rate, total end-to-end time, time spent at each node, and asynchronous backlog latency.
[0028] The process of adding a message queue node to the initial business link based on the business primary key to generate the target business link may include: Based on the target link data, obtain the node event data corresponding to each initial node in the initial business link, and determine the message queue sending node and message queue receiving node in each initial node based on the node event data and the business primary key; If the message queue sending node and the message queue receiving node are detected to meet the preset association detection conditions, a message queue node is added between the message queue sending node and the message queue receiving node to generate the target service link.
[0029] The business link can be composed of nodes and edges between nodes. Each node represents a service instance or middleware instance, and the edges represent call relationships. In this embodiment, after generating the initial business link, node event data corresponding to each initial node can be extracted from the target link data. Then, based on the node event data, message queue sending nodes (where the business operation is sending request information to the message queue and the node event data contains the business primary key) and message queue receiving nodes (where the business operation is receiving request information from the message queue and the node event data contains the business primary key) can be identified among all initial nodes.
[0030] Typically, the node event data corresponding to the message queue sending node may include fields such as service identifier, topic, business primary key, line content container tag context, and timestamp; the node event data corresponding to the message queue receiving node may include fields such as service identifier, message identifier, topic, business primary key, and timestamp. In this embodiment, after determining the message queue sending and receiving nodes, it can determine whether each group of message queue sending and receiving nodes meets the preset association detection conditions based on the node event data. If so, the two nodes are determined to be matched, and a message queue node is added between them to generate the target business link.
[0031] Among them, the preset association detection conditions can be preset conditions used to determine whether the message queue sending node and the message queue receiving node match. For example, it can be that the two nodes have the same business primary key and topic.
[0032] The detection that the message queue sending node and the message queue receiving node meet the preset association detection conditions may include: Based on the node event data, obtain the first topic and first timestamp corresponding to the message queue sending node, and the second topic and second timestamp corresponding to the message queue receiving node; If the first topic is detected to be the same as the second topic, and the time difference between the first timestamp and the second timestamp is less than a preset time window threshold, then it is determined that the message queue sending node and the message queue receiving node meet the preset association detection conditions.
[0033] In a specific example, the preset association detection condition could be that the topics are the same and the time interval is less than a preset time window threshold. Therefore, when determining whether a message queue sending node and a message queue receiving node match, firstly, the first topic and first timestamp corresponding to the sending node can be extracted from the node event data corresponding to the sending node. Simultaneously, the second topic and second timestamp corresponding to the receiving node can be extracted from the node event data corresponding to the receiving node. Then, it is determined whether the first topic and the second topic are the same. If so, it is further determined whether the time difference between the first timestamp and the second timestamp is less than a preset time window threshold (e.g., 5 seconds). If so, it is determined that the current message queue sending node and message queue receiving node have successfully matched, i.e., the preset association detection condition is met.
[0034] The advantage of the above settings is that they can improve the accuracy of correlation detection and the accuracy of the target business link.
[0035] The technical solution of this invention involves obtaining the business identifier and business primary key corresponding to the target business, and obtaining the target tracking identifier based on the business identifier and business primary key; obtaining the target link data corresponding to the target business based on the target tracking identifier, and establishing an initial business link based on the target link data; adding a message queue node to the initial business link based on the business primary key to generate the target business link, and obtaining business indicator data based on the target business link; by setting the business identifier and business primary key to determine the tracking identifier of the target business in different systems, and adding a message queue node to the initial business link based on the business primary key to generate a complete business link, accurate reconstruction of the complete business transaction link in a complex heterogeneous environment can be achieved, thereby improving the accuracy of business monitoring.
[0036] Example 2 Figure 2 This is a flowchart of a business monitoring method provided in Embodiment 2 of the present invention. This embodiment is a further refinement of the above technical solution, and the technical solution in this embodiment can be combined with one or more of the above implementation methods. Figure 2 As shown, the method includes: S210. Obtain the business identifier and business primary key corresponding to the target business, and obtain the target tracking identifier based on the business identifier and the business primary key.
[0037] S220. Based on the target tracking identifier, obtain the target link data corresponding to the target service, and establish an initial service link based on the target link data.
[0038] S230. Based on the business primary key, add a message queue node to the initial business link to generate the target business link.
[0039] S240. Obtain the node indicator data and infrastructure configuration data corresponding to each target node in the target business link, and visualize the target business link and the node indicator data and infrastructure configuration data corresponding to each target node.
[0040] In this embodiment, for each target node, its corresponding metadata information can be set, such as service identifier, Internet Protocol address, host identifier, container identifier, process identifier, etc. Additionally, the system can periodically or in real-time synchronize infrastructure configuration data from the Configuration Management Database (CMDB) interface, including service deployment information, application and host associations, responsible person tags, data center / availability zone, environment (development / testing / production), deployment version, etc. Then, based on preset matching rules between metadata and infrastructure configuration data, such as exact matching of service identifier + Internet Protocol address, fuzzy matching of host identifier, and direct association through container identifier, the infrastructure configuration data corresponding to each target node can be determined, and the matched infrastructure configuration data is stored as an attribute of the target node. If a match fails, it is recorded as an unknown node, and an alarm is triggered. For middleware nodes, the corresponding infrastructure configuration data is also matched using connection information, such as Internet Protocol address + port, to obtain information such as its deployment location, specifications, and cluster affiliation.
[0041] In addition, in this embodiment, node-related metric data can also be collected from monitoring systems (such as Prometheus, Zabbix, Elasticsearch, etc.), including infrastructure metric data (such as CPU utilization, memory utilization, disk I / O, network traffic, etc.) and application performance metric data (such as queries per second, average latency, error rate, HIPCO status code distribution, etc.). Then, the node metric data can be associated with target nodes using node identifiers (such as service identifier + instance identifier, Internet Protocol address, host identifier, etc.) and time ranges to obtain the node metric data corresponding to each target node.
[0042] Furthermore, the target business chain can be output as a directed graph. Node metrics and infrastructure configuration data can be displayed on each node, and the synchronous or asynchronous call type can be labeled on the edges to generate a visual business transaction topology diagram. The business transaction topology diagram can also support time-axis queries to dynamically display real-time node metrics, such as using color depth to represent health and bubble size to represent traffic load.
[0043] S250. Based on the preset indicator calculation rules, and the node indicator data and infrastructure configuration data corresponding to each target node, the business indicator data is calculated.
[0044] In this embodiment, for each business indicator, corresponding indicator calculation rules can be pre-set, including the required data, calculation logic, and result format. After generating the business transaction topology diagram, based on the business transaction topology diagram and the pre-set indicator calculation rules, the indicator calculation results corresponding to each business indicator can be calculated according to the node indicator data and infrastructure configuration data corresponding to each target node, thereby obtaining the business indicator data.
[0045] Optionally, this embodiment also supports combining CMDB dimensions, such as by responsible person or by data center, to perform aggregated drill-down analysis of node indicator data to obtain business indicator data corresponding to each dimension. Additionally, this embodiment also supports automatically identifying issues such as illegal calls, missing dependencies, and zombie nodes by comparing the actual call topology with the expected dependencies defined in the CMDB, thereby generating an architecture compliance report.
[0046] Optionally, after calculating the business indicator data according to the preset indicator calculation rules, and the node indicator data and infrastructure configuration data corresponding to each target node, the following may also be included: If an anomaly is detected in the business metric data, the abnormal node is obtained, and the node metric data corresponding to the abnormal node is obtained based on the node metric data corresponding to each target node. Based on the node indicator data corresponding to the abnormal node, an indicator change curve is generated and the indicator change curve is visualized.
[0047] In this embodiment, if the calculation result of a certain business indicator meets preset anomaly detection conditions, such as the total end-to-end time exceeding a preset range, then the target nodes involved in the business indicator can be extracted as abnormal nodes based on the preset correspondence between business indicators and nodes. Next, node indicator data corresponding to the abnormal node within a certain time period can be extracted, and curves can be plotted based on the extracted node indicator data to generate an indicator change curve. This indicator change curve can then be visualized to assist in root cause analysis.
[0048] In one specific implementation of this embodiment, taking a user placing an order and making payment as an example, the user requests access to the order system, and the gateway generates a business identifier Biz_123. The order system calls the inventory system (synchronously) and transmits Biz_123, while the inventory system internally uses the tracking identifier Trace_A. The order system sends an order creation completion message to the message queue (asynchronously), which contains the order number Order_001 (business primary key). The payment system consumes this message and begins processing the payment (this process may involve synchronous calls to risk control), internally using the tracking identifier Trace_B and unable to receive the transmitted parameters.
[0049] This invention associates Biz_123, Order_001, Trace_A, and Trace_B to the same virtual space, and associates the producer (order system) with the consumer (payment system) based on the order number Order_001, thereby completing the message queue nodes in the link. After reconstructing the topology, the system automatically matches the order system node with the order service configuration item in the CMDB, obtaining that the service manager is "Zhang San", deployed in "Data Center A", and the current version is "v2.1". At the same time, it pulls the central processing unit utilization (currently 45%), queries per second (1200), and error rate (0.1%) of the order service instance from the monitoring system and displays them on the topology map with a green health icon.
[0050] When a transaction experiences a sudden increase in processing time, operations personnel can click on the order system node in the topology diagram to view the node's central processing unit (CPU) utilization, memory utilization, garbage collection time, and other metrics before and after the transaction. For example, if the CPU utilization spikes to 90%, the problem can be quickly identified as a resource bottleneck. The resulting topology diagram not only displays the call relationships (gateway -> order system -> inventory system -> message queue -> payment system -> risk control system) but also integrates configuration and monitoring information, providing operations personnel with a comprehensive overview.
[0051] The technical solution of this invention acquires node indicator data and infrastructure configuration data corresponding to each target node in the target business link, and visualizes the target business link and the node indicator data and infrastructure configuration data corresponding to each target node; according to preset indicator calculation rules and the node indicator data and infrastructure configuration data corresponding to each target node, business indicator data is calculated; by configuring corresponding node indicator data and infrastructure configuration data for the target nodes, and calculating business indicator data based on the node indicator data and infrastructure configuration data, the calculation efficiency of business indicator data can be improved, and the intuitiveness of business monitoring can be enhanced.
[0052] This invention aims to address the technical problems of broken business transaction links and incomplete topologies in existing technologies under multi-system, multi-tracking, and asynchronous decoupling scenarios. It provides a method that can reconstruct complete business transaction links in complex heterogeneous environments and deeply integrate link nodes with CMDB configuration information and real-time monitoring metrics. By constructing a virtual business space to accommodate multiple heterogeneous tracking identifiers, and using a "spatiotemporal window"-based association algorithm to penetrate asynchronous middleware, a true business topology is ultimately generated. Based on this, by matching node metadata with CMDB configuration items, the monitoring system's metric data is mounted to the corresponding nodes, achieving a comprehensive association between the business call chain and infrastructure and performance metrics, forming a more observable business topology view.
[0053] This invention employs a heterogeneous tracking identifier fusion mechanism. Unlike existing technologies that attempt to unify identifiers, this invention establishes a "business lineage" association table, generating a "root business identifier" at the gateway layer or entry service, and dynamically associating it with various heterogeneous tracking identifiers generated by subsequent systems to form a "one-to-many" lineage graph. Furthermore, it utilizes asynchronous penetration technology, parsing message identifiers and specific message body content (such as business primary keys) of message queues to construct a causal relationship of "producer-message queue-consumer," filling the link gaps caused by asynchronous decoupling. Moreover, it employs a topology reconstruction algorithm based on timestamps and business dimensions. In massive logs of synchronous and asynchronous mixed calls, it reconstructs a complete directed acyclic graph of business transactions using graph algorithms through timestamp alignment, extraction of business primary keys (such as order numbers), and determination of call direction. Simultaneously, it employs dynamic association between CMDB and link nodes, automatically matching configuration items in the CMDB using information such as service names, internet protocol addresses, and host identifiers carried by link nodes to obtain metadata such as the application to which the node belongs, the person in charge, and the deployment location, and updating it in real time. Finally, the monitoring metrics were bound to business nodes. Real-time monitoring metrics were associated with the reconstructed business nodes along the time axis. The health status and load of the nodes were presented in a visual way on the topology diagram, and drill-down analysis capabilities were provided.
[0054] By adopting the above technical solutions, this invention (1) achieves link integrity, solves the link breakage problem caused by asynchronous calls and heterogeneous tracing identifiers, and realizes full-link restoration of cross-system business transactions; (2) ensures topology authenticity, the generated business topology accurately reflects the real physical flow of synchronous and asynchronous mixed calls, which is convenient for root cause analysis; (3) ensures indicator accuracy, the business indicators (such as real time consumption, success rate, etc.) calculated based on the complete link eliminate the black hole of asynchronous waiting period, and provide reliable data support for business operation and maintenance and performance optimization; (4) achieves full-stack observability, the call chain data is deeply integrated with CMDB configuration information and monitoring indicators, and full-stack observability from business to underlying infrastructure is realized, which improves the efficiency of fault location; (5) achieves intelligent operation and maintenance, the person in charge and environment can be found quickly through CMDB information, anomalies can be detected in advance through monitoring indicators, support architecture compliance inspection, and provide data foundation for operation and maintenance automation; (6) improves compatibility, no need for unified link tracing protocol, friendly to old systems, and supports docking with multiple CMDB and monitoring systems.
[0055] Example 3 Figure 3 This is a schematic diagram of a business monitoring device provided in Embodiment 3 of the present invention. Figure 3 As shown, the device includes: an identifier acquisition module 310, a link establishment module 320, and a data acquisition module 330; wherein, The identifier acquisition module 310 is used to acquire the business identifier and business primary key corresponding to the target business, and to acquire the target tracking identifier based on the business identifier and the business primary key; The link establishment module 320 is used to obtain target link data corresponding to the target service based on the target tracking identifier, and to establish an initial service link based on the target link data; The data acquisition module 330 is used to add a message queue node to the initial business link according to the business primary key to generate a target business link, and to acquire business indicator data according to the target business link.
[0056] The technical solution of this invention involves obtaining the business identifier and business primary key corresponding to the target business, and obtaining the target tracking identifier based on the business identifier and business primary key; obtaining the target link data corresponding to the target business based on the target tracking identifier, and establishing an initial business link based on the target link data; adding a message queue node to the initial business link based on the business primary key to generate the target business link, and obtaining business indicator data based on the target business link; by setting the business identifier and business primary key to determine the tracking identifier of the target business in different systems, and adding a message queue node to the initial business link based on the business primary key to generate a complete business link, accurate reconstruction of the complete business transaction link in a complex heterogeneous environment can be achieved, thereby improving the accuracy of business monitoring.
[0057] Optionally, the identifier acquisition module 310 is specifically used to filter intermediate link data from the original link data based on the service identifier and the service primary key, and to identify the target tracking identifier from the intermediate link data.
[0058] Optionally, the link establishment module 320 is specifically used to obtain synchronous call event data and asynchronous call event data based on the target link data; Based on the synchronous call event data and the asynchronous call event data, obtain each business execution path and its corresponding execution time, and deduplicate and sort each business execution path according to the execution time to establish an initial business link.
[0059] Optionally, the data acquisition module 330 includes: The node determination unit is used to obtain node event data corresponding to each initial node in the initial service link based on the target link data, and to determine the message queue sending node and message queue receiving node in each initial node based on the node event data and the service primary key. The link generation unit is used to add a message queue node between the message queue sending node and the message queue receiving node to generate a target service link if it is detected that the message queue sending node and the message queue receiving node meet a preset association detection condition.
[0060] Optionally, the link generation unit is specifically used to obtain, based on the node event data, the first topic and first timestamp corresponding to the message queue sending node, and the second topic and second timestamp corresponding to the message queue receiving node; If the first topic is detected to be the same as the second topic, and the time difference between the first timestamp and the second timestamp is less than a preset time window threshold, then it is determined that the message queue sending node and the message queue receiving node meet the preset association detection conditions.
[0061] Optionally, the data acquisition module 330 is specifically used to acquire node indicator data and infrastructure configuration data corresponding to each target node in the target business link, and to visualize the target business link and the node indicator data and infrastructure configuration data corresponding to each target node. Based on the preset indicator calculation rules, as well as the node indicator data and infrastructure configuration data corresponding to each target node, the business indicator data is calculated.
[0062] Optional, the business monitoring device also includes: An anomaly detection module is used to obtain an abnormal node if an anomaly is detected in the business indicator data, and to obtain the node indicator data corresponding to the abnormal node based on the node indicator data corresponding to each target node. The curve generation module is used to generate an indicator change curve based on the node indicator data corresponding to the abnormal node, and to visualize the indicator change curve.
[0063] The business monitoring device provided in the embodiments of the present invention can execute the business monitoring method provided in any embodiment of the present invention, and has the corresponding functional modules and beneficial effects of the method execution.
[0064] The collection, storage, use, processing, transmission, provision, and disclosure of user personal information involved in the technical solution disclosed herein comply with the provisions of relevant laws and regulations and do not violate public order and good morals.
[0065] Example 4 Figure 4 A schematic diagram of an electronic device 40 that can be used to implement embodiments of the present invention is shown. The electronic device 40 is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device 40 can also represent various forms of mobile devices, such as personal digital processors, cellular phones, smartphones, wearable devices (such as helmets, glasses, watches, etc.), and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely illustrative and are not intended to limit the implementation of the invention described and / or claimed herein.
[0066] like Figure 4As shown, the electronic device 40 includes at least one processor 41 and a memory, such as a read-only memory (ROM) 42 or a random access memory (RAM) 43, communicatively connected to the at least one processor 41. The memory stores computer programs executable by the at least one processor. The processor 41 can perform various appropriate actions and processes based on the computer program stored in the read-only memory 42 or loaded from the storage unit 48 into the random access memory 43. The RAM 43 can also store various programs and data required for the operation of the electronic device 40. The processor 41, ROM 42, and RAM 43 are interconnected via a bus 44. An input / output (I / O) interface 45 is also connected to the bus 44.
[0067] Multiple components in electronic device 40 are connected to I / O interface 45, including: input unit 46, such as keyboard, mouse, etc.; output unit 47, such as various types of monitors, speakers, etc.; storage unit 48, such as disk, optical disk, etc.; and communication unit 49, such as network card, modem, wireless transceiver, etc. Communication unit 49 allows electronic device 40 to exchange information / data with other devices through computer networks such as the Internet and / or various telecommunications networks.
[0068] Processor 41 can be a variety of general-purpose and / or special-purpose processing components with processing and computing capabilities. Some examples of processor 41 include, but are not limited to, central processing units, graphics processing units, various special-purpose artificial intelligence computing chips, various processors running machine learning model algorithms, digital signal processors, and any suitable processor, controller, microcontroller, etc. Processor 41 performs the various methods and processes described above, such as business monitoring methods.
[0069] In some embodiments, the service monitoring method may be implemented as a computer program tangibly contained in a computer-readable storage medium, such as storage unit 48. In some embodiments, part or all of the computer program may be loaded and / or installed on electronic device 40 via ROM 42 and / or communication unit 49. When the computer program is loaded into RAM 43 and executed by processor 41, one or more steps of the service monitoring method described above may be performed. Alternatively, in other embodiments, processor 41 may be configured to perform the service monitoring method by any other suitable means (e.g., by means of firmware).
[0070] Various embodiments of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field-programmable gate arrays, application-specific integrated circuits (ASICs), application-specific standard products (ASICs), system-on-a-chip (SoCs), complex programmable logic devices, computer hardware, firmware, software, and / or combinations thereof. These various embodiments may include implementations in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which may be a dedicated or general-purpose programmable processor, capable of receiving data and instructions from a storage system, at least one input device, and at least one output device, and transmitting data and instructions to the storage system, the at least one input device, and the at least one output device.
[0071] Computer programs used to implement the methods of the present invention may be written in any combination of one or more programming languages. These computer programs may be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device, such that when executed by the processor, the computer programs cause the functions / operations specified in the flowcharts and / or block diagrams to be performed. The computer programs may be executed entirely on a machine, partially on a machine, or as a standalone software package, partially on a machine and partially on a remote machine, or entirely on a remote machine or server.
[0072] In the context of this invention, a computer-readable storage medium can be a tangible medium that may contain or store a computer program for use by or in conjunction with an instruction execution system, apparatus, or device. A computer-readable storage medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination thereof. Alternatively, a computer-readable storage medium may be a machine-readable signal medium. More specific examples of machine-readable storage media include electrical connections based on one or more wires, portable computer disks, hard disks, random access memory, read-only memory, erasable programmable read-only memory, optical fibers, portable compact disk read-only memory, optical storage devices, magnetic storage devices, or any suitable combination thereof.
[0073] To provide interaction with a user, the systems and techniques described herein can be implemented on an electronic device 40, which includes: a display device (e.g., a cathode ray tube or liquid crystal display) for displaying information to the user; and a keyboard and pointing device (e.g., a mouse or trackball) through which the user provides input to the electronic device 40. Other types of devices can also be used to provide interaction with the user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including sound input, voice input, or tactile input).
[0074] The systems and technologies described herein can be implemented in computing systems that include backend components (e.g., as data servers), or computing systems that include middleware components (e.g., application servers), or computing systems that include frontend components (e.g., user computers with graphical user interfaces or web browsers through which users can interact with implementations of the systems and technologies described herein), or any combination of such backend, middleware, or frontend components. The components of the system can be interconnected via digital data communication of any form or medium (e.g., communication networks). Examples of communication networks include local area networks (LANs), wide area networks (WANs), blockchain networks, and the Internet.
[0075] A computing system can include clients and servers. Clients and servers are generally located far apart and typically interact via a communication network. The client-server relationship is created by computer programs running on the respective computers and having a client-server relationship with each other. The server can be a cloud server.
[0076] This embodiment may also include a computer program product, which includes a computer program that, when executed by a processor, implements the business monitoring method provided in any embodiment of the present invention.
[0077] It should be understood that the various forms of processes shown above can be used, with steps reordered, added, or deleted. For example, the steps described in this invention can be executed in parallel, sequentially, or in different orders, as long as the desired result of the technical solution of this invention can be achieved, and this is not limited herein.
[0078] The specific embodiments described above do not constitute a limitation on the scope of protection of this invention. Those skilled in the art should understand that various modifications, combinations, sub-combinations, and substitutions can be made according to design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of this invention should be included within the scope of protection of this invention.
Claims
1. A business monitoring method, characterized in that, include: Obtain the business identifier and business primary key corresponding to the target business, and obtain the target tracking identifier based on the business identifier and the business primary key; Based on the target tracking identifier, obtain the target link data corresponding to the target service, and establish an initial service link based on the target link data; Based on the business primary key, a message queue node is added to the initial business link to generate the target business link, and business indicator data is obtained based on the target business link.
2. The method according to claim 1, characterized in that, Based on the business identifier and the business primary key, obtain the target tracking identifier, including: Based on the business identifier and the business primary key, intermediate link data is obtained by filtering from the original link data, and the target tracking identifier is identified from the intermediate link data.
3. The method according to claim 1, characterized in that, Based on the target link data, an initial service link is established, including: Based on the target link data, obtain synchronous call event data and asynchronous call event data; Based on the synchronous call event data and the asynchronous call event data, obtain each business execution path and its corresponding execution time, and deduplicate and sort each business execution path according to the execution time to establish an initial business link.
4. The method according to claim 1, characterized in that, Based on the business primary key, a message queue node is added to the initial business link to generate the target business link, including: Based on the target link data, obtain the node event data corresponding to each initial node in the initial business link, and determine the message queue sending node and message queue receiving node in each initial node based on the node event data and the business primary key; If the message queue sending node and the message queue receiving node are detected to meet the preset association detection conditions, a message queue node is added between the message queue sending node and the message queue receiving node to generate the target service link.
5. The method according to claim 4, characterized in that, The message queue sending node and the message queue receiving node are detected to meet preset association detection conditions, including: Based on the node event data, obtain the first topic and first timestamp corresponding to the message queue sending node, and the second topic and second timestamp corresponding to the message queue receiving node; If the first topic is detected to be the same as the second topic, and the time difference between the first timestamp and the second timestamp is less than a preset time window threshold, then it is determined that the message queue sending node and the message queue receiving node meet the preset association detection conditions.
6. The method according to claim 1, characterized in that, Obtain business indicator data based on the target business link, including: Obtain the node indicator data and infrastructure configuration data corresponding to each target node in the target business link, and visualize the target business link and the node indicator data and infrastructure configuration data corresponding to each target node. Based on the preset indicator calculation rules, as well as the node indicator data and infrastructure configuration data corresponding to each target node, the business indicator data is calculated.
7. The method according to claim 6, characterized in that, After calculating the business indicator data according to the preset indicator calculation rules, and the node indicator data and infrastructure configuration data corresponding to each target node, the method further includes: If an anomaly is detected in the business metric data, the abnormal node is obtained, and the node metric data corresponding to the abnormal node is obtained based on the node metric data corresponding to each target node. Based on the node indicator data corresponding to the abnormal node, an indicator change curve is generated and the indicator change curve is visualized.
8. An electronic device, characterized in that, The electronic device includes: At least one processor, and A memory communicatively connected to the at least one processor; wherein, The memory stores a computer program that can be executed by the at least one processor, the computer program being executed by the at least one processor to enable the at least one processor to perform the business monitoring method according to any one of claims 1-7.
9. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that enables a processor to execute the business monitoring method according to any one of claims 1-7.
10. A computer program product, characterized in that, It includes a computer program that, when executed by a processor, implements the business monitoring method according to any one of claims 1-7.