Transaction monitoring link graph generation processing method, apparatus, and system

Abstract

The application relates to a transaction monitoring link diagram generation processing method, device and system, and relates to the technical field of information processing. The method comprises the following steps: extracting a resource information table and an access relationship table from a transaction monitoring drawing template; each transaction node corresponds to an application service, and each application service comprises one or more transaction nodes; a directed structure diagram between the transaction nodes is constructed according to the resource information table and the access relationship table; the position of each transaction node in the drawing area in the directed structure diagram is determined; dynamic topology modeling and automatic layout are performed according to the directed structure diagram and the positions of the transaction nodes, and a transaction monitoring link diagram is generated; message analysis information in the access relationship table is used to generate message analysis rules corresponding to transaction flows between the transaction nodes in the transaction monitoring link diagram, and the generated message analysis rules are associated and bound with the corresponding transaction flows in the transaction monitoring link diagram.

Description

Technical Field

[0001] The present invention relates to the field of computer technology, and in particular, to a transaction monitoring link graph generation and processing method, apparatus and system. Background Art

[0002] In fields such as finance and e-commerce that are highly dependent on online transaction systems, transaction monitoring is a core operation and maintenance link for ensuring business continuity and quickly locating faults. It draws a transaction monitoring link graph on the monitoring platform to visualize the flow path of business requests among multiple application services, and parses key fields of network packets transmitted on the link based on this graph, so as to obtain indicators such as transaction volume, response time and success rate, and realize real-time monitoring and alarm. However, in the related art, only the generation or display problem of the monitoring graph is solved separately, so that the monitoring graph drawing process is completely separated from the monitoring rule configuration process, resulting in related problems that reduce the monitoring efficiency, such as repeated entry of related information and information transmission distortion. Summary of the Invention

[0003] The present invention provides a transaction monitoring link graph generation and processing method, apparatus and storage medium, so as to at least solve the problem in the related art that the monitoring graph drawing process is completely separated from the monitoring rule configuration process. The technical solution of the present invention is as follows: According to a first aspect of the embodiments of the present invention, a transaction monitoring link graph generation and processing method is provided. The method includes: extracting a resource information table and an access relationship table from a transaction monitoring drawing template; the resource information table is used to define attribute information of transaction nodes, and at least includes node identifiers, function types and network address information; the access relationship includes the information for defining the access relationship between each transaction node and the associated packet parsing information; each transaction node corresponds to one application service, and each application service includes one or more transaction nodes; constructing a directed structure diagram between each transaction node according to the resource information table and the access relationship table; determining the position of each transaction node in the drawing area in the directed structure diagram; performing dynamic topology modeling and automatic layout according to the directed structure diagram and each node position to generate a transaction monitoring link graph; generating packet parsing rules corresponding to the transaction flows between the transaction nodes in the transaction monitoring link graph according to the packet parsing information in the access relationship table, and associating and binding the generated packet parsing rules with the corresponding transaction flows in the transaction monitoring link graph.

[0004] In one implementation, a directed structure graph is constructed based on a resource information table and an access relationship table. This includes: designating the transaction node marked as an entry node in the resource information table as the root node; wherein the parent node identifier of the root node is empty; determining the pointing relationship between transaction nodes with related relationships based on the pre-defined access relationships within the application service and the inter-application service access relationships between various application services in the access relationship table; the pre-defined access relationships within the application service are load balancing nodes pointing to application nodes, and the inter-application service access relationships are from the transaction node of the source application service to the transaction node of the destination application service; generating directed edges between transaction nodes with related relationships based on the association relationship between the parent node identifier and the unique identifier in the node identifier to obtain the directed structure graph; the directed structure graph includes a forward tree structure graph from the entry node to the service provider application service, and a reverse tree structure graph with the entry node as the service provider and the consumer application service pointing to the entry node.

[0005] In another implementation, determining the position of each transaction node in the drawing area within the directed graph involves: starting from the root nodes at the top of the directed graph, performing a recursive layout operation; wherein the recursive layout operation includes: traversing the directed graph from bottom to top to determine the number of child nodes for each transaction node; recursively calculating the node width of each transaction node based on the node layout type, the number of child nodes for each transaction node, and the spacing between child nodes; and traversing the directed graph from bottom to top to determine the level of each transaction node in the parent-child relationship hierarchy, and recursively calculating the node coordinates of each transaction node based on the node width and the level to which each transaction node belongs.

[0006] In another implementation, after recursively calculating the node coordinates of each transaction node, the method further includes: detecting whether there are abnormal nodes with overlapping node coordinates and / or overlapping node spacing in each transaction node; if an abnormal node is detected, adjusting the coordinates of any node in the abnormal node according to a preset adjustment rule until there is no overlap of node coordinates or overlapping node spacing in the abnormal node.

[0007] In another implementation, message parsing rules corresponding to the transaction flows between transaction nodes in the transaction monitoring link diagram are generated based on the message parsing information in the access relationship table. This includes: determining a preset parsing template that matches each transaction flow based on the message type field associated with each transaction flow in the access relationship table; extracting the parsing field information corresponding to each transaction flow from the access relationship table; and filling the parsing field information into the preset positions of the corresponding preset parsing template to generate message parsing rules for parsing the corresponding transaction flow.

[0008] In another implementation, the generated message parsing rules are associated and bound with the corresponding transaction flows in the transaction monitoring link graph. This includes: assigning a unique edge identifier to each directed edge in the directed structure graph; assigning a unique rule identifier to each generated message parsing rule, and recording or pointing to its corresponding edge identifier in the rule identifier; and writing or mounting the message parsing rules as attribute information into the data structure object corresponding to the directed edge, thus forming a one-to-one correspondence between the transaction flows and message parsing rules in the transaction monitoring link graph.

[0009] In another implementation, the method further includes: associating the field of the IP group in the resource information table with the asset record in the configuration management database; the IP group is encapsulated by multiple IPs of the same function type under the same application name; if changes are detected in the asset information in the configuration management database, the field of the IP group in the resource information table is updated in response to the detected changes, and the IP group information of the associated transaction node in the drawing template data is also updated; when it is detected that the application service has only added an interface or only changed the IP, the IP group information in the resource information table is updated; when it is detected that the service architecture of the application service has changed, the transaction monitoring link diagram generation process is re-executed to generate a new transaction monitoring link diagram and message parsing rules.

[0010] In another implementation, the method further includes: generating an approval request based on the generated message parsing rules and sending the approval request; after the approval request is approved, setting the message parsing rules to an effective state, deploying the message parsing rules to the transaction monitoring system, and associating the transaction monitoring link diagram with the effective message parsing rules.

[0011] According to a second aspect of the present invention, a transaction monitoring link diagram generation and processing apparatus is provided. The apparatus includes: a drawing template construction unit configured to extract a resource information table and an access relationship table from a transaction monitoring drawing template; the resource information table is used to define the attribute information of transaction nodes, including at least node identifier, function type, and network address information; the access relationship includes message parsing information used to define the access relationships between various transaction nodes and associated relationships; each transaction node corresponds to an application service, and each application service includes one or more transaction nodes; a link diagram generation unit configured to construct a directed structure graph between various transaction nodes based on the resource information table and the access relationship table; determine the position of each node in the drawing area of ​​each transaction node in the directed structure graph; perform dynamic topology modeling and automatic layout according to the directed structure graph and the positions of each node to generate a transaction monitoring link diagram; and a parsing unit configured to generate message parsing rules corresponding to the transaction flows between transaction nodes in the transaction monitoring link diagram based on the message parsing information in the access relationship table, and associate and bind the generated message parsing rules with the corresponding transaction flows in the transaction monitoring link diagram.

[0012] According to a third aspect of the present invention, a transaction monitoring link graph generation and processing system is provided, the system being configured to perform a transaction monitoring link graph generation and processing method as described in the first aspect and any possible implementation thereof.

[0013] According to a fourth aspect of the present invention, a computer-readable storage medium is provided, on which instructions are stored, such that when the instructions in the computer-readable storage medium are executed by a processor of an electronic device, the electronic device is able to perform a transaction monitoring link graph generation processing method as described in the first aspect and any possible implementation thereof.

[0014] According to a fifth aspect of the present disclosure, a computer program product is provided, the computer program product including computer instructions, which, when executed on an electronic device, cause the electronic device to perform the transaction monitoring link graph generation processing method of the first aspect and any possible implementation thereof.

[0015] The technical solution provided by the embodiments of the present invention brings at least the following beneficial effects: This application synchronously extracts resource information and access relationships from the same standardized transaction monitoring drawing template, and directly associates the access relationship table with message parsing information, forming a single source of facts shared by the monitoring link diagram and parsing rules, completely eliminating the duplication of information entry and transmission distortion. On this basis, topology modeling and rule generation are performed in parallel based on the same data, compressing the monitoring online cycle from days to minutes, achieving an order-of-magnitude leap in delivery efficiency. More importantly, by strongly associating and binding the automatically generated parsing rules with the corresponding transaction flows in the diagram, the rules become embedded attributes of the graph elements, ensuring consistency between the graph drawing design and rule information configuration process from a mechanism perspective, completely eliminating the risk of mismatch and omission caused by manual mapping, and transforming the monitoring configuration from "post-event recording" to "design as configuration". Any architectural change only requires updating the template and rerunning the process to synchronously and losslessly complete batch refresh, making maintenance costs close to zero. Ultimately, the standardized transaction monitoring diagram template itself becomes a structured carrier of enterprise monitoring knowledge, solidifying the scattered operational experience of individuals into reusable and traceable digital assets, thereby fundamentally improving the level of operational governance and team collaboration efficiency. Therefore, this application fundamentally solves the long-standing systemic problem of the disconnect between diagramming and rule configuration in the field of transaction monitoring by constructing a three-in-one technical architecture of "unified data source, parallel processing, and intelligent binding".

[0016] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and are not intended to limit this disclosure. Attached Figure Description

[0017] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this disclosure and, together with the description, serve to explain the principles of this disclosure, and are not intended to unduly limit this disclosure.

[0018] Figure 1 This is a flowchart illustrating a transaction monitoring link diagram generation process according to an exemplary embodiment; Figure 2 This is a schematic block diagram illustrating a transaction monitoring link according to an exemplary embodiment; Figure 3 This is a block diagram illustrating a transaction monitoring link graph generation and processing apparatus according to an exemplary embodiment; Figure 4 This is a schematic diagram of an electronic device according to an exemplary embodiment. Detailed Implementation

[0019] To enable those skilled in the art to better understand the technical solutions of this disclosure, the technical solutions in the embodiments of this disclosure will be clearly and completely described below with reference to the accompanying drawings.

[0020] It should be noted that the terms "first," "second," etc., used in the specification, claims, and accompanying drawings of this disclosure are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this disclosure described herein can be implemented in orders other than those illustrated or described herein. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this disclosure. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this disclosure as detailed in the appended claims.

[0021] Before providing a detailed description of the transaction monitoring link diagram generation and processing method provided in this application embodiment, let's briefly introduce the application scenarios and implementation environment involved in this application embodiment.

[0022] First, a brief introduction to the application scenarios involved in this application will be given.

[0023] Transaction monitoring is a core component of data center operation and management. As a key means to ensure the business continuity of application systems, it achieves real-time monitoring of online transactions by drawing a transaction monitoring link diagram, parsing network packet fields on a specified link, and combining core monitoring indicators such as transaction volume, transaction response time, transaction success rate, and transaction response rate with alarm rules. Therefore, the completeness, accuracy, and standardization of the transaction monitoring link diagram directly determine the effectiveness of transaction monitoring.

[0024] Drawing a transaction monitoring link diagram requires integrating complex information such as physical architecture diagrams, server IP addresses, destination ports, inter-application access relationships, message formats, and message fields. It must accurately reconstruct the topology and data interaction relationships of key transaction links. However, the generation and management of transaction monitoring link diagrams in the industry still suffer from numerous technical deficiencies, and current technologies are insufficient to meet the needs of efficient and standardized transaction monitoring and maintenance in data centers. Specific problems include the following:

[0025] Firstly, the transaction monitoring link diagrams primarily rely on manual drawing, which suffers from inefficiency, inconsistent standards, and susceptibility to errors. Manual drawing requires operations personnel to integrate multiple types of information, a tedious and time-consuming process. Furthermore, the lack of unified information definitions and drawing standards leads to inconsistent diagram formats and poor readability among different personnel, making cross-team collaboration and subsequent maintenance difficult. Moreover, manual configuration is prone to errors such as missing or incorrect network address information like IP addresses and port numbers, resulting in discrepancies between the monitored link and the actual business link, affecting monitoring accuracy. In addition, when routine changes occur in the system, such as adding interfaces or changing IP addresses, manually maintained link diagrams are difficult to update in a timely manner, easily leading to discrepancies between the diagram and reality, further reducing the reliability of transaction monitoring.

[0026] Secondly, the automatic diagram generation technology in related technologies can only generate broad architecture diagrams, which cannot meet the needs of transaction monitoring for refined and precise link details, and also suffers from layout chaos. Although the related automatic architecture diagram generation technology can achieve the automatic generation of application architecture diagrams, the generated architecture diagrams can only show the overall application framework and cannot refine key transaction links for transaction monitoring scenarios, making it difficult to accurately present the access relationships and data flow between transaction nodes. At the same time, this technology does not consider the scientific calculation of node spacing and position layout during the automatic diagram generation process, but simply associates and splices together the various functional sub-architecture diagrams, which easily causes problems such as overlapping graphical modules and chaotic hierarchy. The generated graphics have poor readability and cannot meet the actual use needs of transaction monitoring.

[0027] Third, the link topology diagram display technology in related technologies suffers from poor scenario adaptability and limited functionality, failing to support a complete transaction monitoring process. This technology is only applicable to distributed transaction link scenarios, lacks compatibility with traditional Socket XML links, and struggles to cover diverse transaction link types within data centers. Furthermore, it can only visualize link topology relationships, cannot configure message parsing rules required for transaction monitoring based on the link diagram, and can only meet the needs of link viewing. It cannot be linked with the core parsing and alarm functions of transaction monitoring, and therefore cannot support an end-to-end transaction monitoring process.

[0028] Fourth, the relevant technologies lack a linkage mechanism between transaction link diagramming and message parsing. The diagramming and parsing processes are disconnected, significantly reducing the efficiency of transaction monitoring configuration. Neither manual diagramming nor existing automated diagramming technologies embed message parsing information during the link diagram generation process. After the link diagram is drawn, maintenance personnel must manually re-examine the message format and parsing fields of the transaction flow, and manually write and configure message parsing rules. This not only increases the number of steps and labor costs but also makes it prone to errors in parsing rule configuration due to information transmission discrepancies. Furthermore, the parsing rules and the link diagram are independent of each other, making it impossible to achieve correlated management, further increasing the operational difficulty of transaction monitoring.

[0029] Fifth, the relevant technologies have not achieved structured association modeling between transaction nodes and application services, resulting in poor adaptability to multiple architecture environments. Application services within data centers are deployed in various architecture environments such as containers, virtual machines, and services connected to ServiceMesh. Application services in different environments contain multiple transaction nodes, and the access relationships between nodes differ. However, the relevant technologies have not established a correspondence between transaction nodes and application services, nor have they considered the link characteristics of different architecture environments. They cannot flexibly construct transaction link topologies that adapt to different environments, making it difficult to meet the transaction monitoring needs of complex business systems.

[0030] In summary, the current generation and management of transaction monitoring link diagrams face multiple technical challenges, including low efficiency and inconsistent standards in manual drawing, poor adaptability and chaotic layout of automatic drawing technology, fragmented drawing and parsing processes, and insufficient adaptability to multiple environments. There is an urgent need for a technical solution that can automate and standardize the generation of transaction monitoring link diagrams and intelligently link with message parsing rules to address the shortcomings of existing technologies and improve the standardization level and operational efficiency of data center transaction monitoring.

[0031] To address the aforementioned issues, this application proposes a transaction monitoring link diagram generation method. The method generates a transaction flow based on the access relationships between nodes, then uses a bidirectional recursive algorithm to calculate the width and position of each node, and finally merges the upstream and downstream tree structure diagrams. This achieves dynamic generation of the transaction monitoring link diagram and reduces the readability differences in monitoring diagrams drawn by different personnel.

[0032] For ease of understanding, the following section provides a detailed description of the transaction monitoring link diagram generation and processing method provided in this application, in conjunction with the accompanying drawings.

[0033] Figure 1 This is a flowchart illustrating a transaction monitoring link graph generation process according to an exemplary embodiment, such as... Figure 1 As shown, the transaction monitoring link diagram generation method includes the following steps.

[0034] S11, extract the resource information table and access relationship table from the transaction monitoring drawing template.

[0035] The resource information table is used to define the attribute information of transaction nodes, including at least node identifier, function type and network address information.

[0036] Node identifiers include the node name.

[0037] The access relationship table includes information used to define the access relationships between various transaction nodes and the associated message parsing information.

[0038] Each transaction node corresponds to an application service, and each application service includes one or more transaction nodes.

[0039] The transaction monitoring drawing template includes mandatory fields in the resource information table and access relationship table, which are defined by the government.

[0040] In some implementations, the specific process of constructing a standardized transaction monitoring drawing template is as follows: Based on the resource information and access relationship information for the target application service input by the user on the transaction monitoring drawing template, template data for the transaction monitoring drawing template is generated. The template data includes table information in the resource information table and the access relationship table.

[0041] The field parameters defined in the access relationship table can include one or more of the following: the position index of the message in the transaction flow, the field name, and the field value matching rules.

[0042] In some implementations, the transaction monitoring link graph supports monitoring configuration of the transaction flow in the graph, and the monitoring configuration metrics include one or more of transaction volume, response time, and success rate.

[0043] The resource information table also includes fields for system identifier, data center, application name, destination port, and whether it is an entry node. The node identifier includes a unique identifier and a parent node identifier; network address information includes IP addresses or IP address ranges and IP groups. Multiple IP addresses of the same function type under the same application name are encapsulated into an IP group, and the IP group is associated with the configuration management database.

[0044] In some implementations, the naming convention for transaction nodes is any of the following: Data Center Load Balancer | IP:PORT, Data Center_POD, Application Name, Data Center_Application Name; the naming convention for IP groups is: System Identifier: Data Center: Application Name: Function Type.

[0045] Specifically, the standardized template for transaction monitoring diagrams includes a resource information table and an access relationship table. The resource information table contains seven required fields: system identifier, data center, application name, function type, IP address, destination port, and whether it is an entry node. Node names and IP groups are automatically generated based on the resource information table, and the IP groups are linked with the configuration association database to achieve automatic updates.

[0046] The access relationship table can only contain external access relationships between applications. Each transaction flow includes access method, message type, transaction code field, return code field, other request fields, and other response fields. S12, construct a directed structure graph between each transaction node based on the resource information table and the access relationship table.

[0047] A directed structure graph is also called a directed acyclic graph. A directed structure graph includes the pointing relationships between transaction nodes and the directed edges between transaction nodes.

[0048] Node information is generated based on the resource information table. Each node contains a unique identifier, such as NodeId, a parent node identifier, such as ParentId, a function type, a node name, a destination IP, and a destination port. A directed acyclic graph is constructed with the entry node as the root node, based on the access relationships within and between applications.

[0049] As one implementation method, in S12 above, a directed structure graph between each transaction node is constructed based on the resource information table and the access relationship table, specifically including the following steps.

[0050] First, the transaction node marked as the entry node in the resource information table is taken as the root node.

[0051] The parent node identifier of the root node is empty.

[0052] There can be one or more root nodes.

[0053] Secondly, based on the pre-defined access relationships within the application service and the inter-application service access relationships between various application services in the access relationship table, the pointing relationships between transaction nodes with related relationships are determined.

[0054] Within each application service, the default access relationship is that load balancing nodes point to application nodes. Inter-application service access relationships are that the transaction node of the source application service points to the transaction node of the destination application service.

[0055] Application services can include source application services and destination application services.

[0056] The transaction node function type of the source application service can be limited to POD, APP, or Client, while the transaction node function type of the destination application service can be limited to ELB, ALB, LB, POD, or APP.

[0057] Third, based on the association between the parent node identifier and the unique identifier in the node identifier, directed edges are generated between transaction nodes that have an association relationship to obtain a directed structure graph.

[0058] The directed structure graph includes a forward tree structure graph from the entry node to the service provider application service, and a reverse tree structure graph with the entry node as the service provider and the consumer application service pointing to the entry node.

[0059] S13, determine the position of each transaction node in the plotting area of ​​the directed structure graph.

[0060] The above step S13 determines the position of each node, specifically including the following steps: starting from each root node distributed at the top of the directed structure graph, perform a recursive layout operation.

[0061] The recursive layout operation includes: first, traversing the directed structure graph from bottom to top to determine the number of child nodes for each transaction node; and recursively calculating the node width of each transaction node based on the node layout type, the number of child nodes for each transaction node, and the spacing between child nodes.

[0062] Secondly, the directed structure graph is traversed from bottom to top to determine the level of each transaction node in the parent-child relationship hierarchy, and the node coordinates of each transaction node are recursively calculated based on the node width and the level to which each transaction node belongs.

[0063] For example, the root node is the first level, the child nodes of the directly associated root node are the second level, and the child nodes of the directly associated second-level child nodes are the third level. That is, the third level is directly related to the child nodes of the second level.

[0064] Specifically, a bidirectional recursive algorithm is adopted. First, the directed structure graph is traversed from bottom to top. The width of each transaction node is determined according to the node layout type, the child nodes of each transaction node and the spacing between the child nodes. Then, the directed structure graph is traversed from top to bottom to assign the coordinates of each transaction node.

[0065] The default value for node width can be defined as 1, and the default value for node spacing can also be defined as 1.

[0066] For example, in a horizontal layout, the current node width = the sum of the widths of its child nodes + (number of child nodes - 1) × the spacing between child nodes. In a vertical layout, the current node width = the width of the largest child node.

[0067] The x-coordinate of the root node is set to half the total width of the root node, the y-coordinate is determined according to the hierarchy, and the x-coordinate of the child node is allocated based on the x-coordinate of the parent node and the width of the child node.

[0068] As one implementation method, after recursively calculating the node coordinates of each transaction node, the following operation can also be performed.

[0069] First, detect whether there are abnormal nodes with overlapping node coordinates and / or overlapping node spacing in each transaction node.

[0070] Secondly, if an abnormal node is detected, the coordinates of any node in the abnormal node are adjusted according to the preset adjustment rules until there is no overlap in node coordinates or node spacing.

[0071] The aforementioned preset adjustment rules include a priority adjustment strategy, which prioritizes moving nodes with lower weights within the conflicting area when coordinate conflicts are detected. Node weights are predefined or dynamically calculated based on node type, business importance, or topology level.

[0072] The above coordinate adjustment operations specifically include one or more of the following fine-tuning actions: 1. Slightly stretch or shrink along the line connecting it to its parent node or center node. 2. Slightly translate in the direction perpendicular to the line connecting it to its parent node or center node. 3. Randomly find a new conflict-free position within a preset radius centered on its current position.

[0073] The coordinates of adjacent abnormal nodes are adjusted using a force-guided incremental adjustment algorithm, as detailed below.

[0074] First, a strong short-term repulsive force is applied between the conflicting node pairs, disrupting their overlapping state.

[0075] Secondly, maintain and fine-tune the existing forces (based on the spring model or the gravity-repulsion model) between all other nodes in the diagram.

[0076] Third, a limited number of iterative calculations are performed to ensure that the overall layout maintains stability as much as possible while resolving local conflicts, thus avoiding drastic reconstructions that could have far-reaching consequences.

[0077] When a conflict involves overlap between a connecting line and a node or other connecting lines, the preset rule is an intelligent wiring rule, and the adjustment method includes the following steps.

[0078] Firstly, new Bézier curve control points are inserted at the critical path points of the connecting line to allow the line to bypass the conflict area.

[0079] Secondly, the straight-line connection was changed to an orthogonal broken-line connection (Manhattan wiring), and the inflection point of the broken line was adjusted to avoid obstacles.

[0080] Furthermore, in some implementations, a recursive and backtracking mechanism for conflict resolution is implemented through the following steps: When a node is moved to resolve its conflict with node A, if this results in a new conflict with node B, then: First, an attempt is made to find another new location for the current node that can simultaneously avoid conflicts with both A and B. If the attempt fails, the process reverts to the state before the move, attempts to move either node A or node B, and restarts the aforementioned adjustment process.

[0081] Furthermore, in some implementations, the user-defined rules interface is implemented through the following steps.

[0082] First, a configuration interface is displayed, allowing users to define prohibited movement, fixed coordinates, or permitted movement ranges for specific types of nodes or connectors.

[0083] Second, during the automatic adjustment process, the system strictly adheres to these user-defined constraints.

[0084] S14. Based on the directed structure graph and the position of each node, perform dynamic topology modeling and automatic layout to generate a transaction monitoring link graph.

[0085] Each transaction node in the transaction monitoring chain graph corresponds to a vertex in the graph, containing visual attributes such as coordinates, size, and style. Each transaction flow corresponds to a directed edge in the graph, pointing from the source node to the destination node.

[0086] The mapping rules in the transaction monitoring link diagram are as follows: each record in the access relationship table generates a transaction flow; each record in the resource information table generates a transaction node.

[0087] S15. Based on the message parsing information in the access relationship table, generate message parsing rules corresponding to the transaction flows between transaction nodes in the transaction monitoring link diagram, and associate and bind the generated message parsing rules with the corresponding transaction flows in the transaction monitoring link diagram.

[0088] Through the above implementation methods, resource information and access relationships are synchronously extracted from the same standardized transaction monitoring drawing template, and the access relationship table is directly associated with message parsing information. This forms a single source of fact shared by the monitoring link diagram and parsing rules, completely eliminating duplicate information entry and transmission distortion. Based on this, topology modeling and rule generation are performed in parallel using the same data, compressing the monitoring deployment cycle from days to minutes, achieving an order-of-magnitude leap in delivery efficiency.

[0089] More importantly, by strongly linking the automatically generated parsing rules with the corresponding transaction flows in the graph, making the rules embedded attributes of the graph elements, the mechanism ensures consistency between the graph drawing design and rule information configuration processes. This completely eliminates the risks of mismatches and omissions caused by manual mapping. Simultaneously, it transforms monitoring configuration from "post-event recording" to "design-as-configuration." Any architectural change only requires updating the template and rerunning the process to synchronously and seamlessly complete batch updates, bringing maintenance costs close to zero. Ultimately, the standardized transaction monitoring graph template itself becomes a structured carrier of enterprise monitoring knowledge, solidifying scattered individual operational experience into reusable and traceable digital assets, fundamentally improving operational governance and team collaboration efficiency.

[0090] Therefore, this application fundamentally solves the long-standing systemic problem of the separation between plotting and rule configuration in the field of transaction monitoring by constructing a three-in-one technical architecture of "unified data source, parallel processing, and intelligent binding".

[0091] As one implementation method, the above-mentioned S15 generates message parsing rules based on the message parsing information in the access relationship table, specifically including the following steps.

[0092] First, based on the message type field associated with each transaction flow in the access relationship table, a preset parsing template matching each transaction flow is determined.

[0093] The pre-defined parsing templates include at least one of the following: XML message parsing template, JSON message parsing template, HTTP message parsing template, and CRPC message parsing template.

[0094] Among them, the XML message parsing template and the JSON message parsing template are field-configurable templates, and their parsing fields are dynamically filled by the transaction code field, return code field, request parsing field and response parsing field defined in the access relationship table; the HTTP message parsing template and the CRPC message parsing template are field-fixed templates, and their parsing fields are preset by the system, so there is no need to read the parsing field information from the access relationship table.

[0095] Secondly, extract the parsed field information corresponding to each transaction flow from the access relationship table.

[0096] Third, the parsed field information is filled into the preset position of the corresponding preset parsing template to generate message parsing rules for parsing the corresponding transaction flow.

[0097] When the message type is HTTP or CRPC, the transaction code and return code fields are fixed values, and do not need to be manually filled in the access relationship table. Correspondingly, when the message type in the access relationship table is HTTP or CRPC, the parsing field reading step is skipped, and the corresponding fixed-field template is directly called to generate the message parsing rules.

[0098] When the message type is in other formats, the transaction code field, return code field, other request fields and other response fields in the access relationship table must be filled in manually.

[0099] The parsed field information includes at least one or more of the following: transaction code field name, used to identify the message location path of the transaction type; return code field name, used to identify the message location path of the transaction processing result; the business field name to be parsed in the request message and its location path; and the business field name to be parsed in the response message and its location path.

[0100] As another implementation method, the generated message parsing rules in S15 above are associated and bound with the corresponding transaction flow in the transaction monitoring link diagram, specifically including the following steps.

[0101] First, assign a unique edge identifier to each directed edge in the directed structure graph.

[0102] Secondly, a unique rule identifier is assigned to each generated message parsing rule, and the rule identifier records or points to its corresponding edge identifier.

[0103] Third, the message parsing rules are written as attribute information into or mounted into the data structure object corresponding to the directed edge, forming a one-to-one correspondence between the transaction flow and the message parsing rules in the transaction monitoring link diagram.

[0104] The above-mentioned writing or mounting of message parsing rules as attribute information to the data structure object corresponding to the directed edge specifically includes: in the internal data model of the transaction monitoring link graph, extending the rule attribute field for the directed edge object representing the transaction flow; assigning the serialized data or storage address of the message parsing rule to the rule attribute field; when the transaction monitoring link graph is loaded or rendered, the directed edge object holds the access handle of the message parsing rule.

[0105] Furthermore, after generating the message parsing rules corresponding to the transaction flows of each transaction node in the transaction monitoring link diagram, the following steps can be performed: generate the effective scope of the message parsing rules based on the network address information and port information of the destination node corresponding to the transaction flow.

[0106] The scope of application must include at least: destination IP address, destination port number, and protocol type. The destination IP address is obtained from the list of network addresses corresponding to the IP group identifier associated with the destination node in the resource information table.

[0107] An IP address (Internet Protocol Address) is a digital identifier assigned to a device in a network, used to locate and address devices within the network.

[0108] Furthermore, after generating the message parsing rules corresponding to the transaction flows of each transaction node in the transaction monitoring link diagram, the following steps are also included.

[0109] First, the generated message parsing rules are encapsulated into configuration instructions in a preset format.

[0110] Secondly, the rule deployment interface of the transaction monitoring platform is called to send the configuration instructions to the transaction monitoring platform.

[0111] Third, receive deployment status information returned by the transaction monitoring platform, and update the display status of the corresponding transaction flow in the transaction monitoring link diagram according to the deployment status information.

[0112] Alternatively, to ensure that the generated monitoring configuration has the ability to adapt to the continuous evolution of the infrastructure, the following steps can also be performed.

[0113] First, the fields belonging to the IP group in the resource information table are associated with the asset records in the configuration management database.

[0114] An IP group is a collection of multiple IPs of the same function type under the same application name.

[0115] Secondly, if changes occur to asset information in the monitoring configuration management database, the system will update the field of the IP group in the resource information table and update the IP group information of the associated transaction node in the drawing template data in response to the detected changes.

[0116] Third, when it is detected that the application service has only added a new interface or only changed the IP, update the IP group information in the resource information table.

[0117] Fourth, when a change in the service architecture of the application service is detected, the transaction monitoring link diagram generation process is re-executed to generate a new transaction monitoring link diagram and message parsing rules.

[0118] Optionally, in order to form a closed-loop management mechanism of "parsing rule generation - approval - effectiveness - link binding", which not only makes up for the rule control loopholes without approval links, but also realizes the automated connection from generation to implementation of parsing rules, and strengthens the strong correlation between transaction monitoring link diagram and effective parsing rules, the approval flow control of message parsing rules and the automated deployment of rules and the linkage of link diagrams are realized through the following steps.

[0119] First, an approval request is generated based on the generated message parsing rules, and then the approval request is sent.

[0120] Secondly, after the approval request is approved, the message parsing rule is set to the effective state, the message parsing rule is deployed to the transaction monitoring system, and the transaction monitoring link diagram is associated with the effective message parsing rule.

[0121] In some implementations, the functional types include business initiator (Client), load balancer (ELB / ALB / LB), and application (POD / APP); the application environment corresponding to the application service includes container environment, virtual environment, and service environment accessing ServiceMesh. The internal transaction node access relationship of the application service in different application environments is preset at the code level and does not need to be filled in the access relationship table.

[0122] Specifically, after the transaction monitoring graph is generated, it is necessary to parse the important fields in the messages of each transaction flow in order to obtain the transaction traffic and monitor it. The transaction monitoring parsing process also extracts the transaction flow, message format, and parsed fields from the application access relationship in the standardized template; when the access method equals the function type, the destination IP and destination port of the destination application are obtained. A full parsing is performed according to the message format using the destination IP and destination port of the service provider application, without restricting the source IP. This method supports multiple message formats, including: XML, HTTP, HTTP-XML, HTTP-JSON, JSON, and CRPC protocol messages. The transaction monitoring platform has a built-in universal parsing rule template that can automatically adapt to different message formats. After the parsing rules are generated, they are automatically submitted for leadership approval. After the process is approved, the parsing rules automatically take effect, realizing integrated process management of monitoring graphing and rule parsing. This process reduces the risk of manual changes, and the parsing process based on standardized templates also ensures consistency.

[0123] In addition, the transaction code, return code, and other parsing fields for HTTP and CRPC message formats are fixed, and it is not necessary to fill in the transaction code, return code, other request fields, and response fields. However, for other formats, it is necessary to fill in the transaction code, return code, other request fields, and response fields.

[0124] After completing the transaction monitoring graph drawing and message parsing, core monitoring indicators such as transaction volume, transaction response time, transaction success rate, and transaction response rate can be configured on the transaction flow. Combined with flexible and varied alarm rules, real-time monitoring of online transactions can be achieved.

[0125] In some implementations, the generated transaction monitoring link diagram supports export functionality, with export formats including PNG, SVG, PDF, and editable topology files. The topology files can be re-imported into the transaction monitoring drawing template for further editing.

[0126] Optionally, after the directed graph is constructed, a redundant node removal step is also included: identifying and deleting isolated nodes that have no actual transaction flow association and do not affect topological connectivity, thereby optimizing the simplicity of the link graph.

[0127] As one implementation method, combined with Figure 2 The following is an explanation of the process for generating the transaction monitoring link diagram.

[0128] I. For example Figure 2 The diagram shows the monitoring links for three types of transaction chains: container environment, existing virtual environment, and service chain connected to ServiceMesh.

[0129] In the transaction chain monitoring diagram in the container environment, each application node contains ALB / ELB and container POD (POD is not a specific number of IPs but a large pod segment, which is generally allocated resources according to subnet mask 0 / 24). ALB is the load balancer of Lingque Cloud, and ELB is the load balancer of FullStack Cloud. The application node is an ELB / ALB-->POD link.

[0130] In the transaction chain monitoring diagram in the virtual environment, there are load balancers (LB) and applications (APP) (here, APP may refer to WEB server, PRE server, nginx service, Tomcat service, etc.), and each node is an APP.

[0131] In the transaction chain monitoring diagram of services connected to ServiceMesh, which is mainly used in container environments, there is no need for load balancing between services. Therefore, when the pod segment of service A accesses the pod segment of service B, the pod segment of service A corresponds to the pod segment of service B.

[0132] Therefore, the access relationship table only needs to be filled in for external access relationships between applications, and does not need to be filled in for internal access relationships within the application (internal relationships are standard and have already been set up at the code level). When a new system goes live, once the diagram is drawn according to the predefined rule template, the application layer of this architecture will not be significantly changed in the short term. During the normal deployment process, when new interfaces or transactions are added, the architecture remains unchanged, and the access relationships between services also remain unchanged, so this diagram does not need to be modified.

[0133] Second, transaction monitoring is obtained through network traffic bypass mirroring. According to current requirements, the service provider system performs full resolution based on the destination IP and destination PORT, without restricting the source IP. Therefore, if a new consumer or service provider is added to the system, but the destination IP and destination port remain unchanged, there is no need to repeat the resolution.

[0134] Third, when the system's load balancer IP or application IP is updated, and the system architecture remains unchanged, there is no need to redraw the diagram (the original diagram is automatically generated with IP groups configured on each node, rather than specific IPs, so that when the IP changes, only the IP groups need to be updated). The existing code supports generating a set of IP groups under the same functional type of load balancer LB / ELB / ALB and application APP / POD, and then linking with CMDB to update the IP groups periodically.

[0135] Fourth, only when the system architecture changes, such as from a virtual environment to a container environment, does its link diagram and resolution rules need to be updated. They can be automatically generated according to the standard template, and the resolution rules will also be automatically generated.

[0136] To achieve the above functions, the transaction monitoring link diagram generation and processing apparatus includes hardware structures and / or software modules corresponding to the execution of each function. Those skilled in the art will readily recognize that, based on the algorithmic steps of the examples described in conjunction with the embodiments disclosed herein, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed in hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0137] This disclosure also provides an embodiment such as Figure 3 The transaction monitoring link diagram generation and processing device shown includes the following units: drawing template construction unit 31, link diagram generation unit 32, and parsing unit 33.

[0138] The drawing template construction unit 31 is configured to extract a resource information table and an access relationship table from the transaction monitoring drawing template. The resource information table is used to define the attribute information of the transaction nodes, including at least the node identifier, function type and network address information. The access relationship includes the access relationship between each transaction node and the associated message parsing information. Each transaction node corresponds to an application service, and each application service includes one or more transaction nodes.

[0139] The link diagram generation unit 32 is configured to construct a directed structure diagram between various transaction nodes based on the resource information table and the access relationship table; determine the position of each transaction node in the drawing area in the directed structure diagram; and perform dynamic topology modeling and automatic layout according to the directed structure diagram and the positions of each node to generate a transaction monitoring link diagram.

[0140] The parsing unit 33 is configured to generate message parsing rules corresponding to the transaction flow between transaction nodes in the transaction monitoring link diagram based on the message parsing information in the access relationship table, and associate and bind the generated message parsing rules with the corresponding transaction flow in the transaction monitoring link diagram.

[0141] In one implementation, the link graph generation unit 32 is specifically configured to: use the transaction node marked as the entry node in the resource information table as the root node; wherein the parent node identifier of the root node is empty; determine the pointing relationship between transaction nodes with an association relationship based on the preset access relationship within the application service and the inter-application service access relationship between various application services in the access relationship table; the preset access relationship within the application service is that the load balancing node points to the application node, and the inter-application service access relationship is that the transaction node of the source application service points to the transaction node of the destination application service; generate directed edges between transaction nodes with an association relationship according to the association relationship between the parent node identifier and the unique identifier in the node identifier, so as to obtain a directed structure graph; the directed structure graph includes a forward tree structure graph of accessing the service provider application service from the entry node, and a reverse tree structure graph with the entry node as the service provider and the consumer application service pointing to the entry node.

[0142] In another implementation, the link graph generation unit 32 is specifically configured to: perform a recursive layout operation starting from each root node distributed at the top of the directed structure graph; wherein the recursive layout operation includes: traversing the directed structure graph from bottom to top to determine the number of child nodes of each transaction node; and recursively calculating the node width of each transaction node according to the node layout type, the number of child nodes of each transaction node and the spacing between child nodes; and traversing the directed structure graph from bottom to top to determine the level to which each transaction node belongs in the parent-child relationship hierarchy, and recursively calculating the node coordinates of each transaction node according to the node width of each transaction node and the level to which each transaction node belongs.

[0143] In another embodiment, the link graph generation unit 32 is further configured to: after recursively calculating the node coordinate positions of each transaction node, detect whether there are any abnormal nodes with overlapping node coordinates and / or overlapping node spacing in each transaction node; if an abnormal node is detected, adjust the coordinates of any node in the abnormal node according to a preset adjustment rule until there is no overlap of node coordinates or overlapping node spacing in the abnormal node.

[0144] In another implementation, the parsing unit 33 is specifically configured to: determine a preset parsing template that matches each transaction flow based on the message type field associated with each transaction flow in the access relationship table; extract the parsing field information corresponding to each transaction flow from the access relationship table; fill the parsing field information into the preset position of the corresponding preset parsing template, and generate a message parsing rule for parsing the corresponding transaction flow.

[0145] In another implementation, the parsing unit 33 is specifically configured to: assign a unique edge identifier to each directed edge in the directed structure graph; assign a unique rule identifier to each generated message parsing rule, and record or point to its corresponding edge identifier in the rule identifier; write or mount the message parsing rule as attribute information to the data structure object corresponding to the directed edge, forming a one-to-one correspondence between the transaction flow and the message parsing rule in the transaction monitoring link graph.

[0146] In another implementation, the drawing template construction unit 31 is further configured to: associate the field of the IP group to which the resource information table belongs with the asset record in the configuration management database; the IP group is a group of multiple IPs of the same function type under the same application name; if the asset information in the configuration management database changes, in response to the detected change, update the field of the IP group to which the resource information table belongs, and update the IP group information of the transaction node associated in the drawing template data; when it is detected that the application service only adds an interface or only changes the IP, update the IP group information in the resource information table; when it is detected that the service architecture of the application service changes, re-trigger the execution of the transaction monitoring link diagram generation process to generate a new transaction monitoring link diagram and message parsing rules.

[0147] In another implementation, the parsing unit 33 is further configured to: generate an approval request based on the generated message parsing rules and send the approval request; after the approval request is approved, set the message parsing rules to an effective state, deploy the message parsing rules to the transaction monitoring system, and associate the transaction monitoring link diagram with the effective message parsing rules.

[0148] Regarding the apparatus in the above embodiments, the specific manner in which each unit module performs its operations has been described in detail in the embodiments related to the method, and will not be elaborated upon here.

[0149] Figure 4 This is a schematic diagram of an electronic device provided in this application. (For example...) Figure 4 The electronic device 50 may include at least one processor 501 and a memory 503 for storing processor-executable instructions. The processor 501 is configured to execute the instructions in the memory 503 to implement the transaction monitoring link graph generation processing method in the following embodiments.

[0150] In addition, electronic device 50 may also include communication bus 502, at least one communication interface 504, input device 506 and output device 505.

[0151] The processor 501 may be a processor (central processing unit, CPU), a microprocessor unit, an ASIC, or one or more integrated circuits for controlling the execution of the program of the present application.

[0152] The communication bus 502 may include a path for transmitting information between the aforementioned components.

[0153] Communication interface 504 uses any transceiver-like device for communicating with other devices or communication networks, such as Ethernet, radio access network (RAN), wireless local area networks (WLAN), etc.

[0154] Input device 506 is used to receive input signals and output device 505 is used to output signals.

[0155] Memory 503 may be a read-only memory (ROM) or other type of static storage device capable of storing static information and instructions, random access memory (RAM) or other type of dynamic storage device capable of storing information and instructions, or electrically erasable programmable read-only memory (EEPROM), compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compressed discs, laser discs, optical discs, digital universal discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or any other medium capable of carrying or storing desired program code in the form of instructions or data structures and accessible by a computer, but not limited thereto. Memory may exist independently and be connected to the processing unit via a bus. Memory may also be integrated with the processing unit.

[0156] The memory 503 stores instructions for executing the scheme of this application, and the processor 501 controls the execution. The processor 501 executes the instructions stored in the memory 503 to implement the functions of the method of this application.

[0157] In a specific implementation, as one example, the processor 501 may include one or more CPUs, for example... Figure 4 CPU0 and CPU1 in the CPU.

[0158] In a specific implementation, as one example, electronic device 50 may include multiple processors, such as... Figure 4 Processors 501 and 507 are mentioned. Each of these processors can be a single-core (single-CPU) processor or a multi-core (multi-CPU) processor. A processor here can refer to one or more devices, circuits, and / or processing cores used to process data (such as computer program instructions).

[0159] The electronic device is as follows Figure 4 The diagram includes a processor 501 and a memory 503 for storing executable instructions of the processor 501. The processor 501 is configured to execute the executable instructions to implement the transaction monitoring link graph generation processing method as described in any of the possible embodiments above. Furthermore, it achieves the same technical effect, and to avoid repetition, will not be elaborated further here.

[0160] This application also provides a computer-readable storage medium. When the instructions in the computer-readable storage medium are executed by the processor of a transaction monitoring link diagram generation processing device or electronic device, the transaction monitoring link diagram generation processing device or electronic device is able to perform the transaction monitoring link diagram generation processing method as described in any of the above possible embodiments. And it can achieve the same technical effect; to avoid repetition, it will not be described again here.

[0161] This application also provides a computer program product, including a computer program or instructions, which are executed by a processor as described in any of the possible implementations above for a transaction monitoring link graph generation processing method. This achieves the same technical effect, and to avoid repetition, it will not be described again here.

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

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

Claims

1. A method for generating and processing a transaction monitoring link diagram, characterized in that, The method includes: Extract the resource information table and access relationship table from the transaction monitoring drawing template; the resource information table is used to define the attribute information of the transaction node, including at least the node identifier, function type and network address information; the access relationship includes the access relationship between each transaction node and the associated message parsing information; each transaction node corresponds to an application service, and each application service includes one or more transaction nodes; Based on the resource information table and access relationship table, construct a directed structure graph between the various transaction nodes; Determine the position of each transaction node in the drawing area of ​​the directed structure graph; Based on the directed structure graph and the positions of each node, dynamic topology modeling and automatic layout are performed to generate a transaction monitoring link graph; Based on the message parsing information in the access relationship table, a message parsing rule corresponding to the transaction flow between transaction nodes in the transaction monitoring link diagram is generated, and the generated message parsing rule is associated and bound with the corresponding transaction flow in the transaction monitoring link diagram.

2. The transaction monitoring link diagram generation and processing method according to claim 1, characterized in that, The step of constructing a directed structure graph between various transaction nodes based on the resource information table and the access relationship table includes: The transaction node marked as the entry node in the resource information table is taken as the root node; wherein, the parent node identifier of the root node is empty; Based on the pre-defined access relationships within the application service and the inter-application service access relationships between various application services in the access relationship table, the pointing relationships between transaction nodes with related relationships are determined; the pre-defined access relationships within the application service are load balancing nodes pointing to application nodes, and the inter-application service access relationships are transaction nodes of the source application service pointing to transaction nodes of the destination application service. Based on the association between the parent node identifier and the unique identifier in the node identifier, directed edges are generated between transaction nodes that have an association relationship to obtain the directed structure graph; the directed structure graph includes a forward tree structure graph from the entry node to the service provider application service, and a reverse tree structure graph with the entry node as the service provider and the consumer application service pointing to the entry node.

3. The transaction monitoring link diagram generation and processing method according to claim 2, characterized in that, Determining the position of each transaction node in the drawing area of ​​the directed graph specifically includes: Starting from the root nodes distributed at the top of the directed structure graph, a recursive layout operation is performed. This recursive layout operation includes: traversing the directed structure graph from bottom to top to determine the number of child nodes for each transaction node; recursively calculating the node width of each transaction node based on the node layout type, the number of child nodes for each transaction node, and the spacing between child nodes; and traversing the directed structure graph from bottom to top to determine the level of each transaction node in the parent-child relationship hierarchy, and recursively calculating the node coordinates of each transaction node based on the node width and the level to which each transaction node belongs.

4. The transaction monitoring link diagram generation and processing method according to claim 3, characterized in that, After recursively calculating the node coordinates of each transaction node, the method further includes: Detect whether there are any abnormal nodes with overlapping node coordinates and / or overlapping node spacing among the various transaction nodes; If the abnormal node is detected, the coordinates of any of the abnormal nodes are adjusted according to the preset adjustment rules until there is no overlap in node coordinates or node spacing between the abnormal nodes.

5. The transaction monitoring link diagram generation and processing method according to claim 3, characterized in that, The step of generating message parsing rules corresponding to the transaction flow between transaction nodes in the transaction monitoring link diagram based on the message parsing information in the access relationship table includes: Based on the message type field associated with each transaction flow in the access relationship table, determine the preset parsing template that matches each transaction flow; Extract the parsed field information corresponding to each transaction flow from the access relationship table; The parsed field information is filled into the preset position of the corresponding preset parsing template to generate the message parsing rule for parsing the corresponding transaction flow.

6. The transaction monitoring link diagram generation and processing method according to claim 5, characterized in that, The step of associating and binding the generated message parsing rules with the corresponding transaction flows in the transaction monitoring link diagram includes: Assign a unique edge identifier to each directed edge in the directed structure graph; Assign a unique rule identifier to each of the generated message parsing rules, and record or point to the corresponding edge identifier in the rule identifier; The message parsing rules are written as attribute information into or mounted into the data structure object corresponding to the directed edge, forming a one-to-one correspondence between the transaction flow and the message parsing rules in the transaction monitoring link diagram.

7. The transaction monitoring link diagram generation and processing method according to any one of claims 1 to 6, characterized in that, The method further includes: The fields belonging to the IP group in the resource information table are associated with the asset records in the configuration management database; the IP group is a group of multiple IPs of the same function type under the same application name. If changes are detected in the asset information in the configuration management database, the field of the IP group to which the resource information belongs is updated in response to the detected change, and the IP group information of the transaction node associated in the drawing template data is also updated. When it is detected that the application service has only added a new interface or only changed the IP, the IP group information in the resource information table is updated; When a change in the service architecture of an application service is detected, the transaction monitoring link diagram generation process is re-executed to generate a new transaction monitoring link diagram and message parsing rules.

8. The transaction monitoring link diagram generation and processing method according to any one of claims 1 to 6, characterized in that, The method further includes: An approval request is generated based on the generated message parsing rules, and the approval request is sent. After the approval request is approved, the message parsing rule is set to the effective state, the message parsing rule is deployed to the transaction monitoring system, and the transaction monitoring link diagram is associated with the effective message parsing rule.

9. A transaction monitoring link graph generation and processing apparatus for performing the transaction monitoring link graph generation and processing method as described in any one of claims 1 to 8, characterized in that, The device includes: The drawing template construction unit is configured to extract a resource information table and an access relationship table from the transaction monitoring drawing template; the resource information table is used to define the attribute information of the transaction nodes, including at least node identifier, function type and network address information; the access relationship includes information used to define the access relationship between each transaction node and the associated message parsing information; each transaction node corresponds to an application service, and each application service includes one or more transaction nodes; The link diagram generation unit is configured to construct a directed structure diagram between various transaction nodes based on the resource information table and the access relationship table; determine the position of each node in the drawing area for each transaction node in the directed structure diagram; and perform dynamic topology modeling and automatic layout according to the directed structure diagram and the positions of each node to generate a transaction monitoring link diagram. The parsing unit is configured to generate a message parsing rule corresponding to the transaction flow between transaction nodes in the transaction monitoring link diagram based on the message parsing information in the access relationship table, and to associate and bind the generated message parsing rule with the corresponding transaction flow in the transaction monitoring link diagram.

10. A transaction monitoring link diagram generation and processing system, characterized in that, It is configured to perform the transaction monitoring link graph generation processing method as described in any one of claims 1-8.

Images