CN112532478B - Link relation tracking method, system, checking method, device and equipment - Google Patents
Link relation tracking method, system, checking method, device and equipment Download PDFInfo
- Publication number
- CN112532478B CN112532478B CN202011324525.2A CN202011324525A CN112532478B CN 112532478 B CN112532478 B CN 112532478B CN 202011324525 A CN202011324525 A CN 202011324525A CN 112532478 B CN112532478 B CN 112532478B
- Authority
- CN
- China
- Prior art keywords
- link
- server
- message
- service end
- data storage
- 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.)
- Active
Links
Images
Classifications
-
- 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/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
-
- 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/0631—Management of faults, events, alarms or notifications using root cause analysis; using analysis of correlation between notifications, alarms or events based on decision criteria, e.g. hierarchy, tree or time analysis
-
- 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/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
- H04L43/0805—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability
- H04L43/0817—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability by checking functioning
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Environmental & Geological Engineering (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The invention relates to the technical field of internet and discloses a link relation tracking method, a system, a checking method, a device and equipment, wherein the link relation tracking method comprises the following steps: the client side initiates a first access request to a first service side; the first server sends a first link message to an interactive data storage server through a first gateway; the first server side initiates a second access request to a second server side, and adds link tracking information required by link tracking at a message header of the second access request through an interception layer; the second server sends a second link message to the interactive data storage server through a second gateway according to the link tracking information; and the interactive data storage service end acquires the link relation between the first service end and the second service end according to the first link message and the second link message, and can acquire the link relation among multiple service calls.
Description
Technical Field
The invention relates to the technical field of internet, in particular to a method, a system, a checking method, a device and equipment for tracking a link relation.
Background
At present, for network access, an access link relationship is usually adopted to embody an access path of a user. However, in one access request, there are often a plurality of services that the request needs to invoke, and the existing link relation tracking method can only simply obtain a single service invocation obtaining the access request, and cannot effectively distinguish multiple service invocations belonging to the same access request, and neglects the link interrelation among multiple service invocations.
Disclosure of Invention
The technical problem to be solved by the embodiment of the invention is as follows: a method, a system, a checking method, a device and equipment for tracking the link relation are provided, and the link relation among multiple service calls is obtained.
In order to solve the above technical problem, in a first aspect, an embodiment of the present invention provides a link relation tracking method, where the method includes: the client side initiates a first access request to a first service side;
the first server sends a first link message to an interactive data storage server through a first gateway;
the first server side initiates a second access request to a second server side, and adds link tracking information required by link tracking at a message header of the second access request through an interception layer;
the second server sends a second link message to the interactive data storage server through a second gateway according to the link tracking information;
and the interactive data storage service end acquires the link relation between the first service end and the second service end according to the first link message and the second link message.
As a preferred scheme, the first service end includes a first adaptation layer, where the first adaptation layer is configured to perform adaptation processing on technology stacks of all services of the first service end;
the second server includes a second adaptation layer, and the second adaptation layer is configured to perform adaptation processing on the technology stacks of all services of the second server.
As a preferred scheme, the adaptation principle of the first adaptation layer and the second adaptation layer is as follows:
detecting whether a service uses a first framework;
if so, the service uses the first writing method, and if not, the service uses the second writing method.
As a preferred scheme, the first framework is a spring mvc framework, the first writing is a spring mvc writing, and the second writing is a Jersey writing.
In order to solve the above technical problem, in a second aspect, an embodiment of the present invention provides a link tracking system, which includes a client, a first server, a second server, and an interactive data storage server, wherein,
the client is used for initiating a first access request to a first service terminal;
the first server side is used for sending a first link message to the interactive data storage server side through the first gateway;
the first server is also used for initiating a second access request to a second server and adding link tracking information required by link tracking at a message header of the second access request through an interception layer;
the second server is used for sending a second link message to the interactive data storage server through a second gateway according to the link tracking information;
and the interactive data storage service end is used for acquiring the link relation between the first service end and the second service end according to the first link message and the second link message.
In order to solve the foregoing technical problem, in a third aspect, an embodiment of the present invention provides a link relation checking method, where the method is applied to an interactive data storage server, and the method includes:
receiving a first link message of a first server;
receiving a second link message of a second server;
and checking the link relation between the first service end and the second service end according to the first link message and the second link message.
As a preferred scheme, the first service end includes a first adaptation layer, where the first adaptation layer is configured to perform adaptation processing on technology stacks of all services of the first service end;
the second server includes a second adaptation layer, and the second adaptation layer is configured to perform adaptation processing on the technology stacks of all services of the second server.
As a preferred scheme, the adaptation principle of the first adaptation layer and the second adaptation layer is as follows:
detecting whether a service uses a first framework;
if so, the service uses the first writing method, and if not, the service uses the second writing method.
In order to solve the foregoing technical problem, in a fourth aspect, an embodiment of the present invention provides a link relationship checking apparatus, where the apparatus is applied to an interactive data storage server, and the apparatus includes:
a first receiving module, configured to receive a first link message of a first service end;
the second receiving module is used for receiving a second link message of a second server;
and the link relation checking module is used for checking the link relation between the first service end and the second service end according to the first link message and the second link message.
In order to solve the technical problem, in a fifth aspect, an embodiment of the present invention provides a terminal device, where the device includes a processor, a memory, and a computer program stored in the memory and configured to be executed by the processor, and when the computer program is executed by the processor, the terminal device implements the link relation viewing method according to any one of the third aspects.
In order to solve the above technical problem, according to a sixth aspect, an embodiment of the present invention provides a plug-in, which is capable of implementing the link relation tracking method according to any one of the first aspects and/or implementing the link relation viewing method according to any one of the third aspects.
Compared with the prior art, the link relation tracking method, the system, the checking method, the checking device, the equipment and the plug-in provided by the embodiment of the invention have the beneficial effects that: when a client needs to call a service, a first access request is firstly initiated to a first server, when the first server receives the first access request, a first link message is firstly sent to an interactive data storage server, and because the first link message does not reach the end point of the first access request, the first server initiates a second access request to a second server, and link tracking information required by this link tracking is added to a second message header through an interception layer; when the second server receives the second access request, a second link message is sent to the interactive data storage server according to the link tracking information, and finally, the interactive data storage server acquires the link relation between the first server and the second server according to the first link message and the second link message, so that the link relation between multiple service calls of the client can be acquired and checked in one access request of the client; the server side is provided with an adaptation layer, can adapt the technical stacks of all services, and is compatible with a plurality of technical stacks.
Drawings
In order to more clearly illustrate the technical features of the embodiments of the present invention, the drawings needed to be used in the embodiments of the present invention will be briefly described below, and it is apparent that the drawings described below are only some embodiments of the present invention, and it is obvious for those skilled in the art that other drawings can be obtained based on the drawings without inventive labor.
FIG. 1 is a flow chart illustrating a method for tracking a link relationship according to a preferred embodiment of the present invention;
FIG. 2 is a schematic structural diagram of a preferred embodiment of a link relation tracking system provided in the present invention;
FIG. 3 is a flow chart diagram of a preferred embodiment of a link relation viewing method provided by the present invention;
fig. 4 is a schematic structural diagram of a preferred embodiment of a link relation viewing apparatus provided in the present invention;
fig. 5 is a schematic structural diagram of a preferred embodiment of a terminal device provided by the present invention.
Detailed Description
In order to make the technical features, objects and effects of the present invention more clearly understood, the following detailed description of the embodiments of the present invention is made with reference to the accompanying drawings and examples. The following examples are intended to illustrate the invention, but are not intended to limit the scope of the invention. Other embodiments, which can be derived by those skilled in the art from the embodiments of the present invention without inventive step, shall fall within the scope of the present invention.
In the description of the present invention, it should be understood that the numbers themselves, such as "first", "second", etc., are used only for distinguishing the described objects, do not have a sequential or technical meaning, and cannot be understood as defining or implying importance of the described objects.
It should be noted that the micro service architecture is a distributed architecture, which divides service units according to services, and a distributed system often has many service units. Due to the large number of service units and the complexity of the service, if errors and exceptions occur, the positioning is difficult to carry out. Mainly, one request may need to call many services, and the complexity of calling internal services determines that the problem is difficult to locate. Therefore, in the micro-service architecture, distributed link relation tracking must be realized to follow up which services participate in a request, and the participation sequence is the same, so that the steps of each request are clearly visible, problems are caused, and positioning is fast.
Fig. 1 is a schematic flow chart of a link relation tracking method according to a preferred embodiment of the present invention.
As shown in fig. 1, the link relation tracking method includes:
step S11: the client side initiates a first access request to a first service side;
step S12: the first server sends a first link message to an interactive data storage server through a first gateway;
step S13: the first server side initiates a second access request to a second server side, and adds link tracking information required by link tracking at a message header of the second access request through an interception layer;
step S14: the second server sends a second link message to the interactive data storage server through a second gateway according to the link tracking information;
step S15: and the interactive data storage service end acquires the link relation between the first service end and the second service end according to the first link message and the second link message.
Specifically, when a client initiates a first access request to a first service end, because the request needs more than one service to be invoked, each service is in a different service end, the first service end first sends a first link message to an interactive data service end through a first gateway, and simultaneously initiates a second access request to a second service end and adds link trace information needed for link trace at a message header of the second access request through an interception layer; when the second server receives the second access request, a second link message is sent to the interactive data storage server through a second gateway according to the link tracking information; and finally, the interactive data storage service side acquires the link relationship between the first service side and the second service side according to the first link message and the second link message, and the link relationship can be viewed through a viewing tool, for example, through Jaeger-ui.
Wherein the link tracing information includes but is not limited to the following data information:
1)"x-request-id"；
2)"x-b3-traceid"；
3)"x-b3-spanid"；
4)"x-b3-sampled"；
5)"x-b3-flags"；
6)"x-ot-span-context"；
7)"x-datadog-trace-id"；
8)"x-datadog-parent-id"；
9)"x-datadog-sampled"；
10)"end-user"；
11)"user-agent"。
when the first server sends the second access request to the second server, the first server carries the header parameters and the values, and then intercepts the information through an interception layer and transmits the information to the next service, so that the link relation can be tracked through the transmission of the information.
It should be understood that if the second server is still not the call end point of the first access request, the method further includes:
the second server initiates a third access request to a subsequent server, and adds second link tracking information required by link tracking at a message header of the third access request through an interception layer;
the subsequent server side sends a third link message to the interactive data storage server side through a third gateway according to the second link tracking information;
and the interactive data storage service end acquires the link relation of the first service end, the second service end and the subsequent service end according to the first link message, the second link message and the third link message.
The second server may be one server or a plurality of servers; the subsequent server may be one server or a plurality of servers.
In a preferred embodiment, the first service end includes a first adaptation layer, and the first adaptation layer is configured to adapt technology stacks of all services of the first service end;
the second server includes a second adaptation layer, and the second adaptation layer is configured to perform adaptation processing on the technology stacks of all services of the second server.
Further, the adaptation principle of the first adaptation layer and the second adaptation layer is as follows:
detecting whether a service uses a first framework;
if so, the service uses the first writing method, and if not, the service uses the second writing method.
Further, the first framework is a spring mvc framework, the first writing is a spring mvc writing, and the second writing is a Jersey writing.
It should be noted that, in JAVA WEB engineering, a framework of SpringMVC or Jersey is used as a microservice, and if different technology stacks interact with each other, 2 sets of codes need to be developed, and one set of codes cannot be used for compatibility.
In this embodiment, an adaptation layer is set in each service end to perform adaptation processing on the technical stacks of all services, and the adaptation principle of the adaptation layer is to automatically detect whether a service uses a SpringMVC framework, where a SpringMVC writing method is used if the service uses the SpringMVC framework, and a Jersey writing method is used if the service does not use the SpringMVC framework.
Specifically, when a public void application (RequestTemplate) is detected, a Jersey writing method is adopted to indicate that the service uses a default Jersey framework; when a public void application (RequestTemplate, String controller) is detected, the SpringMVC writing method is adopted to indicate that the service uses the SpringMVC framework.
In summary, the embodiments of the present invention provide a link relationship tracking method, where an interactive data storage server obtains a link relationship between servers according to a received link message, and can obtain and view the link relationship between multiple service calls in a single access request of a client; each server has an adaptation layer, can adapt the technical stacks of all services, and is compatible with a plurality of technical stacks.
Fig. 2 is a schematic structural diagram of a preferred embodiment of the link relation tracking system according to the present invention, which is capable of implementing all the processes of the link relation tracking method according to any of the above embodiments.
As shown in fig. 2, the system includes: a client, a first service end, a second service end and an interactive data storage service end, wherein,
the client is used for initiating a first access request to a first service terminal;
the first server side is used for sending a first link message to the interactive data storage server side through the first gateway;
the first server is also used for initiating a second access request to a second server and adding link tracking information required by link tracking at a message header of the second access request through an interception layer;
the second server is used for sending a second link message to the interactive data storage server through a second gateway according to the link tracking information;
and the interactive data storage service end is used for acquiring the link relation between the first service end and the second service end according to the first link message and the second link message.
The interactive data storage server and the client can be arranged in the same terminal; or, the interactive data storage service end and the first service end or the second service end are arranged in the same terminal.
Preferably, the first service end includes a first adaptation layer, and the first adaptation layer is configured to perform adaptation processing on technology stacks of all services of the first service end;
the second server includes a second adaptation layer, and the second adaptation layer is configured to perform adaptation processing on the technology stacks of all services of the second server.
Preferably, the adaptation principle of the first adaptation layer and the second adaptation layer is as follows:
detecting whether a service uses a first framework;
if so, the service uses the first writing method, and if not, the service uses the second writing method.
Preferably, the first framework is a spring mvc framework, the first writing is a spring mvc writing, and the second writing is a Jersey writing.
The link relation tracking system provided by the embodiment of the invention can acquire and check the link relation among multiple service calls in one access request initiated by a client; each server has an adaptation layer, can adapt the technical stacks of all services, and is compatible with a plurality of technical stacks.
Fig. 3 is a schematic flow chart of a preferred embodiment of a link relationship checking method provided by the present invention, where the link relationship checking method is applied to an interactive data storage server.
As shown in fig. 3, the link relationship checking method includes:
x11: receiving a first link message of a first server;
x12: receiving a second link message of a second server;
x13: and checking the link relation between the first service end and the second service end according to the first link message and the second link message.
The operations performed by the first server and the second server are the same as those performed in the link relation tracking method according to any of the above embodiments, and are not described herein again.
Preferably, the first service end includes a first adaptation layer, and the first adaptation layer is configured to perform adaptation processing on technology stacks of all services of the first service end;
the second server includes a second adaptation layer, and the second adaptation layer is configured to perform adaptation processing on the technology stacks of all services of the second server.
Further, the adaptation principle of the first adaptation layer and the second adaptation layer is as follows:
detecting whether a service uses a first framework;
if so, the service uses the first writing method, and if not, the service uses the second writing method.
Further, the first framework is a spring mvc framework, the first writing is a spring mvc writing, and the second writing is a Jersey writing.
The link relation checking method provided by the embodiment of the invention can be used for acquiring and checking the link relation among multiple service calls of the access request initiated by the client at the interactive data storage server.
It should be understood that all or part of the processes in the link relationship checking method may be implemented by the present invention, and may also be implemented by a computer program instructing related hardware, where the computer program may be stored in a computer-readable storage medium, and when the computer program is executed by a processor, the steps of the link relationship checking method may be implemented. Wherein the computer program comprises computer program code, which may be in the form of source code, object code, an executable file or some intermediate form, etc. The computer readable medium may include: any entity or device capable of carrying the computer program code, recording medium, usb disk, removable hard disk, magnetic disk, optical disk, computer Memory, Read-Only Memory (ROM), Random Access Memory (RAM), electrical carrier wave signals, telecommunications signals, software distribution medium, and the like. It should be noted that the computer readable medium may contain other components which may be suitably increased or decreased as required by legislation and patent practice in jurisdictions, for example, in some jurisdictions, in accordance with legislation and patent practice, the computer readable medium does not include electrical carrier signals and telecommunications signals.
It should be noted that the link relationship tracking method and/or the link relationship checking method described in any of the above embodiments may also be made into a form of a plug-in, where the plug-in is placed in a core package, the core package manages each plug-in therein, and the core package can be seamlessly loaded in a Springboot project. The core package manages the plug-in version number in a unified mode without considering the compatibility problem. And 10% of functions in the core package are called through 1-2 lines of codes, and the rest 90% of functions are realized in a configuration mode. The core package can provide rapid project building, 90% of plug-in core packages in the project are included, each project group is not required to be built, and high-quality projects can be guaranteed.
Further, the core package also comprises a plug-in capable of realizing log collection.
In a preferred embodiment, the log collection is implemented by the following steps:
capturing log data output by a terminal console;
storing the log data into a local thread;
performing real-time anomaly analysis on log data stored in a local thread, and generating an anomaly result when the anomaly analysis result is abnormal;
and transmitting the abnormal result to the terminal console in real time.
Preferably, the performing real-time exception analysis on the log data stored in the local thread, and generating an exception result when the exception analysis result indicates that an exception exists, specifically includes:
judging whether log data stored in a local thread contains abnormity or not;
when the log data stored in the local thread contains an exception, judging whether the exception is one or two of unknown exception and system exception;
when the abnormality is unknown abnormality, generating a first abnormality result;
when the abnormality is system abnormality, generating a second abnormality result;
when the abnormity is unknown abnormity and system abnormity, generating a third abnormity result;
then, the abnormal result is transmitted to the terminal console in real time, specifically:
and transmitting the first abnormal result, the second abnormal result or the third abnormal result to the terminal console in real time.
Preferably, the unknown exception is a middleware exception; the system exception is one or two of a code logic exception and a network interaction exception.
Preferably, the first abnormal result includes: the system comprises a first exception file, a first exception name, a first exception row number and first exception information;
the second exception result includes: the second exception file, the second exception name, the second exception row number and the second exception information;
the third anomaly result comprises: a third exception file, a third exception name, a third exception line number, and third exception information.
Preferably, the transmitting the abnormal result to the terminal console in real time specifically includes:
packaging the abnormal result according to a message queue mode;
intercepting the packaged abnormal result according to the mode of the information segment; wherein the size of each intercepted information segment does not exceed a first threshold value;
and connecting the JMS process of the message transmission queue with a message receiving queue of the terminal controller, and transmitting each intercepted information segment to the terminal console in a segmented manner.
This nuclear core package is through tracing, looking over and collecting in real time to the link relation, carries out automatic error finding early warning, can carry out lasting control to each microservice to reach the problem very first time and know, effective and quick solution problem guarantees the stability of project.
Fig. 4 is a schematic structural diagram of a preferred embodiment of a link relationship checking apparatus provided in the present invention, where the apparatus is applied to an interactive data storage server, and the apparatus can implement all the processes of the link relationship checking method described in any of the above embodiments.
As shown in fig. 4, the apparatus includes:
a first receiving module 21, configured to receive a first link message of a first server;
a second receiving module 22, configured to receive a second link message of a second server;
and a link relationship checking module 23, checking a link relationship between the first service end and the second service end according to the first link message and the second link message.
Preferably, the first service end includes a first adaptation layer, and the first adaptation layer is configured to perform adaptation processing on technology stacks of all services of the first service end;
the second server includes a second adaptation layer, and the second adaptation layer is configured to perform adaptation processing on the technology stacks of all services of the second server.
Further, the adaptation principle of the first adaptation layer and the second adaptation layer is as follows:
detecting whether a service uses a first framework;
if so, the service uses the first writing method, and if not, the service uses the second writing method.
Further, the first framework is a spring mvc framework, the first writing is a spring mvc writing, and the second writing is a Jersey writing.
The link relation checking device provided by the embodiment of the invention can acquire and check the link relation among multiple service calls of the access request initiated by the client at the interactive data storage server.
Fig. 5 is a schematic structural diagram of a preferred embodiment of a terminal device provided in the present invention, where the device is capable of implementing all the processes of the link relationship checking method described in any of the above embodiments.
As shown in fig. 5, the apparatus includes a memory 31, a processor 32; wherein, the memory 31 stores therein a computer program configured to be executed by the processor 32, and when being executed by the processor 32, the computer program implements the link relation checking method according to any one of the above embodiments.
The terminal equipment provided by the embodiment of the invention can acquire and check the link relation among multiple service calls of the access request initiated by the client.
Illustratively, the computer program may be divided into one or more modules/units, which are stored in the memory 31 and executed by the processor 32 to accomplish the present invention. The one or more modules/units may be a series of computer program instruction segments capable of performing specific functions, which are used for describing the execution process of the computer program in the terminal device.
The Processor 32 may be a Central Processing Unit (CPU), other general purpose Processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other Programmable logic device, discrete Gate or transistor logic, discrete hardware components, etc. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
The memory 31 may be used for storing the computer programs and/or modules, and the processor 32 implements various functions of the terminal device by running or executing the computer programs and/or modules stored in the memory 31 and calling data stored in the memory 31. The memory 31 may mainly include a program storage area and a data storage area, wherein the program storage area may store an operating system, an application program required by at least one function (such as a sound playing function, an image playing function, etc.), and the like; the storage data area may store data (such as audio data, a phonebook, etc.) created according to the use of the cellular phone, and the like. In addition, the memory 31 may include high-speed random access memory, and may also include non-volatile memory, such as a hard disk, a memory, a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash memory Card (Flash Card), at least one magnetic disk storage device, a Flash memory device, or other volatile solid state storage device.
It should be noted that the terminal device includes, but is not limited to, the processor 32 and the memory 31, and those skilled in the art will understand that the structural diagram of fig. 5 is only an example of the terminal device, and does not constitute a limitation to the terminal device, and may include more components than those shown in the figure, or combine some components, or different components.
The above description is only a preferred embodiment of the present invention, but the scope of the present invention is not limited thereto, and it should be noted that, for those skilled in the art, several equivalent obvious modifications and/or equivalent substitutions can be made without departing from the technical principle of the present invention, and these obvious modifications and/or equivalent substitutions should also be regarded as the scope of the present invention.
Claims (10)
1. A method for link relationship tracking, the method comprising:
the client side initiates a first access request to a first service side;
the first server sends a first link message to an interactive data storage server through a first gateway;
the first server side initiates a second access request to a second server side, and adds link tracking information required by link tracking at a message header of the second access request through an interception layer;
the second server sends a second link message to the interactive data storage server through a second gateway according to the link tracking information;
and the interactive data storage service end acquires the link relation between the first service end and the second service end according to the first link message and the second link message.
2. The link relation tracking method according to claim 1, wherein the first service end includes a first adaptation layer, and the first adaptation layer is configured to adapt technology stacks of all services of the first service end;
the second server includes a second adaptation layer, and the second adaptation layer is configured to perform adaptation processing on the technology stacks of all services of the second server.
3. The link relation tracking method according to claim 2, wherein the adaptation principle of the first adaptation layer and the second adaptation layer is:
detecting whether a service uses a first framework;
if so, the service uses the first writing method, and if not, the service uses the second writing method.
4. The link relationship tracking method of claim 3, wherein the first frame is a springMVC frame, the first writing is a springMVC writing, and the second writing is a Jersey writing.
5. A link relation tracking system is characterized in that the system comprises a client, a first server, a second server and an interactive data storage server, wherein,
the client is used for initiating a first access request to a first service terminal;
the first server side is used for sending a first link message to the interactive data storage server side through the first gateway;
the first server is also used for initiating a second access request to a second server and adding link tracking information required by link tracking at a message header of the second access request through an interception layer;
the second server is used for sending a second link message to the interactive data storage server through a second gateway according to the link tracking information;
and the interactive data storage service end is used for acquiring the link relation between the first service end and the second service end according to the first link message and the second link message.
6. A link relation viewing method is applied to an interactive data storage server side, and comprises the following steps:
receiving a first link message of a first server; the client side initiates a first access request to a first server side; the first server sends a first link message to an interactive data storage server through a first gateway;
receiving a second link message of a second server; the first server initiates a second access request to a second server, and adds link tracking information required by link tracking at a message header of the second access request through an interception layer; the second server sends a second link message to the interactive data storage server through a second gateway according to the link tracking information;
and checking the link relation between the first service end and the second service end according to the first link message and the second link message.
7. The link relationship viewing method according to claim 6, wherein the first service end includes a first adaptation layer, and the first adaptation layer is configured to adapt the technology stacks of all services of the first service end;
the second server includes a second adaptation layer, and the second adaptation layer is configured to perform adaptation processing on the technology stacks of all services of the second server.
8. The link relationship viewing method according to claim 7, wherein the adaptation principle of the first adaptation layer and the second adaptation layer is:
detecting whether a service uses a first framework;
if so, the service uses the first writing method, and if not, the service uses the second writing method.
9. A link relation viewing device, applied to an interactive data storage server, comprises:
a first receiving module, configured to receive a first link message of a first service end; the client side initiates a first access request to a first server side; the first server sends a first link message to an interactive data storage server through a first gateway;
the second receiving module is used for receiving a second link message of a second server; the first server initiates a second access request to a second server, and adds link tracking information required by link tracking at a message header of the second access request through an interception layer; the second server sends a second link message to the interactive data storage server through a second gateway according to the link tracking information;
and the link relation checking module is used for checking the link relation between the first service end and the second service end according to the first link message and the second link message.
10. A terminal device, characterized in that the device comprises a processor, a memory, and a computer program stored in the memory and configured to be executed by the processor, the computer program, when executed by the processor, implementing the link relationship viewing method according to any one of claims 6 to 8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011324525.2A CN112532478B (en) | 2020-11-23 | 2020-11-23 | Link relation tracking method, system, checking method, device and equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011324525.2A CN112532478B (en) | 2020-11-23 | 2020-11-23 | Link relation tracking method, system, checking method, device and equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112532478A CN112532478A (en) | 2021-03-19 |
| CN112532478B true CN112532478B (en) | 2022-05-03 |
Family
ID=74992878
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011324525.2A Active CN112532478B (en) | 2020-11-23 | 2020-11-23 | Link relation tracking method, system, checking method, device and equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112532478B (en) |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109921927A (en) * | 2019-02-20 | 2019-06-21 | 苏州人之众信息技术有限公司 | Real-time calling D-chain trace method based on micro services |
| CN110262889A (en) * | 2019-06-27 | 2019-09-20 | 深圳前海微众银行股份有限公司 | A kind of link tracing method and device |
| CN110442641A (en) * | 2019-08-06 | 2019-11-12 | 中国工商银行股份有限公司 | A kind of link topology figure methods of exhibiting, device, storage medium and equipment |
| CN110717132A (en) * | 2019-09-05 | 2020-01-21 | 深圳平安通信科技有限公司 | Data collection method and pushing method for full-link monitoring system and related equipment |
Family Cites Families (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9203872B2 (en) * | 2010-02-19 | 2015-12-01 | Microsoft Technology Licensing, Llc | Distributed connectivity policy enforcement with ICE |
| CN104301929B (en) * | 2014-09-30 | 2018-02-02 | 大唐移动通信设备有限公司 | A kind of measurement report report method and equipment |
| CN107135276A (en) * | 2017-06-28 | 2017-09-05 | 北京中电普华信息技术有限公司 | A kind of full link monitoring methods, devices and systems under micro services framework |
| CN110069354A (en) * | 2019-04-15 | 2019-07-30 | 必成汇(成都)科技有限公司 | The full link trace method of micro services and micro services framework |
| CN110362550A (en) * | 2019-07-08 | 2019-10-22 | 紫光云技术有限公司 | The log system of distributed link tracking |
| CN111858248B (en) * | 2020-07-20 | 2024-03-15 | 北京百度网讯科技有限公司 | Application monitoring method, device, equipment and storage medium |
-
2020
- 2020-11-23 CN CN202011324525.2A patent/CN112532478B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109921927A (en) * | 2019-02-20 | 2019-06-21 | 苏州人之众信息技术有限公司 | Real-time calling D-chain trace method based on micro services |
| CN110262889A (en) * | 2019-06-27 | 2019-09-20 | 深圳前海微众银行股份有限公司 | A kind of link tracing method and device |
| CN110442641A (en) * | 2019-08-06 | 2019-11-12 | 中国工商银行股份有限公司 | A kind of link topology figure methods of exhibiting, device, storage medium and equipment |
| CN110717132A (en) * | 2019-09-05 | 2020-01-21 | 深圳平安通信科技有限公司 | Data collection method and pushing method for full-link monitoring system and related equipment |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112532478A (en) | 2021-03-19 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111083225A (en) | Data processing method and device in Internet of things platform and Internet of things platform | |
| CN108255545B (en) | Function calling method and device between components and modular architecture system | |
| US20170187782A1 (en) | Telemetry response system | |
| US11386061B2 (en) | Telemetry request system | |
| CN109582655B (en) | Method and device for positioning system log and computer readable storage medium | |
| CN111782530B (en) | Remote debugging method, device, system, electronic equipment and storage medium | |
| CN111858375A (en) | Software testing method, device, electronic equipment and medium | |
| CN113076253A (en) | Test method and test device | |
| CN108121633A (en) | Exception catching method and device | |
| CN115934471A (en) | Big data based data acquisition method and big data system | |
| CN113553260B (en) | Test method, test apparatus, device, and medium | |
| CN115391228A (en) | Precise test method, device, equipment and medium | |
| CN111538602A (en) | Message forwarding method and device for message queue | |
| CN114579194A (en) | Spring remote call-based exception handling method and system | |
| CN114239026A (en) | Information desensitization conversion processing method, device, computer equipment and storage medium | |
| CN104142882B (en) | Test method and device, system based on data processing | |
| CN112532478B (en) | Link relation tracking method, system, checking method, device and equipment | |
| CN110995756A (en) | Method and device for calling service | |
| CN112380105A (en) | Log collection method, device, system, equipment, storage medium and plug-in | |
| CN110022332B (en) | Hypertext transfer security protocol proxy method, device, equipment and medium | |
| CN111049795B (en) | Method and device for detecting sensitive data unencrypted vulnerability of distributed Web application | |
| CN116932367A (en) | Code coverage rate generation method and device, storage medium and electronic equipment | |
| CN111147445B (en) | Packet capturing method, device, system and storage medium | |
| CN114020513A (en) | Method and device for processing log information | |
| CN112632534A (en) | Malicious behavior detection method and device |
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 |