CN111784516A - Method and device for determining service path and electronic equipment - Google Patents
Method and device for determining service path and electronic equipment Download PDFInfo
- Publication number
- CN111784516A CN111784516A CN202010545849.2A CN202010545849A CN111784516A CN 111784516 A CN111784516 A CN 111784516A CN 202010545849 A CN202010545849 A CN 202010545849A CN 111784516 A CN111784516 A CN 111784516A
- Authority
- CN
- China
- Prior art keywords
- transaction
- processing node
- field
- matching
- code
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 238000000034 method Methods 0.000 title claims abstract description 53
- 238000012545 processing Methods 0.000 claims abstract description 242
- 230000004044 response Effects 0.000 claims description 13
- 238000013507 mapping Methods 0.000 claims description 11
- 238000007619 statistical method Methods 0.000 claims description 6
- 238000004590 computer program Methods 0.000 claims description 5
- 230000008569 process Effects 0.000 description 15
- 238000010586 diagram Methods 0.000 description 12
- 238000004891 communication Methods 0.000 description 8
- 238000012544 monitoring process Methods 0.000 description 6
- 238000011161 development Methods 0.000 description 4
- 230000000694 effects Effects 0.000 description 4
- 238000004458 analytical method Methods 0.000 description 3
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 238000004519 manufacturing process Methods 0.000 description 3
- 230000000007 visual effect Effects 0.000 description 3
- 238000005516 engineering process Methods 0.000 description 2
- 238000012423 maintenance Methods 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000012546 transfer Methods 0.000 description 2
- 238000013459 approach Methods 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 238000000802 evaporation-induced self-assembly Methods 0.000 description 1
- 230000006870 function Effects 0.000 description 1
- 230000036541 health Effects 0.000 description 1
- 230000000977 initiatory effect Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
- G06Q40/04—Trading; Exchange, e.g. stocks, commodities, derivatives or currency exchange
Landscapes
- Business, Economics & Management (AREA)
- Accounting & Taxation (AREA)
- Finance (AREA)
- Engineering & Computer Science (AREA)
- Development Economics (AREA)
- Economics (AREA)
- Marketing (AREA)
- Strategic Management (AREA)
- Technology Law (AREA)
- Physics & Mathematics (AREA)
- General Business, Economics & Management (AREA)
- General Physics & Mathematics (AREA)
- Theoretical Computer Science (AREA)
- Debugging And Monitoring (AREA)
- Computer And Data Communications (AREA)
Abstract
The invention provides a method and a device for determining a service path and electronic equipment, which relate to the technical field of computers and comprise the following steps: determining a plurality of transaction processing nodes for processing a target service; determining transaction data of transaction operation corresponding to each transaction processing node; and matching the first transaction operation entering each transaction processing node with the second transaction operation sent by each transaction processing node according to the transaction characteristic field in the transaction data, so as to obtain a target service transaction tracking path. The invention can reduce the requirement of the matching code when matching the first transaction operation entering each transaction processing node with the second transaction operation sent by each transaction processing node based on the transaction data, thereby providing a powerful help for timely discovering and positioning application performance faults, and further relieving the technical problem of poor path tracking performance caused by non-uniform transaction serial numbers in the traditional transaction path tracking method.
Description
Technical Field
The present invention relates to the field of computer technologies, and in particular, to a method and an apparatus for determining a service path, and an electronic device.
Background
With the rapid development of new services and new technologies, monitoring the health condition of the whole transaction service process and rapidly finding and positioning problems are the key of the current operation and maintenance work. In the scheme of application performance monitoring, transaction tracking is a leading and popular technical means.
The existing transaction tracking method mainly obtains the transaction information of each section of transaction processing link through analyzing a transaction flow log or a network data packet, and forms a transaction path diagram according to a network access relation. On the basis, a transaction serial number in a network session or a log is extracted, and a transaction is tracked from an initiating end to a final processing link so as to find a fault point or a performance bottleneck in the whole process. However, it is the actual situation that the transaction processing link does not have a uniform transaction serial number when the system modules are crossed. This requires an overall change in the production environment for such monitoring requirements, but this approach is risky and not cost effective.
Disclosure of Invention
In view of this, the present invention aims to provide a method, an apparatus, and an electronic device for determining a service path, which can reduce the requirement of a matching code when a first transaction operation entering each transaction processing node is matched with a second transaction operation sent by each transaction processing node, thereby providing a powerful help for timely discovering and locating an application performance fault.
In a first aspect, an embodiment of the present invention provides a method for determining a service path, including: determining a plurality of transaction processing nodes for processing a target service; determining transaction data of transaction operation corresponding to each transaction processing node; the transaction operation comprises a first transaction operation entering a current transaction processing node and a second transaction operation sent by the current transaction processing node, and the transaction data comprises each network field and each transaction characteristic field; matching the first transaction operation entering each transaction processing node and the second transaction operation sent by each transaction processing node according to the transaction characteristic field in the transaction data so as to obtain a target service transaction tracking path, wherein the transaction characteristic field comprises at least one of the following fields: user ID, subject ID, and type ID.
Further, determining transaction data for the transaction operation corresponding to each transaction processing node comprises: sending a calling request to a target database; the calling request is used for calling the transaction data of each transaction processing node; and acquiring response information which carries the transaction data and is fed back by the target database based on the calling request.
Further, determining the transaction data of the transaction operation corresponding to each transaction processing node further includes: obtaining target data of at least one service, wherein the target data comprises: network traffic data packets, or transaction journal data; and analyzing the network flow data packet to obtain transaction data of the transaction operation corresponding to each transaction processing node.
Further, the matching operation of the first transaction operation entering each transaction processing node and the second transaction operation sent by each transaction processing node according to the transaction characteristic field in the transaction data comprises: determining a first transaction operation of each transaction processing node and a transaction matching code of a second transaction operation sent by each transaction processing node to obtain a first transaction matching code and a second transaction matching code; and matching the first transaction operation with the second transaction operation according to the first transaction matching code and the second transaction matching code.
Further, the first and second transaction match codes include any of: the first transaction matching code and the second transaction matching code are fields with the same or different field names and the same field contents; or, the first transaction match code includes at least one first field, the second transaction match code includes at least one second field, and the field content of the at least one first field and the field content of the at least one second field match; or the first transaction matching code is a partial field in a first field, and the second transaction matching code is a second field, wherein the partial field in the first field and the field content of the second field are the same.
Further, the first transaction operation is plural, and the second transaction operation is plural; matching the first transaction operation and the second transaction operation according to the first transaction matching code and the second transaction matching code comprises: for each first transaction match code, determining a second transaction match code among the plurality of second transaction match codes that is the same as the current first transaction match code; if the same second transaction matching code is determined, establishing an incidence relation between the current first transaction matching code and the matched same second transaction matching code; and if the same second transaction matching code is not determined, determining that the service transaction tracking path corresponding to the current first transaction matching code is finished.
Further, determining a transaction match code for the first transaction operation of each transaction processing node and the second transaction operation issued by each transaction processing node comprises: searching node attribute information of each transaction processing node in a target mapping table; and determining the first transaction operation of each transaction processing node and the transaction matching code of the second transaction operation sent by each transaction processing node according to the node attribute information.
Further, the method further comprises: performing statistical analysis on the target service transaction tracking path to obtain transaction processing performance information of the target service transaction tracking path at each transaction processing node, wherein the transaction processing performance information includes at least one of the following information: the target service transaction tracking path comprises transaction processing nodes, transaction processing time of each transaction processing node, transaction field information of transaction data of each transaction processing node and response state of each transaction processing node.
In a second aspect, an embodiment of the present invention further provides a device for determining a service path, where the device includes: a first determination unit for determining a plurality of transaction processing nodes for processing a target service; the second determining unit is used for determining the transaction data of the transaction operation corresponding to each transaction processing node; the transaction operation comprises a first transaction operation entering a current transaction processing node and a second transaction operation sent by the current transaction processing node, and the transaction data comprises each network field and each transaction characteristic field; a matching unit, configured to perform matching operation on a first transaction operation entering each transaction processing node and a second transaction operation sent by each transaction processing node according to a transaction characteristic field in the transaction data, so as to obtain a target service transaction tracking path, where the transaction characteristic field includes at least one of: user ID, subject ID, and type ID.
In a third aspect, an embodiment of the present invention provides an electronic device, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor, where the processor implements the steps of the method in any one of the above first aspects when executing the computer program.
In the embodiment of the invention, a plurality of transaction processing nodes for processing target services are determined firstly; then determining transaction data of transaction operation corresponding to each transaction processing node; and finally, matching the first transaction operation entering each transaction processing node with the second transaction operation sent by each transaction processing node according to the transaction characteristic field in the transaction data, so as to obtain a target service transaction tracking path. In this embodiment, by means of matching the first transaction operation and the second transaction operation through the transaction characteristic field, when the first transaction operation entering each transaction processing node and the second transaction operation sent by each transaction processing node are matched based on transaction data, the requirement of the matching code can be reduced, and further a powerful help is provided for timely discovering and positioning application performance faults, so that the technical problem of poor path tracking performance caused by non-uniform transaction serial numbers in the conventional transaction path tracking method is solved.
Additional features and advantages of the invention will be set forth in the description which follows, and in part will be obvious from the description, or may be learned by practice of the invention. The objectives and other advantages of the invention will be realized and attained by the structure particularly pointed out in the written description and claims hereof as well as the appended drawings.
In order to make the aforementioned and other objects, features and advantages of the present invention comprehensible, preferred embodiments accompanied with figures are described in detail below.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, and it is obvious that the drawings in the following description are some embodiments of the present invention, and other drawings can be obtained by those skilled in the art without creative efforts.
Fig. 1 is a flowchart of a method for determining a service path according to an embodiment of the present invention;
FIG. 2 is a schematic diagram of transaction data provided by an embodiment of the present invention;
fig. 3 is a schematic diagram of a transaction tracking path of a mobile banking system according to an embodiment of the present invention;
fig. 4 is a schematic diagram of a business transaction tracking path according to an embodiment of the present invention;
fig. 5 is a waterfall model display effect diagram of a business transaction tracking path according to an embodiment of the present invention;
fig. 6 is a schematic diagram of a service path determining apparatus according to an embodiment of the present invention;
fig. 7 is a schematic diagram of an electronic device according to an embodiment of the present invention.
Detailed Description
To make the objects, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings, and it is apparent that the described embodiments are some, but not all embodiments of the present invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
The first embodiment is as follows:
in accordance with an embodiment of the present invention, there is provided an embodiment of a method for determining a traffic path, it should be noted that the steps illustrated in the flowchart of the accompanying drawings may be performed in a computer system such as a set of computer executable instructions, and that while a logical order is illustrated in the flowchart, in some cases the steps illustrated or described may be performed in an order different than that herein.
Fig. 1 is a flowchart of a method for determining a traffic path according to an embodiment of the present invention, as shown in fig. 1, the method includes the following steps:
step S102, a plurality of transaction processing nodes for processing the target service are determined.
Target service: one transaction for the end user includes all transaction operations from the originating end to the final transaction processing segment. For example: a transfer, a deposit, etc.
The transaction processing node: is an abstract concept and specifically refers to each transaction processing link. The transaction processing node not only corresponds to one or a group of IP addresses or ports, but can also be defined by transaction characteristics. Such as a certain transaction type code or channel number.
Step S104, determining transaction data of the transaction operation corresponding to each transaction processing node; the transaction operation comprises a first transaction operation entering the current transaction processing node and a second transaction operation sent by the current transaction processing node, and the transaction data comprises each network field and each transaction characteristic field.
And (3) transaction operation: a request and corresponding response occurs between two processing links. For example, in a transfer process, a request of the WEB server to the APP server, whether a response is received or not, is counted as a transaction operation.
FIG. 2 is a diagram of transaction data including various network fields including IP and port, and various transaction characteristics fields including transaction parameters and service return code. When a target transaction is processed in the background, the target transaction is composed of all transaction data, and the number of fields and the field value of each transaction data may be different.
Step S106, matching the first transaction operation entering each transaction processing node and the second transaction operation sent by each transaction processing node according to the transaction characteristic field in the transaction data, so as to obtain a target service transaction tracking path, wherein the transaction characteristic field comprises at least one of the following fields: user ID, subject ID, and type ID.
It should be noted that, in the present application, the user ID is a field userid, the subject ID is a field tid, and the type ID is a field typeid. Target business transaction tracking path: a target business is composed of a plurality of transaction operations, and all transaction processing links passed by the transaction operations form a target business transaction tracking path.
As shown in fig. 3, a service path of the mobile banking is presented, and a transaction is initiated from a WEB node of the mobile banking, passes through each logic node, and finally reaches a core, a DB node, and the like. As shown in fig. 3, the WEB of the mobile phone bank is a logical node, and the APP of the mobile phone bank, the F5 of the mobile phone bank, and the like are all logical nodes. It should be noted that, in the present application, a logical node is a transaction processing node in the present application. The logical nodes are different from the physical nodes, and in the application, the logical nodes are abstract concepts and specifically refer to each transaction processing link. The transaction processing node not only corresponds to one or a group of IP addresses or ports, but can also be defined by transaction characteristics.
For the transaction processing nodes shown in fig. 3, a transaction characteristic field is extracted from each segment of the transaction processing node. If the original transaction tracking means is adopted, a unique transaction serial number, such as the uid shown in fig. 3, is required on each transaction processing node to realize matching tracking of the transaction, which is identified as a service.
However, in practice, the production system often does not have such a condition, different application modules in the production system are developed by different people, and no unique identifier is unchanged from beginning to end, so that the cost for modification is high. However, the inventors have found that transaction operations entering each transaction processing node and transaction operations issuing from each transaction processing node have characteristic fields that can be matched. For example, a user id field is provided before and after the mobile banking APP, and the two transactions with the same field value can be matched.
However, the transactions before and after the mobile banking F5 do not have transaction fields with the same name, but the inventor finds that the tid field of the previous section and the typeid field of the next section have the same business meaning, and the two fields have the same value, so that matching can be performed. Also, as shown in fig. 3, no transaction field is exactly the same before and after the ESB front node, but the value of the typeid field in the previous stage is the same as the value of the tt field in the subsequent stage, and thus matching can be achieved as well.
As can be seen from the above description, in the present application, the first transaction operation entered into each transaction processing node and the second transaction operation sent by each transaction processing node are matched according to the transaction characteristic field in the transaction data, so that the strict requirement on transaction matching is greatly reduced, and the transaction tracking of the whole service path is finally realized by segment-by-segment matching.
In this embodiment, by matching the first transaction operation and the second transaction operation through the transaction characteristic field, when the first transaction operation entering each transaction processing node and the second transaction operation sent by each transaction processing node are matched based on transaction data, the requirement of a matching code can be reduced, and further a powerful help is provided for timely discovering and positioning application performance faults, so that the technical problem of poor path tracking performance caused by non-uniform transaction serial numbers in the conventional transaction path tracking method is solved.
Step S102 to step S106 will be described below with reference to the detailed description.
As can be seen from the above description, in the present application, first, a plurality of transaction processing nodes for processing a target service are determined, and then, transaction data of a transaction operation corresponding to each transaction processing node is determined, which may be specifically determined in the following ways.
In a first way,
Firstly, sending a calling request to a target database; the calling request is used for calling the transaction data of each transaction processing node;
and then, acquiring response information which carries the transaction data and is fed back by the target database based on the calling request.
In the present application, the transaction data may be obtained to a development department. Specifically, since various service systems are realized by the development department, complete transaction data corresponding to a service at each transaction processing node can be acquired from the development department.
For example, a user may send a call request to a target database storing transaction data, and after the target database obtains the call request, the target database feeds back complete transaction data carrying each service at each transaction processing node to the user. Such as the transaction data shown in figure 2.
By the adoption of the acquisition mode, accurate transaction data can be acquired, and based on the acquisition mode, a more accurate path tracking result can be obtained when the transaction tracking path is determined based on the transaction data.
The second way,
Firstly, target data of at least one service is obtained, wherein the target data comprises: network traffic data packets, or transaction journal data;
and secondly, analyzing the network flow data packet to obtain transaction data of the transaction operation corresponding to each transaction processing node.
In this application, in addition to the manner described in the first manner, target data of at least one service may be obtained, where the target data may be a network traffic data packet or transaction journal data. And analyzing the network flow data packet or the transaction flow log data to obtain transaction data of the transaction operation corresponding to each transaction processing node.
It should be noted that the transaction data obtained after the analysis is organized according to the communication pair, and when the transaction data is mapped to the service transaction tracking path, the physical concepts such as an IP address, a port and the like are merged or split according to asset information, and in addition, transaction characteristic fields such as a service code, a channel number and the like are added to define a transaction processing node together, so as to form a real service path.
It should be noted that, in the present application, an analysis process for analyzing the network traffic data packet is the same as an analysis process for analyzing the transaction flow log data, and details are not repeated here.
By the aid of the acquisition mode, the transaction data can be acquired quickly, and accordingly, when the service path is determined based on the transaction data, the required service path can be monitored quickly.
It should be noted that, in the present application, the first and second manners may be combined, so as to obtain the traffic transaction tracking path required for monitoring more quickly and completely.
After the business transaction tracking path is obtained, the business transaction tracking path may be displayed in a visual manner, as shown in fig. 4, the business transaction tracking path is a visual display diagram of the business transaction tracking path, and as can be seen from fig. 4, the business transaction tracking path is formed by a directed connection line between a transaction processing node and a transaction processing node.
Specifically, A, B, C in fig. 4 are transaction processing nodes, and AB represents the second transaction operation issued by transaction processing node a, i.e., the first transaction operation entered into transaction processing node B. Similarly, BC represents the second transaction operation issued by transaction processing node B, i.e., the first transaction operation entered into transaction processing node C.
In the present application, after determining the transaction data of the transaction operation corresponding to each transaction processing node according to the manner described above, the first transaction operation entering each transaction processing node and the second transaction operation sent by each transaction processing node may be matched according to the transaction characteristic field in the transaction data, so as to obtain the target service transaction tracking path.
In an optional embodiment, in step S106, the matching, according to the transaction characteristic field in the transaction data, the first transaction operation entering each transaction processing node and the second transaction operation sent by each transaction processing node includes:
step S1061, determining a first transaction operation entering each transaction processing node and a transaction matching code of a second transaction operation sent by each transaction processing node to obtain a first transaction matching code and a second transaction matching code;
step S1062, performing a matching operation on the first transaction operation and the second transaction operation according to the first transaction matching code and the second transaction matching code.
In this embodiment, first, a first transaction match code before each transaction processing node and a second transaction match code after each transaction processing node are determined. The first transaction matching code before each transaction processing node is the transaction matching code of the first transaction operation entering each transaction processing node, and the second transaction matching code after the transaction processing node is the transaction matching code of the second transaction operation sent by each transaction processing node.
After the first transaction matching code and the second transaction matching code are obtained, the first transaction operation and the second transaction operation can be matched according to the first transaction matching code and the second transaction matching code, and therefore whether the first transaction operation and the second transaction operation belong to the same target service transaction tracking path or not can be determined according to a matching result.
Taking fig. 4 as an example, first, a first transaction matching code before the transaction processing node B (i.e., the transaction matching code of the first transaction operation entering the transaction processing node B) is determined, and a second transaction matching code after the transaction processing result B (i.e., the transaction matching code of the second transaction operation sent by the transaction processing node B) is determined. The first transaction operation entering the transaction processing node B is transaction operation AB, and the second transaction operation sent by the transaction processing node B is transaction operation BC.
Then, the first transaction operation AB and the second transaction operation BC are matched according to the first transaction match code and the second transaction match code.
In an alternative embodiment, the first transaction match code and the second transaction match code comprise any one of:
first, the first transaction matching code and the second transaction matching code are fields with the same or different field names and the same field contents.
Specifically, the first transaction matching code may be a transit id, and in this case, the second transaction matching code may also be a transit id, where the field contents of the first transaction matching code transit id and the second transaction matching code transit id are the same. If the first transaction matching code is a Transid, then the second transaction matching code may be a Transcode, where the field contents of the first transaction matching code Transid and the second transaction matching code Transcode are the same.
That is, the field names of the first transaction match code and the second transaction match code may be the same or different, but the field contents of the first transaction match code and the second transaction match code are the same.
For example, as shown in fig. 4, the transaction matching code of the transaction operation AB may be a transid, denoted as transid1, and the transaction matching code of the transaction operation BC may be a transid, denoted as transid2, at which time, the contents of the fields of transid1 and transid2 may be matched, so as to determine whether the transaction operation AB and the transaction operation BC are matched according to the matching result.
The transaction matching code of the transaction operation AB may be a transport, and the transaction matching code of the transaction operation BC may be a transport, and at this time, the contents of the fields of the transport and the transport may be matched, so as to determine whether the transaction operation AB and the transaction operation BC are matched according to the matching result.
Second, the first transaction match code includes at least one first field, the second transaction match code includes at least one second field, the field content of the at least one first field matches the field content of the at least one second field, and the at least one first field and the at least one second field contain fields with the same field name.
Specifically, the first transaction matching code may be a Transid + Transcode, and in this case, the second transaction matching code may be a Transid, wherein the field contents of the first transaction matching code Transid + Transcode and the second transaction matching code Transid are the same. If the first transaction matching code is a Transid + Transcode, then the second transaction matching code may also be a Transid + Transcode, where the field contents of the first transaction matching code Transid + Transcode and the second transaction matching code Transid + Transcode are the same.
That is, the first transaction match code includes at least one first field, the second transaction match code includes at least one second field, and the field contents of the at least one first field and the field contents of the at least one second field match.
For example, as shown in fig. 4, the transaction match code for transaction operation AB may be a transid + transcode, denoted as transid1+ transcode1, and the transaction match code for transaction operation BC may be a transid, denoted as transid 2. At this time, the field contents of transit 1+ transit 1 and the field contents of transit 2 may be matched, thereby determining whether the transaction operation AB and the transaction operation BC match according to the matching result.
For another example, the transaction match code for transaction operation AB may be transit + transit, denoted as transit 1+ transit 1, and the transaction match code for transaction operation BC may be transit + transit, denoted as transit 2+ transit 2. At this time, the contents of the fields of the transit 1+ transit 1 and the fields of the transit 2+ transit 2 may be matched, thereby determining whether the transaction operation AB and the transaction operation BC are matched according to the matching result.
Thirdly, the first transaction matching code is a partial field in a first field, and the second transaction matching code is a second field, wherein the partial field in the first field and the second field have the same field content.
Specifically, the first transaction match code may be the first three bits of the transid, and in this case, the second transaction match code may be the transid, wherein the field contents of the first transaction match code and the field contents of the second transaction match code are the same.
That is, the first transaction match code is a partial field in the first field, and the second transaction match code is a second field, wherein the partial field in the first field and the second field have the same field content.
For example, as shown in fig. 4, the transaction matching code of the transaction operation AB may be the first three fields of the transod, the first three fields of the transod are denoted as transod 1, and the transaction matching code of the transaction operation BC may be the transod, which is denoted as transod 2, at which time, the contents of the fields of the transod 1 and the transod 2 may be matched, so as to determine whether the transaction operation AB and the transaction operation BC are matched according to the matching result.
In this application, the determining of the transaction matching code of the first transaction operation of each transaction processing node and the second transaction operation sent by each transaction processing node may specifically include:
first, the node attribute information for each transaction processing node is looked up in a target mapping table.
In the application, a target mapping table may be constructed in advance, and the target mapping table includes a corresponding relationship between the transaction processing node and the transaction matching code. Wherein, the target mapping table may be a table in a key-value form. Key represents node attribute information of a transaction processing node, and value represents a first transaction matching code and a second transaction matching code corresponding to the node attribute information.
And then, determining the transaction matching codes of the first transaction operation of each transaction processing node and the second transaction operation sent by each transaction processing node according to the node attribute information.
It should be noted that the target mapping table may be a data table preset by a skilled person. When determining the transaction matching code of the first transaction operation of each transaction processing node and the second transaction operation sent by each transaction processing node, the target mapping table may be first called from the database, and then the node attribute information of the transaction processing node is found in the target mapping table, so as to find the first transaction matching code and the second transaction matching code corresponding to the node attribute information in the target mapping table.
In this application, after the first transaction matching code and the second transaction matching code are determined according to the above several cases, the first transaction operation and the second transaction operation may be matched according to the first transaction matching code and the second transaction matching code, and the specific process is described as follows:
step S11, determining, for each first transaction match code, a second transaction match code among the plurality of second transaction match codes that is the same as the current first transaction match code;
step S12, if the same second transaction matching code is determined, establishing the incidence relation between the current first transaction matching code and the matched same second transaction matching code;
step S13, if the same second transaction matching code is not determined, it is determined that the service transaction tracking path corresponding to the current first transaction matching code is ended.
In the present application, the matching process may be performed for all transaction processing nodes except the head-to-tail transaction processing node according to the procedures described in step S11 to step S13.
It is assumed that, for any one transaction processing node, the first transaction operation is plural and the second transaction operation is plural.
At this time, each first transaction operation may be matched with each of the plurality of second transaction operations. The specific matching principle is to match the first transaction matching code of the first transaction operation with the second transaction matching code of each second transaction operation. And if a second transaction matching code which is the same as the first transaction matching code is determined in the plurality of second transaction matching codes, establishing the association relationship between the first transaction matching code and the matched same second transaction matching code.
Specifically, when the association relationship between the first transaction matching code and the matched identical second transaction matching code is established, the same identification information may be set for the first transaction operation of the first transaction matching code and the second transaction operation corresponding to the identical second transaction matching code.
If the second transaction matching code which is the same as the first transaction matching code is not determined, the transaction processing node corresponding to the first transaction operation is the last transaction processing node of the corresponding target service transaction tracking path, and at this time, path tracking is finished.
The above-described process is adopted for matching all the transaction processing nodes except the head-end transaction processing node, and the target service transaction tracking path of each service can be finally obtained through section-by-section matching.
In this application, after obtaining the target service transaction tracking path of each service in the manner described above, the statistical analysis may be performed on the target service transaction tracking path to obtain transaction processing performance information of the target service transaction tracking path at each transaction processing node, where the transaction processing performance information includes at least one of the following information: the target service transaction tracking path comprises transaction processing nodes, transaction processing time of each transaction processing node, transaction field information of transaction data of each transaction processing node and response state of each transaction processing node.
In the present application, a source IP, a destination IP, a source port, a destination port, and transaction characteristic rules such as transaction parameters and service return codes may also be defined on the transaction processing node or the directed connection. The transaction data forms an index according to the rule definitions, indexes such as transaction amount, response time and the like can be obtained through statistics, and all relevant field information of the target service in the processing process is contained.
Specifically, in the present application, after the target service transaction tracking path is obtained, transaction data corresponding to a transaction operation sent by the service at each transaction processing node in the target service transaction tracking path may be extracted according to the transaction matching code, and statistical analysis is performed on the transaction data, so that transaction processing performance information of each transaction processing node in the target service transaction tracking path may be obtained, where the transaction processing performance information includes at least one of the following: the transaction processing nodes (i.e. the transaction processing nodes included in the target service transaction tracking path) through which the service passes in the processing process, each transaction processing node receives the time required by the request of the previous transaction processing node to send the request to the next transaction processing node (i.e. the transaction processing time of each transaction processing node), and the feedback result (i.e. the response state of each transaction processing node) made by the next transaction processing node to send the request to the previous transaction processing node and the transaction field information of the transaction data of each transaction processing node.
In this embodiment, after the target service transaction tracking path is completed, the transaction tracking path of the service and the transaction processing performance information of the service at each transaction processing node may also be displayed in a visual form, and the display effect diagram is shown in fig. 5.
Taking fig. 5 as an example for explanation, first, transaction processing nodes included in the target service are determined according to the target service transaction tracking path, then from the application performance monitoring perspective, transaction processing performance information of each transaction processing node is obtained by performing statistical analysis on transaction data corresponding to transaction operations sent by each transaction processing node in the target service transaction tracking path, and is displayed by using a waterfall model diagram, as shown in fig. 5. From fig. 5, it can be visually observed that the target traffic passes through the transaction processing nodes in the traffic tracking path, and the transaction processing time of each transaction processing node. In addition, the transaction field information and the response state of the target service at each transaction processing node can be observed, so that the operation and maintenance work is facilitated to the maximum extent.
As can be seen from the above description, the present application has the following technical effects:
(1) and determining a target service transaction tracking path through the transaction processing node, thereby realizing fine monitoring of the target service. And, the transaction processing node includes but is not limited to various transaction characteristics such as IP address, port, transaction type, service return code, etc.
(2) And obtaining a target business transaction tracking path of each business through the section-by-section transaction tracking matching. In the target service transaction tracking process, a uniform transaction serial number is not required, only a unique transaction matching code is required between a first transaction operation entering each transaction processing node and a second transaction operation sent by each transaction processing node, and the requirement on the transaction matching code in the target service transaction tracking process is reduced.
(3) The display of target service transaction tracking paths and transaction processing performance information of each service can be realized, and transaction processing nodes through which the tracked services pass are displayed through a service path graph; displaying the transaction processing time on each transaction processing node through a waterfall model graph; and provides transaction field information for each transaction operation tracked.
Example two:
the embodiment of the present invention further provides a device for determining a service path, where the device for determining a service path is mainly used to execute the method for determining a service path provided in the foregoing content of the embodiment of the present invention, and the following describes the device for determining a service path provided in the embodiment of the present invention in detail.
Fig. 6 is a schematic diagram of a service path determining apparatus according to an embodiment of the present invention, and as shown in fig. 6, the service path determining apparatus mainly includes a first determining unit 10, a second determining unit 20 and a matching unit 30, where:
a first determination unit 10 for determining a plurality of transaction processing nodes for processing a target service;
a second determining unit 20, configured to determine transaction data of a transaction operation corresponding to each transaction processing node; the transaction operation comprises a first transaction operation entering a current transaction processing node and a second transaction operation sent by the current transaction processing node, and the transaction data comprises each network field and each transaction characteristic field;
a matching unit 30, configured to perform matching operation on a first transaction operation entering each transaction processing node and a second transaction operation sent by each transaction processing node according to a transaction characteristic field in the transaction data, so as to obtain a target service transaction tracking path, where the transaction characteristic field includes at least one of: user ID, subject ID, and type ID.
In the embodiment of the invention, a plurality of transaction processing nodes for processing target services are determined firstly; then determining transaction data of transaction operation corresponding to each transaction processing node; and finally, matching the first transaction operation entering each transaction processing node with the second transaction operation sent by each transaction processing node according to the transaction characteristic field in the transaction data, so as to obtain a target service transaction tracking path. In this embodiment, by matching the first transaction operation and the second transaction operation through the transaction characteristic field, when the first transaction operation entering each transaction processing node and the second transaction operation sent by each transaction processing node are matched based on transaction data, the requirement of a matching code can be reduced, and further a powerful help is provided for timely discovering and positioning application performance faults, so that the technical problem of poor path tracking performance caused by non-uniform transaction serial numbers in the conventional transaction path tracking method is solved.
Optionally, the second determination unit 20 is configured to: sending a calling request to a target database; the calling request is used for calling the transaction data of each transaction processing node; and acquiring response information which carries the transaction data and is fed back by the target database based on the calling request.
Optionally, the second determining unit 20 is further configured to: obtaining target data of at least one service, wherein the target data comprises: network traffic data packets, or transaction journal data; and analyzing the network flow data packet to obtain transaction data of the transaction operation corresponding to each transaction processing node.
Optionally, the matching unit 30 is configured to: determining a first transaction operation of each transaction processing node and a transaction matching code of a second transaction operation sent by each transaction processing node to obtain a first transaction matching code and a second transaction matching code; and matching the first transaction operation with the second transaction operation according to the first transaction matching code and the second transaction matching code.
Optionally, the first and second transaction match codes comprise any of: the first transaction matching code and the second transaction matching code are fields with the same or different field names and the same field contents; or the first transaction match code includes at least one first field and the second transaction match code includes at least one second field, the field contents of the at least one first field and the at least one second field matching; or the first transaction matching code is a partial field in a first field, and the second transaction matching code is a second field, wherein the partial field in the first field and the field content of the second field are the same.
Optionally, if the first transaction operation is multiple, and the second transaction operation is multiple; the matching unit 30 is further adapted to: for each first transaction match code, determining a second transaction match code among the plurality of second transaction match codes that is the same as the current first transaction match code; if the same second transaction matching code is determined, establishing an incidence relation between the current first transaction matching code and the matched same second transaction matching code; and if the same second transaction matching code is not determined, determining that the service transaction tracking path corresponding to the current first transaction matching code is finished.
Optionally, the matching unit 30 is further configured to: searching node attribute information of each transaction processing node in a target mapping table; and determining the first transaction operation of each transaction processing node and the transaction matching code of the second transaction operation sent by each transaction processing node according to the node attribute information.
Optionally, the apparatus is further configured to: performing statistical analysis on the target service transaction tracking path to obtain transaction processing performance information of the target service transaction tracking path at each transaction processing node, wherein the transaction processing performance information includes at least one of the following information: the target service transaction tracking path comprises transaction processing nodes, transaction processing time of each transaction processing node, transaction field information of transaction data of each transaction processing node and response state of each transaction processing node.
The device provided by the embodiment of the present invention has the same implementation principle and technical effect as the method embodiments, and for the sake of brief description, reference may be made to the corresponding contents in the method embodiments without reference to the device embodiments.
Example three:
referring to fig. 7, an embodiment of the present invention further provides an electronic device 100, including: a processor 40, a memory 41, a bus 42 and a communication interface 43, wherein the processor 40, the communication interface 43 and the memory 41 are connected through the bus 42; the processor 40 is arranged to execute executable modules, such as computer programs, stored in the memory 41.
The memory 41 may include a high-speed Random Access Memory (RAM) and may also include a non-volatile memory (non-volatile memory), such as at least one disk memory. The communication connection between the network element of the system and at least one other network element is realized through at least one communication interface 43 (which may be wired or wireless), and the internet, a wide area network, a local network, a metropolitan area network, etc. may be used.
The bus 42 may be an ISA bus, PCI bus, EISA bus, or the like. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one double-headed arrow is shown in FIG. 7, but this does not indicate only one bus or one type of bus.
The memory 41 is used for storing a program, the processor 40 executes the program after receiving an execution instruction, and the method executed by the apparatus defined by the flow process disclosed in any of the foregoing embodiments of the present invention may be applied to the processor 40, or implemented by the processor 40.
The processor 40 may be an integrated circuit chip having signal processing capabilities. In implementation, the steps of the above method may be performed by integrated logic circuits of hardware or instructions in the form of software in the processor 40. The processor 40 may be a general-purpose processor, and includes a Central Processing Unit (CPU), a Network Processor (NP), and the like; the device can also be a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field-Programmable Gate Array (FPGA) or other Programmable logic device, a discrete Gate or transistor logic device, or a discrete hardware component. The various methods, steps and logic blocks disclosed in the embodiments of the present invention may be implemented or performed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of the method disclosed in connection with the embodiments of the present invention may be directly implemented by a hardware decoding processor, or implemented by a combination of hardware and software modules in the decoding processor. The software module may be located in ram, flash memory, rom, prom, or eprom, registers, etc. storage media as is well known in the art. The storage medium is located in a memory 41, and the processor 40 reads the information in the memory 41 and completes the steps of the method in combination with the hardware thereof.
In addition, in the description of the embodiments of the present invention, unless otherwise explicitly specified or limited, the terms "mounted," "connected," and "connected" are to be construed broadly, e.g., as meaning either a fixed connection, a removable connection, or an integral connection; can be mechanically or electrically connected; they may be connected directly or indirectly through intervening media, or they may be interconnected between two elements. The specific meanings of the above terms in the present invention can be understood in specific cases to those skilled in the art.
In the description of the present invention, it should be noted that the terms "center", "upper", "lower", "left", "right", "vertical", "horizontal", "inner", "outer", etc., indicate orientations or positional relationships based on the orientations or positional relationships shown in the drawings, and are only for convenience of description and simplicity of description, but do not indicate or imply that the device or element being referred to must have a particular orientation, be constructed and operated in a particular orientation, and thus, should not be construed as limiting the present invention. Furthermore, the terms "first," "second," and "third" are used for descriptive purposes only and are not to be construed as indicating or implying relative importance.
It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.
In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other ways. The above-described embodiments of the apparatus are merely illustrative, and for example, the division of the units is only one logical division, and there may be other divisions when actually implemented, and for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection of devices or units through some communication interfaces, and may be in an electrical, mechanical or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit.
The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a non-volatile computer-readable storage medium executable by a processor. Based on such understanding, the technical solution of the present invention may be embodied in the form of a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present invention. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes.
Finally, it should be noted that: the above-mentioned embodiments are only specific embodiments of the present invention, which are used for illustrating the technical solutions of the present invention and not for limiting the same, and the protection scope of the present invention is not limited thereto, although the present invention is described in detail with reference to the foregoing embodiments, those skilled in the art should understand that: any person skilled in the art can modify or easily conceive the technical solutions described in the foregoing embodiments or equivalent substitutes for some technical features within the technical scope of the present disclosure; such modifications, changes or substitutions do not depart from the spirit and scope of the embodiments of the present invention, and they should be construed as being included therein. Therefore, the protection scope of the present invention shall be subject to the protection scope of the claims.
Claims (10)
1. A method for determining a traffic path, comprising:
determining a plurality of transaction processing nodes for processing a target service;
determining transaction data of transaction operation corresponding to each transaction processing node; the transaction operation comprises a first transaction operation entering a current transaction processing node and a second transaction operation sent by the current transaction processing node, and the transaction data comprises each network field and each transaction characteristic field;
matching the first transaction operation entering each transaction processing node and the second transaction operation sent by each transaction processing node according to the transaction characteristic field in the transaction data so as to obtain a target service transaction tracking path, wherein the transaction characteristic field comprises at least one of the following fields: user ID, subject ID, and type ID.
2. The method of claim 1, wherein determining transaction data for the transaction operation for each transaction processing node comprises:
sending a calling request to a target database; the calling request is used for calling the transaction data of each transaction processing node;
and acquiring response information which carries the transaction data and is fed back by the target database based on the calling request.
3. The method of claim 1, wherein determining transaction data for the transaction operation for each transaction processing node further comprises:
obtaining target data of at least one service, wherein the target data comprises: network traffic data packets, or transaction journal data;
and analyzing the network flow data packet to obtain transaction data of the transaction operation corresponding to each transaction processing node.
4. The method of claim 1, wherein matching a first transaction operation entered into each transaction processing node with a second transaction operation issued by each transaction processing node based on a transaction characteristics field in the transaction data comprises:
determining a first transaction operation entering each transaction processing node and a transaction matching code of a second transaction operation sent by each transaction processing node to obtain a first transaction matching code and a second transaction matching code;
and matching the first transaction operation with the second transaction operation according to the first transaction matching code and the second transaction matching code.
5. The method of claim 4, wherein the first transaction match code and the second transaction match code comprise any of:
the first transaction matching code and the second transaction matching code are fields with the same or different field names and the same field contents; or
The first transaction match code includes at least one first field and the second transaction match code includes at least one second field, the field contents of the at least one first field and the at least one second field matching; or
The first transaction matching code is a partial field in a first field, and the second transaction matching code is a second field, wherein the partial field in the first field and the field content of the second field are the same.
6. The method of claim 4, wherein the first transaction operation is a plurality and the second transaction operation is a plurality;
matching the first transaction operation and the second transaction operation according to the first transaction matching code and the second transaction matching code comprises:
for each first transaction match code, determining a second transaction match code among the plurality of second transaction match codes that is the same as the current first transaction match code;
if the same second transaction matching code is determined, establishing an incidence relation between the current first transaction matching code and the matched same second transaction matching code;
and if the same second transaction matching code is not determined, determining that the service transaction tracking path corresponding to the current first transaction matching code is finished.
7. The method of claim 4, wherein determining the transaction match code for the first transaction operation of each transaction processing node and the second transaction operation issued by each transaction processing node comprises:
searching node attribute information of each transaction processing node in a target mapping table;
and determining the first transaction operation of each transaction processing node and the transaction matching code of the second transaction operation sent by each transaction processing node according to the node attribute information.
8. The method of claim 1, further comprising:
performing statistical analysis on the target service transaction tracking path to obtain transaction processing performance information of the target service transaction tracking path at each transaction processing node, wherein the transaction processing performance information includes at least one of the following information: the target service transaction tracking path comprises transaction processing nodes, transaction processing time of each transaction processing node, transaction field information of transaction data of each transaction processing node and response state of each transaction processing node.
9. An apparatus for determining a traffic path, comprising:
a first determination unit for determining a plurality of transaction processing nodes for processing a target service;
the second determining unit is used for determining the transaction data of the transaction operation corresponding to each transaction processing node; the transaction operation comprises a first transaction operation entering a current transaction processing node and a second transaction operation sent by the current transaction processing node, and the transaction data comprises each network field and each transaction characteristic field;
a matching unit, configured to perform matching operation on a first transaction operation entering each transaction processing node and a second transaction operation sent by each transaction processing node according to a transaction characteristic field in the transaction data, so as to obtain a target service transaction tracking path, where the transaction characteristic field includes at least one of: user ID, subject ID, and type ID.
10. An electronic device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the steps of the method of any of the preceding claims 1 to 8 are implemented when the computer program is executed by the processor.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010545849.2A CN111784516B (en) | 2020-06-15 | 2020-06-15 | Service path determining method and device and electronic equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010545849.2A CN111784516B (en) | 2020-06-15 | 2020-06-15 | Service path determining method and device and electronic equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111784516A true CN111784516A (en) | 2020-10-16 |
| CN111784516B CN111784516B (en) | 2023-12-22 |
Family
ID=72756579
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010545849.2A Active CN111784516B (en) | 2020-06-15 | 2020-06-15 | Service path determining method and device and electronic equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111784516B (en) |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112737869A (en) * | 2021-04-02 | 2021-04-30 | 北京宇信科技集团股份有限公司 | Link tracking method and system of ESB (Enterprise service bus) system |
| CN112882994A (en) * | 2021-03-30 | 2021-06-01 | 中信银行股份有限公司 | Log extraction method and device |
| CN113744058A (en) * | 2021-09-08 | 2021-12-03 | 中国建设银行股份有限公司 | Transaction line processing method and device |
| CN113868089A (en) * | 2021-09-30 | 2021-12-31 | 中国建设银行股份有限公司 | Transaction data processing method and device |
Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| AUPR384701A0 (en) * | 2001-03-20 | 2001-04-12 | Department of Natural Resources and Environment for and on Behalf of the Crown in Right of the State of Victoria, The | Electronic financial instrument |
| JP2011034298A (en) * | 2009-07-31 | 2011-02-17 | Sumitomo Mitsui Banking Corp | Method for foreign remittance auto process control, and program |
| CN105719072A (en) * | 2016-01-18 | 2016-06-29 | 上海天旦网络科技发展有限公司 | System and method for associating multistage assembly transactions |
| CN110428325A (en) * | 2019-07-31 | 2019-11-08 | 中国工商银行股份有限公司 | Transaction tracking and device |
| CN110502426A (en) * | 2019-07-08 | 2019-11-26 | 中国工商银行股份有限公司 | The test method and device of distributed data processing system |
| CN110795003A (en) * | 2019-10-30 | 2020-02-14 | 邵忠 | Interface display method and device |
| CN111105235A (en) * | 2019-12-31 | 2020-05-05 | 深圳市网心科技有限公司 | Supply chain transaction privacy protection system and method based on block chain and related equipment |
| CN111177252A (en) * | 2019-11-26 | 2020-05-19 | 腾讯云计算（北京）有限责任公司 | Service data processing method and device |
| CN111177246A (en) * | 2019-12-27 | 2020-05-19 | 腾讯云计算（北京）有限责任公司 | Service data processing method and device |
-
2020
- 2020-06-15 CN CN202010545849.2A patent/CN111784516B/en active Active
Patent Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| AUPR384701A0 (en) * | 2001-03-20 | 2001-04-12 | Department of Natural Resources and Environment for and on Behalf of the Crown in Right of the State of Victoria, The | Electronic financial instrument |
| JP2011034298A (en) * | 2009-07-31 | 2011-02-17 | Sumitomo Mitsui Banking Corp | Method for foreign remittance auto process control, and program |
| CN105719072A (en) * | 2016-01-18 | 2016-06-29 | 上海天旦网络科技发展有限公司 | System and method for associating multistage assembly transactions |
| CN110502426A (en) * | 2019-07-08 | 2019-11-26 | 中国工商银行股份有限公司 | The test method and device of distributed data processing system |
| CN110428325A (en) * | 2019-07-31 | 2019-11-08 | 中国工商银行股份有限公司 | Transaction tracking and device |
| CN110795003A (en) * | 2019-10-30 | 2020-02-14 | 邵忠 | Interface display method and device |
| CN111177252A (en) * | 2019-11-26 | 2020-05-19 | 腾讯云计算（北京）有限责任公司 | Service data processing method and device |
| CN111177246A (en) * | 2019-12-27 | 2020-05-19 | 腾讯云计算（北京）有限责任公司 | Service data processing method and device |
| CN111105235A (en) * | 2019-12-31 | 2020-05-05 | 深圳市网心科技有限公司 | Supply chain transaction privacy protection system and method based on block chain and related equipment |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112882994A (en) * | 2021-03-30 | 2021-06-01 | 中信银行股份有限公司 | Log extraction method and device |
| CN112737869A (en) * | 2021-04-02 | 2021-04-30 | 北京宇信科技集团股份有限公司 | Link tracking method and system of ESB (Enterprise service bus) system |
| CN113744058A (en) * | 2021-09-08 | 2021-12-03 | 中国建设银行股份有限公司 | Transaction line processing method and device |
| CN113868089A (en) * | 2021-09-30 | 2021-12-31 | 中国建设银行股份有限公司 | Transaction data processing method and device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111784516B (en) | 2023-12-22 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111784516B (en) | Service path determining method and device and electronic equipment | |
| CN111367983A (en) | Database access method, system, device and storage medium | |
| CN108737333B (en) | Data detection method and device | |
| WO2019196549A1 (en) | Method and device for determining high-risk user | |
| WO2020259003A1 (en) | Link tracking method and apparatus | |
| CN113342564B (en) | Log auditing method and device, electronic equipment and medium | |
| CN109194617B (en) | Automatic parsing and packaging method and device for XML (extensive markup language) message | |
| CN107633016B (en) | Data processing method and device and electronic equipment | |
| US9172593B2 (en) | System and method for identifying problems on a network | |
| CN110780870B (en) | Service execution method, device, equipment and storage medium | |
| WO2021254027A1 (en) | Method and apparatus for identifying suspicious community, and storage medium and computer device | |
| RU2631769C2 (en) | Method and device for determining objective of information processing | |
| CN111181799B (en) | Network traffic monitoring method and equipment | |
| CN105608517B (en) | Business transaction performance management and visualization method and device based on flow | |
| CN111654414B (en) | Application system monitoring method and device and electronic equipment | |
| CN108512720B (en) | Website traffic statistical method and device | |
| WO2020155508A1 (en) | Suspicious user screening method and apparatus, computer device and storage medium | |
| CN110807050B (en) | Performance analysis method, device, computer equipment and storage medium | |
| CN114022151A (en) | Block chain data visualization method and system, electronic device and storage medium | |
| CN113326064A (en) | Method for dividing business logic module, electronic equipment and storage medium | |
| CN109995834A (en) | Massive dataflow processing method, calculates equipment and storage medium at device | |
| CN116723154A (en) | Route distribution method and system based on load balancing | |
| CN110020166B (en) | Data analysis method and related equipment | |
| CN114285786B (en) | Construction method and device of network link library | |
| WO2021129849A1 (en) | Log processing method, apparatus and device, and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |