CN111884824A - Transaction link monitoring method, device, equipment and storage medium - Google Patents
Transaction link monitoring method, device, equipment and storage medium Download PDFInfo
- Publication number
- CN111884824A CN111884824A CN202010463577.1A CN202010463577A CN111884824A CN 111884824 A CN111884824 A CN 111884824A CN 202010463577 A CN202010463577 A CN 202010463577A CN 111884824 A CN111884824 A CN 111884824A
- Authority
- CN
- China
- Prior art keywords
- transaction
- identification code
- request message
- private network
- user side
- 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.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 65
- 238000012544 monitoring process Methods 0.000 title claims abstract description 53
- 238000012546 transfer Methods 0.000 claims abstract description 54
- 230000004044 response Effects 0.000 claims abstract description 53
- 230000001960 triggered effect Effects 0.000 claims abstract description 17
- 230000005540 biological transmission Effects 0.000 claims description 17
- 238000004590 computer program Methods 0.000 claims description 15
- 238000012806 monitoring device Methods 0.000 claims description 7
- 238000010586 diagram Methods 0.000 description 10
- 238000004364 calculation method Methods 0.000 description 3
- 238000012545 processing Methods 0.000 description 3
- 230000002159 abnormal effect Effects 0.000 description 2
- 238000013475 authorization Methods 0.000 description 2
- 230000005856 abnormality Effects 0.000 description 1
- 238000003491 array Methods 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 238000011156 evaluation Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
- H04L41/0677—Localisation of faults
-
- 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
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/10—Active monitoring, e.g. heartbeat, ping or trace-route
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/16—Threshold monitoring
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
- H04L63/0823—Network architectures or network communication protocols for network security for authentication of entities using certificates
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
- H04L67/025—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP] for remote control or remote monitoring of applications
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Business, Economics & Management (AREA)
- Accounting & Taxation (AREA)
- Finance (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)
- Computer Hardware Design (AREA)
- Computer Security & Cryptography (AREA)
- Computing Systems (AREA)
- General Engineering & Computer Science (AREA)
- Health & Medical Sciences (AREA)
- Cardiology (AREA)
- General Health & Medical Sciences (AREA)
- Computer And Data Communications (AREA)
Abstract
The application relates to the field of system data monitoring, and particularly discloses a transaction link monitoring method, a device, equipment and a storage medium, wherein the method comprises the following steps: the user side generates a transaction identification code according to a transaction request message triggered by a user and stores a corresponding transaction record in a relational database; the user side inserts the transaction identification code into the transaction request message to obtain a filled transaction request message, and sends the filled transaction request message to the transfer server; the transfer server is connected with a private network according to the received filled transaction request message so as to send the filled transaction request message to a private network subsystem; the private network subsystem processes the filled transaction request message, generates a response message and sends the response message to the user side, wherein the response message comprises a transaction identification code; and respectively recording the time when the user side, the transfer server and the private network subsystem receive the transaction identification code so as to monitor the user side, the transfer server and the private network subsystem.
Description
Technical Field
The present application relates to the field of transaction monitoring, and in particular, to a method, an apparatus, a device, and a storage medium for monitoring a transaction link.
Background
At present, with the improvement of hardware processing capacity, the complexity of an application system is gradually increased, and when a transaction link composed of a plurality of application systems is used for data transmission, sudden failure of the application system in the transaction link often affects transaction progress, so that a large amount of loss is caused. Therefore, monitoring of the application system is needed for fault location and bottleneck evaluation to reduce the probability of the application system failure.
However, the current heartbeat monitoring method cannot track the whole life cycle of the transaction generated in circulation in the application system, cannot assist the application system in identifying the bottleneck, and has limited capability of assisting in fault location.
Therefore, how to comprehensively monitor the transaction of the application system in the transaction link and improve the accuracy and efficiency of fault location becomes an urgent problem to be solved.
Disclosure of Invention
The application provides a transaction link monitoring method, a transaction link monitoring device and a storage medium, so that transactions of an application system in a transaction link can be comprehensively monitored, and the accuracy and efficiency of fault location are improved.
In a first aspect, the present application provides a method for monitoring a transaction link, where the transaction link includes a user side, a transit server, and a private network subsystem, and the method includes:
a user side generates a transaction identification code corresponding to a transaction request message according to the transaction request message triggered by a user, and stores a transaction record corresponding to the transaction request message in a relational database, wherein the transaction record comprises the transaction identification code;
the user side inserts the transaction identification code in the transaction record into the transaction request message to obtain a filled transaction request message, and sends the filled transaction request message to a transfer server;
the transfer server is connected with a private network according to the received filled transaction request message so as to send the filled transaction request message to a private network subsystem;
the private network subsystem processes the filled transaction request message, generates a response message and sends the response message to the user side through the transfer server, wherein the response message comprises the transaction identification code;
and recording the time of receiving the transaction identification code by the user side, the transfer server and the private network subsystem according to the transaction identification code respectively so as to monitor the user side, the transfer server and the private network subsystem.
In a second aspect, the present application further provides a transaction link monitoring device, where the transaction link includes a user side, a transit server and a private network subsystem, and the device includes:
the identification code generation module is used for generating a transaction identification code corresponding to a transaction request message according to the transaction request message triggered by a user side and storing a transaction record corresponding to the transaction request message in a relational database, wherein the transaction record comprises the transaction identification code;
the message sending module is used for inserting the transaction identification code in the transaction record into the transaction request message by the user side to obtain a filled transaction request message and sending the filled transaction request message to a transfer server;
the message transfer module is used for connecting the transfer server with a private network according to the received filled transaction request message so as to send the filled transaction request message to a private network subsystem;
a response generation module, configured to process the filled transaction request message by the private network subsystem, generate a response message, and send the response message to the user side through the transit server, where the response message includes the transaction identification code;
and the time monitoring module is used for recording the time of receiving the transaction identification code by the user side, the transit server and the private network subsystem according to the transaction identification code so as to monitor the user side, the transit server and the private network subsystem.
In a third aspect, the present application further provides a computer device comprising a memory and a processor; the memory is used for storing a computer program; the processor is configured to execute the computer program and to implement the transaction link monitoring method as described above when executing the computer program.
In a fourth aspect, the present application also provides a computer-readable storage medium having stored thereon a computer program which, when executed by a processor, causes the processor to implement the transaction link monitoring method as described above.
The application discloses a transaction link monitoring method, a device, equipment and a storage medium.A user side generates a corresponding transaction identification code according to a transaction request message triggered by a user, stores a transaction record comprising the transaction identification code, inserts the transaction identification code in the transaction record into the transaction request message to obtain a filled transaction request message, and sends the filled transaction request message to a transfer server; the transfer server is connected with a private network and sends the filled transaction request message to a private network subsystem; and finally, the private network subsystem processes the filled transaction request message, generates a response message comprising the transaction identification code and sends the response message to the user side through the transfer server. And finally, monitoring the user side, the transfer server and the private network subsystem based on the time when the user side, the transfer server and the private network subsystem receive the transaction identification code. Each transaction is marked by using the unique transaction identification code generated when the transaction occurs, and the abnormal node in each transaction link is judged according to the time when the node in each transaction link receives the transaction identification code, so that the fault positioning time is shortened, and the fault positioning accuracy is improved.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings needed to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the following description are some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.
FIG. 1 is a schematic diagram of a transaction link provided by an embodiment of the present application;
fig. 2 is a schematic flow chart of a transaction link monitoring method according to an embodiment of the present application;
fig. 3 is a schematic diagram illustrating a step of storing a transaction record corresponding to a transaction request message in a relational database according to an embodiment of the present application;
FIG. 4 is a flow diagram illustrating exemplary sub-steps of a transaction link monitoring method provided in an embodiment of the present application;
FIG. 5 is a schematic block diagram of a transaction link monitoring apparatus provided by an embodiment of the present application;
fig. 6 is a schematic block diagram of a computer device according to an embodiment of the present application.
Detailed Description
The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some, but not all, embodiments of the present application. 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 application.
The flow diagrams depicted in the figures are merely illustrative and do not necessarily include all of the elements and operations/steps, nor do they necessarily have to be performed in the order depicted. For example, some operations/steps may be decomposed, combined or partially combined, so that the actual execution sequence may be changed according to the actual situation.
It is to be understood that the terminology used in the description of the present application herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. As used in the specification of the present application and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise.
It should also be understood that the term "and/or" as used in this specification and the appended claims refers to and includes any and all possible combinations of one or more of the associated listed items.
The embodiment of the application provides a transaction link monitoring method, a transaction link monitoring device, computer equipment and a storage medium. The transaction link monitoring method can be used for carrying out internal monitoring on the transaction link, and the accuracy of clapping positioning is improved.
Some embodiments of the present application will be described in detail below with reference to the accompanying drawings. The embodiments described below and the features of the embodiments can be combined with each other without conflict.
Fig. 1 is a schematic diagram of a transaction link. The transaction link comprises a user side, a transfer server and a private network subsystem.
In the specific implementation process, taking a private network subsystem as a bank system as an example, a user can trigger a transaction request at a user side, the user side sends a transaction request message to a transfer server, and then the transfer server sends the transaction request message to a subsystem a in the bank system, the subsystem a processes the transaction request message and sends the transaction request message to the subsystem B to wait for the response of the subsystem B, the subsystem C receives and processes the transaction request message and returns a response message to the subsystem B, the subsystem B returns the response message to the subsystem a after receiving the response message, and finally the subsystem a returns the processed response message to the user side, and the transaction is completed immediately.
Referring to fig. 2, fig. 2 is a schematic flow chart of a transaction link monitoring method according to an embodiment of the present application. According to the transaction link monitoring method, the transaction flow is generated when the transaction occurs in the transaction link, so that the transaction flow runs through the whole transaction process, the internal monitoring of the transaction link is further realized, and the accuracy of fault positioning is improved.
As shown in fig. 2, the transaction link monitoring method specifically includes: step S101 to step S105.
S101, a user side generates a transaction identification code corresponding to a transaction request message according to the transaction request message triggered by a user, and stores a transaction record corresponding to the transaction request message in a relational database, wherein the transaction record comprises the transaction identification code.
The user side may be an external application system, such as a web page. The transaction request message may be a transaction request triggered by a user at a user terminal, and the transaction request may be a request in the form of HTTP, T3, or the like.
The transaction identification code is a unique identification code for identifying a transaction corresponding to the transaction request message, and the transaction identification code may be generated by a Java Virtual Machine (JVM). In particular implementations, the transaction serial number may include an application instance, a timestamp of when the user triggered the transaction request, and random six bits of data.
For example, a user logs in a bank official network, clicks an option of applying for loan on the official network, submits an application after inputting related information, a bank webpage receives a loan transaction request triggered by the user, encapsulates the transaction request triggered by the user in an HTTP transaction request message through an HTTP protocol, and generates a transaction identification code representing the loan transaction based on the loan transaction request, wherein the transaction identification code of the loan transaction is qhcs-dcs SF14874^1567684809033^ 359572.
The relational database may be an Oracle database for maintaining a record of transactions that have been transacted or are completing transactions.
The transaction record comprises information such as a transaction request, a transaction identification code, a transaction requester identifier, transaction attributes and the like. The transaction requester identifier is information such as an identification number, a name, a mobile phone number and the like of a user triggering the transaction. The transaction attribute information refers to information such as transaction type, transaction amount, transaction occurrence date, transaction occurrence channel, whether the current transaction has an authorization authentication code or an authorization authentication certificate, and the like.
After the user terminal generates a corresponding transaction identification code according to a transaction request message triggered by the user, a transaction record comprising the transaction identification code is stored in a transaction database, so that the transaction record of the transaction occurring in a transaction link is stored.
In some embodiments, referring to fig. 3, storing the transaction record corresponding to the transaction request message in the relational database specifically includes step S1011 and step S1012.
S1011, the user terminal queries the transaction identifier in a relational database to determine whether an identifier identical to the transaction identifier exists in the relational database.
Specifically, after the user generates the transaction identification code corresponding to the transaction request message, the transaction identification code is checked for duplication in the relational database to determine whether the identification code identical to the transaction identification code exists.
And S1012, if the identification code which is the same as the transaction identification code does not exist in the relational database, storing a transaction record corresponding to the transaction request message in the relational database.
Specifically, if the same identification code as the transaction identification code does not exist in the relational database, it is determined that the transaction identification code is unique, and the transaction corresponding to the transaction identification code is a newly generated transaction, and the transaction record corresponding to the transaction identification code is inserted into the relational database for storage.
If the identification code which is the same as the transaction identification code exists in the relational database, the transaction identification code is not unique, the transaction is completed or is being completed, the transaction record corresponding to the transaction identification code is not stored in the database, the transaction request message is not processed, and the situation that the same transaction request message is repeatedly processed due to the fact that the transaction request message is submitted for many times is avoided.
S102, the user side inserts the transaction identification code in the transaction record into the transaction request message to obtain a filled transaction request message, and sends the filled transaction request message to a transfer server.
Specifically, the user side can extract the transaction identification code in the transaction record based on the relational database, and fill the transaction identification code into the head position of the transaction request message to obtain the filled transaction request message, so that the transaction identification code can run through the whole transaction process along with the transaction request message, and a transaction link can be conveniently tracked through the transaction identification code to perform performance monitoring.
For example, a transaction request triggered by a user is encapsulated in an HTTP transaction request message through an HTTP protocol, and a generated transaction identification code is inserted into a header of the transaction request message to obtain a filled transaction request message.
In the specific implementation process, the sending time when the client sends the filled transaction request message to the transit server may also be recorded.
In some embodiments, the transaction link monitoring method further comprises: and the user side caches the transaction record corresponding to the filled transaction request message in a first cache database.
In particular, the first cache database may be a Redis database. And caching the transaction records corresponding to the filled transaction request message in a first cache database, so that the response speed of the user side to the filled transaction request message is improved.
In a specific implementation process, after receiving a transaction request message triggered by a user, the first cache database starts data self-increment, and respectively caches transaction records corresponding to the filled transaction request message in the first cache database. Data duplication or disorder of cache records when caching of transaction records in the first cache database can be reduced by utilizing data self-increment of the first cache database.
S103, the transfer server is connected with a private network according to the filled transaction request message so as to send the filled transaction request message to a private network subsystem.
Specifically, the transit server may be connected to the private network through a private network front-end processor, which may be an ethernet switch, for example.
The transfer server is used for realizing information exchange between the private network and the external network, ensuring that external applications cannot directly access core data of the private network and improving network security. Therefore, after receiving the filled request message, the transit server can connect to the private network through the private network front-end processor according to the filled transaction request message, so as to send the filled transaction request message to the private network subsystem.
In a specific implementation process, the time when the transit server receives the filled transaction request message may also be recorded, so as to determine the connection state between the user side and the transit server according to the time.
In some embodiments, the transaction link monitoring method further comprises: and the transit server caches the received transaction record corresponding to the filled transaction request message in a second cache database.
In particular, the second cache database may also be a Redis database. And caching the transaction records corresponding to the filled transaction request message in a second cache database, so that the response speed of the transfer server to the filled transaction request message is improved.
S104, the private network subsystem processes the filled transaction request message, generates a response message and sends the response message to the user side through the transfer server, wherein the response message comprises the transaction identification code.
Specifically, after receiving the filled transaction request message, the private network subsystem may call related data in the private network to perform corresponding data call and data processing on the filled transaction request message, thereby generating a response message, where the response message also includes a transaction identification code, and send the generated response message to the user side through the transit server, thereby completing the transaction.
In some embodiments, the transaction link monitoring method further comprises: and releasing corresponding transaction records cached in the first cache database and the second cache database according to the response message.
Specifically, after the private network subsystem generates the response packet, it indicates that the transaction corresponding to the response packet is completed, that is, the transaction corresponding to the filled transaction request packet is completed, so that the transaction records cached in the first cache data and the second cache database and corresponding to the response packet can be released according to the response packet, so as to ensure the margins in the first cache database and the second cache database.
And S105, recording the time when the user side, the transfer server and the private network subsystem receive the transaction identification code according to the transaction identification code respectively so as to monitor the user side, the transfer server and the private network subsystem.
Specifically, because the transaction identification code is inserted into the header of the transaction request message, the transaction identification code will circulate in the whole transaction link along with the transaction request message and the response message, so that when a transaction occurs in the transaction link, each node in the transaction link can be monitored for abnormality through the transaction identification code.
When the transaction is sent in the transaction link, the time for the transaction request message or the response message to reach each node in the whole transaction link is predictable, so that the nodes in the transaction link, namely the user side, the transit server and the private network subsystem can be monitored according to the time for the user side, the transit server and the private network subsystem to receive the transaction identification code.
In some embodiments, referring to fig. 4, step S105 specifically includes step S1051 and step S1052.
S1051, recording the time of the user side, the transit server and the private network subsystem receiving the transaction identification code according to the transaction identification code, and respectively calculating the time difference between two adjacent nodes.
Specifically, the time of each node in the transaction link receiving the transaction identification code is respectively recorded according to the transaction identification code, and the time difference between two adjacent nodes is respectively calculated.
That is, the time when the transaction identification code is received by the user side, the transit server and the private network subsystem is respectively recorded, and the time difference when the transaction identification code is received by the user side and the transit server and the time difference when the transaction identification code is received by the transit server and the private network subsystem are calculated.
S1052, if the time difference between the two adjacent nodes is larger than a preset threshold, determining that the two adjacent nodes have data transmission abnormity.
Specifically, when each node in the transaction link is in a normal data transmission state, the time used by the transaction request message to be transmitted from one node to the next node is known. In the implementation process, the time required for data transmission between nodes in the transaction link in the normal state can be tested as a preset threshold. If the time difference between two adjacent nodes is greater than the preset threshold, it indicates that the two adjacent nodes may reach the data transmission bottleneck, resulting in a slow data transmission speed.
That is, the time required for the user side to perform data transmission with the relay server is used as a first threshold, and the time required for the relay server to perform data transmission with the private network subsystem is used as a second threshold.
And comparing the time difference of the transaction identification code received by the user side and the transit server with a first threshold, and if the time difference of the transaction identification code received by the user side and the transit server is greater than a preset threshold, indicating that the data transmission between the user side and the transit server reaches a bottleneck.
And comparing the time difference when the transit server and the private network subsystem receive the transaction identification code with a second threshold, and if the time difference when the transit server and the private network subsystem receive the transaction identification code is greater than the second threshold, indicating that the data transmission between the transit server and the private network subsystem reaches a bottleneck.
It should be noted that the preset threshold may be a plurality of thresholds, and the specific threshold number of the preset threshold should be related to the number of nodes in the transaction link. If there are two nodes in the transaction link, there should be one preset threshold, and if there are three nodes in the transaction link, there should be two preset thresholds.
In some embodiments, before the recording the time when the user side, the transit server, and the private network subsystem receive the transaction identification code according to the transaction identification code, respectively, the transaction link monitoring method includes:
and respectively judging whether the user side, the transfer server and the private network subsystem all receive the transaction identification code so as to monitor data transmission among the user side, the transfer server and the private network subsystem.
Specifically, when the transaction link is monitored to be failed, the failure location can be performed by judging whether each node in the transaction link receives the transaction identification code. If some nodes do not receive the transaction identification code, the fault exists between the node and the adjacent node, so that the fault in the transaction link can be quickly positioned.
That is, if the user receives the transaction identifier and neither the transit server nor the private network subsystem receives the transaction identifier during the process of sending the transaction request message, it may be considered that a fault exists in the data transmission between the user and the transit server, and thus the fault in the transaction link is located.
In the method for monitoring a transaction link provided in the above embodiment, the user side generates a corresponding transaction identification code according to a transaction request message triggered by a user, stores a transaction record including the transaction identification code, inserts the transaction identification code in the transaction record into the transaction request message to obtain a filled transaction request message, and sends the filled transaction request message to the transfer server; the transfer server is connected with a private network and sends the filled transaction request message to a private network subsystem; and finally, the private network subsystem processes the filled transaction request message, generates a response message comprising the transaction identification code and sends the response message to the user side through the transfer server. And finally, monitoring the user side, the transfer server and the private network subsystem based on the time when the user side, the transfer server and the private network subsystem receive the transaction identification code. Each transaction is marked by using the unique transaction identification code generated when the transaction occurs, and the abnormal node in each transaction link is judged according to the time when the node in each transaction link receives the transaction identification code, so that the fault positioning time is shortened, and the fault positioning accuracy is improved.
Referring to fig. 5, fig. 5 is a schematic block diagram of a transaction link monitoring device according to an embodiment of the present application, where the transaction link monitoring device is configured to execute the foregoing transaction link monitoring method. Wherein, the transaction link monitoring device can be configured in a server or a terminal.
The server may be an independent server or a server cluster. The terminal can be an electronic device such as a mobile phone, a tablet computer, a notebook computer, a desktop computer, a personal digital assistant and a wearable device.
As shown in fig. 5, the transaction link monitoring apparatus 200 includes: an identification code generating module 201, a message sending module 202, a message relay module 203, a response generating module 204 and a time monitoring module 205.
The identification code generation module 201 is configured to generate, by a user side, a transaction identification code corresponding to a transaction request message triggered by a user, and store, in a relational database, a transaction record corresponding to the transaction request message, where the transaction record includes the transaction identification code.
The identification code generating module 201 includes an identification code querying sub-module 2011 and an identification code saving sub-module 2012.
Specifically, the identifier query sub-module 2011 is configured to query, by the user side, the transaction identifier in a relational database, so as to determine whether an identifier identical to the transaction identifier exists in the relational database. The identification code saving sub-module 2012 is configured to, if the identification code identical to the transaction identification code does not exist in the relational database, save the transaction record corresponding to the transaction request packet in the relational database.
A message sending module 202, configured to insert the transaction identification code in the transaction record into the transaction request message by the user side, obtain a filled transaction request message, and send the filled transaction request message to a transit server.
The message transfer module 203 is configured to connect the transfer server to a private network according to the filled transaction request message, so as to send the filled transaction request message to a private network subsystem.
A response generating module 204, configured to process the filled transaction request message by the private network subsystem, generate a response message, and send the response message to the user side through the transit server, where the response message includes the transaction identification code.
And the time monitoring module 205 is configured to record the time when the user side, the transit server, and the private network subsystem receive the transaction identification code according to the transaction identification code, so as to monitor the user side, the transit server, and the private network subsystem.
The time monitoring module 205 includes a time difference calculation sub-module 2051 and an anomaly determination sub-module 2052.
Specifically, the time difference calculation sub-module 2051 is configured to record, according to the transaction identifier, the time when the user side, the transit server, and the private network subsystem receive the transaction identifier, and calculate the time difference between two adjacent nodes respectively. The anomaly determination submodule 2052 is configured to determine that data transmission anomaly exists in two adjacent nodes if a time difference between the two adjacent nodes is greater than a preset threshold.
It should be noted that, as will be clear to those skilled in the art, for convenience and brevity of description, the specific working processes of the transaction link monitoring apparatus and each module described above may refer to corresponding processes in the foregoing embodiments of the transaction link monitoring method, and are not described herein again.
The transaction link monitoring apparatus described above may be implemented in the form of a computer program which may be run on a computer device as shown in figure 6.
Referring to fig. 6, fig. 6 is a schematic block diagram of a computer device according to an embodiment of the present disclosure. The computer device may be a server or a terminal.
Referring to fig. 6, the computer device includes a processor, a memory, and a network interface connected through a system bus, wherein the memory may include a nonvolatile storage medium and an internal memory.
The non-volatile storage medium may store an operating system and a computer program. The computer program includes program instructions that, when executed, cause a processor to perform any of the transaction link monitoring methods.
The processor is used for providing calculation and control capability and supporting the operation of the whole computer equipment.
The internal memory provides an environment for the execution of a computer program on a non-volatile storage medium, which when executed by the processor, causes the processor to perform any of the transaction link monitoring methods.
The network interface is used for network communication, such as sending assigned tasks and the like. Those skilled in the art will appreciate that the architecture shown in fig. 6 is merely a block diagram of some of the structures associated with the disclosed aspects and is not intended to limit the computing devices to which the disclosed aspects apply, as particular computing devices may include more or less components than those shown, or may combine certain components, or have a different arrangement of components.
It should be understood that the Processor may be a Central Processing Unit (CPU), and the Processor may be other general purpose processors, Digital Signal Processors (DSPs), Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs) or other Programmable logic devices, discrete Gate or transistor logic devices, discrete hardware components, etc. Wherein a general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
Wherein, in one embodiment, the processor is configured to execute a computer program stored in the memory to implement the steps of:
a user side generates a transaction identification code corresponding to a transaction request message according to the transaction request message triggered by a user, and stores a transaction record corresponding to the transaction request message in a relational database, wherein the transaction record comprises the transaction identification code;
the user side inserts the transaction identification code in the transaction record into the transaction request message to obtain a filled transaction request message, and sends the filled transaction request message to a transfer server;
the transfer server is connected with a private network according to the received filled transaction request message so as to send the filled transaction request message to a private network subsystem;
the private network subsystem processes the filled transaction request message, generates a response message and sends the response message to the user side through the transfer server, wherein the response message comprises the transaction identification code;
and recording the time of receiving the transaction identification code by the user side, the transfer server and the private network subsystem according to the transaction identification code respectively so as to monitor the user side, the transfer server and the private network subsystem.
In one embodiment, when the processor implements the storing of the transaction record corresponding to the transaction request message in the relational database, the processor is configured to implement:
the user side inquires the transaction identification code in a relational database to judge whether the identification code identical to the transaction identification code exists in the relational database;
and if the identification code which is the same as the transaction identification code does not exist in the relational database, storing a transaction record corresponding to the transaction request message in the relational database.
In one embodiment, the processor is further configured to implement:
and the user side caches the transaction record corresponding to the filled transaction request message in a first cache database.
In one embodiment, the processor is further configured to implement:
and the transit server caches the received transaction record corresponding to the filled transaction request message in a second cache database.
In one embodiment, the processor is further configured to implement:
and releasing the transaction record corresponding to the response message, which is cached in the first cache database or the second cache database, according to the response message.
In one embodiment, the processor is configured to, when the time when the user side, the transit server, and the private network subsystem receive the transaction identification code is recorded according to the transaction identification code, so as to monitor the user side, the transit server, and the private network subsystem, respectively, to implement:
recording the time of the user side, the transit server and the private network subsystem for receiving the transaction identification code according to the transaction identification code, and respectively calculating the time difference between two adjacent nodes;
and if the time difference between two adjacent nodes is greater than a preset threshold value, determining that the two adjacent nodes have data transmission abnormity.
In one embodiment, before the time when the client, the transit server and the private network subsystem receive the transaction identification code is recorded according to the transaction identification code, the processor is configured to:
and respectively judging whether the user side, the transfer server and the private network subsystem all receive the transaction identification code so as to monitor data transmission among the user side, the transfer server and the private network subsystem.
The embodiment of the present application further provides a computer-readable storage medium, where a computer program is stored in the computer-readable storage medium, where the computer program includes program instructions, and the processor executes the program instructions to implement any one of the transaction link monitoring methods provided in the embodiments of the present application.
The computer-readable storage medium may be an internal storage unit of the computer device described in the foregoing embodiment, for example, a hard disk or a memory of the computer device. The computer readable storage medium may also be an external storage device of the computer device, such as a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash memory Card (Flash Card), and the like provided on the computer device.
While the invention has been described with reference to specific embodiments, the scope of the invention is not limited thereto, and those skilled in the art can easily conceive various equivalent modifications or substitutions within the technical scope of the invention. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.
Claims (10)
1. A transaction link monitoring method is characterized in that the transaction link comprises a user side, a transfer server and a private network subsystem, and the method comprises the following steps:
a user side generates a transaction identification code corresponding to a transaction request message according to the transaction request message triggered by a user, and stores a transaction record corresponding to the transaction request message in a relational database, wherein the transaction record comprises the transaction identification code;
the user side inserts the transaction identification code in the transaction record into the transaction request message to obtain a filled transaction request message, and sends the filled transaction request message to a transfer server;
the transfer server is connected with a private network according to the received filled transaction request message so as to send the filled transaction request message to a private network subsystem;
the private network subsystem processes the filled transaction request message, generates a response message and sends the response message to the user side through the transfer server, wherein the response message comprises the transaction identification code;
and recording the time of receiving the transaction identification code by the user side, the transfer server and the private network subsystem according to the transaction identification code respectively so as to monitor the user side, the transfer server and the private network subsystem.
2. The transaction link monitoring method according to claim 1, wherein the storing of the transaction record corresponding to the transaction request message in the relational database includes:
the user side inquires the transaction identification code in a relational database to judge whether the identification code identical to the transaction identification code exists in the relational database;
and if the identification code which is the same as the transaction identification code does not exist in the relational database, storing a transaction record corresponding to the transaction request message in the relational database.
3. The transaction link monitoring method of claim 1, wherein the method comprises:
and the user side caches the transaction record corresponding to the filled transaction request message in a first cache database.
4. The transaction link monitoring method of claim 1, wherein the method comprises:
and the transit server caches the received transaction record corresponding to the filled transaction request message in a second cache database.
5. The transaction link monitoring method according to claim 3 or 4, wherein the method comprises:
and releasing the transaction record corresponding to the response message, which is cached in the first cache database or the second cache database, according to the response message.
6. The method for monitoring transaction link according to claim 1, wherein the recording the time when the transaction identification code is received by the user terminal, the transit server and the private network subsystem according to the transaction identification code respectively, so as to monitor the user terminal, the transit server and the private network subsystem, comprises:
recording the time of the user side, the transit server and the private network subsystem for receiving the transaction identification code according to the transaction identification code, and respectively calculating the time difference between two adjacent nodes;
and if the time difference between two adjacent nodes is greater than a preset threshold value, determining that the two adjacent nodes have data transmission abnormity.
7. The transaction link monitoring method of claim 1, wherein before the time when the user terminal, the transit server and the private network subsystem receive the transaction identification code is recorded according to the transaction identification code, respectively, the method comprises:
and respectively judging whether the user side, the transfer server and the private network subsystem all receive the transaction identification code so as to monitor data transmission among the user side, the transfer server and the private network subsystem.
8. A transaction link monitoring device, wherein the transaction link includes a client, a transit server and a private network subsystem, and the system includes:
the identification code generation module is used for generating a transaction identification code corresponding to a transaction request message according to the transaction request message triggered by a user side and storing a transaction record corresponding to the transaction request message in a relational database, wherein the transaction record comprises the transaction identification code;
the message sending module is used for inserting the transaction identification code in the transaction record into the transaction request message by the user side to obtain a filled transaction request message and sending the filled transaction request message to a transfer server;
the message transfer module is used for connecting the transfer server with a private network according to the received filled transaction request message so as to send the filled transaction request message to a private network subsystem;
a response generation module, configured to process the filled transaction request message by the private network subsystem, generate a response message, and send the response message to the user side through the transit server, where the response message includes the transaction identification code;
and the time monitoring module is used for recording the time of receiving the transaction identification code by the user side, the transit server and the private network subsystem according to the transaction identification code so as to monitor the user side, the transit server and the private network subsystem.
9. A computer device, wherein the computer device comprises a memory and a processor;
the memory is used for storing a computer program;
the processor for executing the computer program and implementing the transaction link monitoring method of any one of claims 1 to 7 when executing the computer program.
10. A computer-readable storage medium, characterized in that the computer-readable storage medium stores a computer program which, when executed by a processor, causes the processor to implement the transaction link monitoring method according to any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010463577.1A CN111884824A (en) | 2020-05-27 | 2020-05-27 | Transaction link monitoring method, device, equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010463577.1A CN111884824A (en) | 2020-05-27 | 2020-05-27 | Transaction link monitoring method, device, equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111884824A true CN111884824A (en) | 2020-11-03 |
Family
ID=73154073
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010463577.1A Pending CN111884824A (en) | 2020-05-27 | 2020-05-27 | Transaction link monitoring method, device, equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111884824A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113326072A (en) * | 2021-05-24 | 2021-08-31 | 北京计算机技术及应用研究所 | Real-time monitoring method based on nonvolatile memory under Feiteng server platform |
| CN117974171A (en) * | 2024-04-01 | 2024-05-03 | 贵州华谊联盛科技有限公司 | Data element transaction traceability system based on digital watermark |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20080250128A1 (en) * | 2007-04-03 | 2008-10-09 | Alvan Sargent | Automated time zone based grouping |
| CN106980975A (en) * | 2017-02-24 | 2017-07-25 | 济南汉泰信息科技有限公司 | A kind of method of payment, system and intelligent terminal |
| CN108462750A (en) * | 2018-03-22 | 2018-08-28 | 平安好房（上海）电子商务有限公司 | Distribution calls method for tracing, operation system, monitoring system and storage medium |
| CN108833184A (en) * | 2018-06-29 | 2018-11-16 | 腾讯科技（深圳）有限公司 | Service fault localization method, device, computer equipment and storage medium |
| CN109104302A (en) * | 2018-07-18 | 2018-12-28 | 杭州鑫合汇互联网金融服务有限公司 | A kind of full link tracing monitoring method |
| CN110888783A (en) * | 2019-11-21 | 2020-03-17 | 望海康信(北京)科技股份公司 | Monitoring method and device of micro-service system and electronic equipment |
| CN111124731A (en) * | 2019-12-20 | 2020-05-08 | 浪潮电子信息产业股份有限公司 | File system abnormity monitoring method, device, equipment and medium |
-
2020
- 2020-05-27 CN CN202010463577.1A patent/CN111884824A/en active Pending
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20080250128A1 (en) * | 2007-04-03 | 2008-10-09 | Alvan Sargent | Automated time zone based grouping |
| CN106980975A (en) * | 2017-02-24 | 2017-07-25 | 济南汉泰信息科技有限公司 | A kind of method of payment, system and intelligent terminal |
| CN108462750A (en) * | 2018-03-22 | 2018-08-28 | 平安好房（上海）电子商务有限公司 | Distribution calls method for tracing, operation system, monitoring system and storage medium |
| CN108833184A (en) * | 2018-06-29 | 2018-11-16 | 腾讯科技（深圳）有限公司 | Service fault localization method, device, computer equipment and storage medium |
| CN109104302A (en) * | 2018-07-18 | 2018-12-28 | 杭州鑫合汇互联网金融服务有限公司 | A kind of full link tracing monitoring method |
| CN110888783A (en) * | 2019-11-21 | 2020-03-17 | 望海康信(北京)科技股份公司 | Monitoring method and device of micro-service system and electronic equipment |
| CN111124731A (en) * | 2019-12-20 | 2020-05-08 | 浪潮电子信息产业股份有限公司 | File system abnormity monitoring method, device, equipment and medium |
Non-Patent Citations (2)
| Title |
|---|
| FELIPE MATA等: "Quality of Service analysis of Internet links with minimal information", IEEE * |
| 徐明伟;彭艳海;李琦;: "轻量级隧道虚链路状态检测协议", 清华大学学报(自然科学版), no. 11 * |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113326072A (en) * | 2021-05-24 | 2021-08-31 | 北京计算机技术及应用研究所 | Real-time monitoring method based on nonvolatile memory under Feiteng server platform |
| CN113326072B (en) * | 2021-05-24 | 2023-11-24 | 北京计算机技术及应用研究所 | Real-time monitoring method based on nonvolatile memory under Feiteng server platform |
| CN117974171A (en) * | 2024-04-01 | 2024-05-03 | 贵州华谊联盛科技有限公司 | Data element transaction traceability system based on digital watermark |
| CN117974171B (en) * | 2024-04-01 | 2024-05-31 | 贵州华谊联盛科技有限公司 | Data element transaction traceability system based on digital watermark |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107992398A (en) | The monitoring method and monitoring system of a kind of operation system | |
| US10296435B2 (en) | Storage of mass data for monitoring | |
| CN112035472B (en) | Data processing method, device, computer equipment and storage medium | |
| CN111884824A (en) | Transaction link monitoring method, device, equipment and storage medium | |
| JP2009531750A (en) | Method and system for risk monitoring in online business | |
| CN111641563B (en) | Flow self-adaption method and system based on distributed scene | |
| CN111475376A (en) | Method and device for processing test data, computer equipment and storage medium | |
| CN115543871B (en) | Data storage method and related equipment | |
| US20210374029A1 (en) | System and Method for Monitoring Computing Platform Parameters and Dynamically Generating and Deploying Monitoring Packages | |
| CN116743619B (en) | Network service testing method, device, equipment and storage medium | |
| CN111125168B (en) | Data processing method and device, electronic equipment and storage medium | |
| US9329972B2 (en) | Implementing client based throttled error logging in a computing device | |
| CN115756309A (en) | Battery management equipment parameter storage method, battery management equipment and energy storage system | |
| CN112559290B (en) | Service call monitoring method, device, computer equipment and storage medium | |
| CN113411191B (en) | Data auditing method and device | |
| CN106445837B (en) | Embedded device history record storage and loading management implementation method and device | |
| JP5538810B2 (en) | Mass data storage system for monitoring | |
| CN114513469A (en) | Traffic shaping method and device for distributed system and storage medium | |
| CN109254880A (en) | A kind of method and device handling database delay machine | |
| CN109034768B (en) | Financial reconciliation method, apparatus, computer device and storage medium | |
| CN113791922B (en) | Exception handling method, system and device for distributed storage system | |
| US8032797B1 (en) | Storage of mass data for monitoring | |
| CN108228420A (en) | The method, apparatus of IO monitoring and the realization device of IO monitoring | |
| US9244832B1 (en) | Cache learning model | |
| CN114296993A (en) | Data verification method, equipment and medium based on cache |
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 |