Call link identification method and related equipment

Abstract

The present application provides a call link identification method and related equipment, the method comprising: obtaining a pre-built link identification plug-in, wherein the link identification plug-in is a plug-in built according to the driver of the isolation device; using the link identification plug-in to identify the call request of the internal database to obtain an identification result; and constructing a call link corresponding to the call request according to the identification result. The present application pre-builds a link identification plug-in according to the driver of the isolation device, and uses the link identification plug-in to identify the call request. Through the adaptability improvement of the link identification plug-in for the isolation device, the link tracking system's call link identification function for the isolation device is compensated, and the integrity of the call link is increased. Through the call link identification result of the isolation device, the status monitoring of the isolation device is realized, and the link tracking system's perception of the isolation device is improved.

Description

Technical Field

[0001] The present application relates to the field of data processing technology, and in particular to a call link identification method and related equipment. Background Art

[0002] In order to ensure the security and reliability of the company's data, the company's network is mainly divided into two types: intranet and extranet. The internal and external networks communicate data through isolation devices. The function of the isolation device is to process and convert the data to be transmitted according to internal algorithms and store it in the intranet database.

[0003] Usually, APM (Application Performance Management) built on open source software can be redeveloped according to personalized scenario requirements to realize the company's distributed link tracking function. Through link tracking, APM can automatically detect the call link of the internal database, but the isolation device is a company-specific network device, and APM cannot detect the isolation device, which leads to incomplete call links. Summary of the invention

[0004] In view of this, the purpose of this application is to propose a calling link identification method and related equipment to solve or partially solve the above technical problems.

[0005] Based on the above purpose, the first aspect of the present application provides a call link identification method, which is applied to a link tracking system, and the system is connected to an isolation device and an internal database respectively; the method includes:

[0006] Acquire a pre-built link identification plug-in, wherein the link identification plug-in is a plug-in built according to a driver of the isolation device;

[0007] Using the link identification plug-in to identify the call request of the internal database to obtain an identification result;

[0008] A call link corresponding to the call request is constructed according to the recognition result.

[0009] A second aspect of the present application provides a call link identification device, including:

[0010] An acquisition module is configured to acquire a pre-built link identification plug-in, wherein the link identification plug-in is a plug-in built according to a driver of the isolation device;

[0011] An identification module, configured to use the link identification plug-in to identify the call request of the internal database and obtain an identification result;

[0012] A construction module is configured to construct a call link corresponding to the call request according to the recognition result.

[0013] A third aspect of the present application provides an electronic device, comprising a memory, a processor, and a computer program stored in the memory and executable by the processor, wherein the processor implements the method described in the first aspect when executing the computer program.

[0014] A fourth aspect of the present application provides a non-transitory computer-readable storage medium, wherein the non-transitory computer-readable storage medium stores computer instructions, wherein the computer instructions are used to cause a computer to execute the method described in the first aspect.

[0015] From the above, it can be seen that the present application provides a call link identification method and related equipment, which pre-builds a link identification plug-in according to the driver of the isolation device, and uses the link identification plug-in to identify the call request. Through the adaptability improvement of the link identification plug-in for the isolation device, the link tracking system's call link identification function for the isolation device is compensated, and the integrity of the call link is increased. Through the call link identification results of the isolation device, the status of the isolation device is monitored, and the link tracking system's perception of the isolation device is improved. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] In order to more clearly illustrate the technical solutions in the present application or related technologies, the drawings required for use in the embodiments or related technical descriptions are briefly introduced below. Obviously, the drawings described below are only embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.

[0017] Figure 1a A schematic diagram of the structure of a link tracking system according to an embodiment of the present application;

[0018] Figure 1b A flowchart of a link identification method according to an embodiment of the present application;

[0019] Figure 1c A schematic diagram of the construction process of the link identification plug-in according to an embodiment of the present application;

[0020] Figure 2 A schematic diagram of the structure of a call link identification device according to an embodiment of the present application;

[0021] Figure 3 A schematic diagram of the structure of an electronic device according to an embodiment of the present application. DETAILED DESCRIPTION

[0022] In order to make the objectives, technical solutions and advantages of the present application more clearly understood, the present application is further described in detail below in combination with specific embodiments and with reference to the accompanying drawings.

[0023] It should be noted that, unless otherwise defined, the technical terms or scientific terms used in the embodiments of the present application should be the usual meanings understood by people with ordinary skills in the field to which the present application belongs. The "first", "second" and similar words used in the embodiments of the present application do not represent any order, quantity or importance, but are only used to distinguish different components. "Including" or "comprising" and similar words mean that the elements or objects appearing in front of the word cover the elements or objects listed after the word and their equivalents, without excluding other elements or objects. "Connect" or "connected" and similar words are not limited to physical or mechanical connections, but can include electrical connections, whether direct or indirect. "Up", "down", "left", "right" and the like are only used to indicate relative positional relationships. When the absolute position of the described object changes, the relative positional relationship may also change accordingly.

[0024] As described in the background technology, Figure 1a As shown, the link tracking system 110 is connected to the isolation device 120 and the internal database 130 respectively. The link tracking system 110 can be a computer system that controls the isolation device 120 and the internal database 130. The link tracking system 110 completes the call link identification by exchanging data between the isolation device 120 and the internal database 130. The isolation device 120 can be a computer system that isolates the internal database 130 and the external Internet ( Figure 1a The device (not shown) is configured in such a way that all the company's databases are arranged in the intranet, and all application systems that need to provide Internet access are placed in the extranet. The isolation device implements protection against attacks on the internal database by the external system through parsing and controlling the database protocol. When the data in the internal database 130 is called by the isolation device 120, the link tracking system 110 can obtain the call request through the connection with the internal database 130, and the link tracking system 110 can obtain the call status of the driver in the isolation device 120 through the connection with the isolation device 120. Specifically, the process of the external network accessing the intranet database 130 can be equivalent to the external network driving through the isolation device to directly read and write data to the intranet database, thereby realizing the purpose of interconnecting the internal and external networks.

[0025] This brings about the following problems: when the link tracking system 110 obtains the call link through a call request, due to the existence of the isolation device 120, it is difficult to penetrate the isolation device 120 to obtain the complete call link.

[0026] Therefore, it is necessary to provide a call link identification method, which can penetrate the isolation device and perform link identification on the call request of the isolation device 120.

[0027] It can be understood that the method of the embodiment of the present application is explained by taking the isolation system of data interaction as an example, and the method of the embodiment of the present application can also be applied to the isolation system of unidirectional data transmission.

[0028] like Figure 1b As shown, the method of this embodiment includes:

[0029] Step 101: Obtain a pre-built link identification plug-in, wherein the link identification plug-in is a plug-in built according to a driver of the isolation device.

[0030] In this step, the link identification plug-in refers to a plug-in built according to the driver of the isolation device. The preferred link identification plug-in in this embodiment can be a distributed link tracking plug-in built according to the driver of the isolation device. In this way, a plug-in foundation is provided for subsequent call requests to perform identification.

[0031] Step 102: Use the link identification plug-in to identify the call request of the internal database to obtain an identification result.

[0032] In this step, the call request refers to the start of the execution process of a transaction, request or flow. The preferred call request of this embodiment can be the start of the execution process of a transaction, request or flow in the internal database. For example, the call request can be a request for microservice A to call microservice B, or a request for microservice B to query the Mysql (an open source database service) database in the internal database, or a request for microservice B to query the Oracle (an open source database service) database in the internal database, or a request for microservice B to call the middleware, wherein the middleware includes kafka (an open source stream processing platform), ES (a distributed storage component), and Redis (an open source remote dictionary service). In this way, a link identification plug-in is pre-built according to the driver of the isolation device, and the link identification plug-in is used to identify the call request. Through the adaptability improvement of the link identification plug-in for the isolation device, the link tracking system makes up for the call link identification function of the isolation device, and increases the integrity of the call link.

[0033] Step 103: construct a call link corresponding to the call request according to the recognition result.

[0034] In this step, the call link refers to the execution process of a transaction, request or process. The preferred call request in this embodiment can be the execution process of a transaction, request or process in the internal database. For example, the call link can be the process of microservice A calling microservice B, and the call request can also be the process of microservice B querying the Mysql database in the internal database, and the call request can also be the process of microservice B querying the Oracle database in the internal database, and the call request can also be the process of microservice B calling the middleware. In this way, through the call link identification result of the isolation device, the status monitoring of the isolation device is realized, and the perception ability of the link tracking system to the isolation device is improved.

[0035] Through the above scheme, a link identification plug-in is pre-built according to the driver of the isolation device, and the link identification plug-in is used to identify the call request. Through the adaptability improvement of the link identification plug-in for the isolation device, the link tracking system makes up for the call link identification function of the isolation device, and increases the integrity of the call link. Through the call link identification result of the isolation device, the status monitoring of the isolation device is realized, and the perception ability of the link tracking system to the isolation device is improved.

[0036] In some embodiments, Figure 1c As shown, the construction process of the link identification plug-in in step 101 includes:

[0037] Step 1011, obtaining a driver identifier corresponding to a driver of the isolation device, and constructing a first link identification plug-in according to the driver identifier;

[0038] Step 1012, obtaining the microservice of the internal database, and constructing a second link identification plug-in according to the microservice;

[0039] Step 1013: Use the first link identification plug-in and the second link identification plug-in as the link identification plug-in.

[0040] In the above scheme, the driver identifier refers to an identifier that can obtain the driver. The preferred driver identifier in this embodiment may be an identifier that can obtain the driver of the isolation device. For example, the driver name of the isolation device may be used as the identifier. The first link identification plug-in refers to a link identification plug-in that can identify the driver of the isolation device. The preferred first link identification plug-in in this embodiment may be a link identification plug-in built based on the driver of the isolation device. The second link identification plug-in refers to a link identification plug-in that can identify the microservice. The preferred second link identification plug-in in this embodiment may be a link identification plug-in built based on the microservice of the internal database.

[0041] Through the above solution, a plug-in foundation is provided for subsequent call requests to be identified

[0042] In some embodiments, step 1011 specifically includes:

[0043] Obtaining a drive identifier corresponding to a drive of the isolation device;

[0044] Collecting service information of the driver identifier to obtain an isolation link element;

[0045] The first link identification plug-in is constructed according to the isolated link element.

[0046] In the above scheme, the isolation link element refers to a logical unit with a start time and an execution duration, wherein the logical unit can reflect the reference relationship of the isolation link element. The preferred isolation link element in this embodiment may be a logical unit driven by a calling isolation device with a start time and an execution duration. For example, the isolation link element may include an operation name: a driver identifier of the isolation device, a start time; 2021-1-25 22:00:00 and an end time; 2021-1-30 22:00:00, and a reference relationship: called by microservice C.

[0047] Specifically, the process of constructing the first link identification plug-in according to the isolated link element at least includes:

[0048] Obtain an interceptor, wherein the interceptor is a function for extracting link elements in a call link;

[0049] Constructing a monitoring function according to the isolation link element, wherein the monitoring function is a function for monitoring a corresponding call request of the isolation device according to the drive identifier;

[0050] The monitoring function is injected into the interceptor to obtain the first link identification plug-in.

[0051] In this way, the identification process of the call request by the first link identification plug-in at least includes: using an interceptor to extract the link elements in the call link corresponding to the call request, screening the link elements corresponding to the isolation device driver identifier through a monitoring function, and obtaining the first link element.

[0052] The above solution provides a plug-in foundation for the construction of subsequent call links.

[0053] In some embodiments, step 102 specifically includes:

[0054] Get the link probe plugin;

[0055] Obtaining a call request for the internal database through the link probe plug-in;

[0056] Using the first link identification plug-in to identify the call request, and obtaining a first identification result corresponding to the driver identifier;

[0057] Using the second link identification plug-in to identify the call request, and obtain a second identification result corresponding to the microservice;

[0058] The first recognition result and the second recognition result are used as the recognition result.

[0059] In the above scheme, the link probe plug-in refers to a plug-in that can obtain a call request. The preferred link probe plug-in of this embodiment can be a plug-in that can obtain a call request of an internal database. For example, a Java language agent (probe) plug-in can be used to complete the acquisition of the call request. The first identification result refers to the call link corresponding to the driver of the isolation device, and the second identification result refers to the call link corresponding to the microservice in the internal database.

[0060] Through the above scheme, a link identification plug-in built according to the isolation device driver is used to identify the call request. Through the adaptability improvement of the link identification plug-in for the isolation device, the link tracking system's call link identification function for the isolation device is compensated, and the integrity of the call link is increased.

[0061] In some embodiments, the using the first link identification plug-in to identify the call request to obtain a first identification result corresponding to the driver identifier includes:

[0062] Using the first link identification plug-in to identify the call request according to the isolated link element, and obtain a first link element corresponding to the isolated link element;

[0063] The first link element is used as the first identification result.

[0064] In the above scheme, the first link identification plug-in obtains all the call services corresponding to the call request, wherein the call service is an adjacent service constituting the call link; the first link identification plug-in screens the above call services according to the isolation link element, and determines that the call service includes the driver of the isolation device; the first link identification plug-in obtains the link element corresponding to the driver, and obtains the first link element. For example, if the call request is microservice A calling the driver of the isolation device through microservice B, then microservice A, microservice B and the driver of the isolation device are the call services corresponding to the call request, and the first link identification plug-in determines that the above call service includes the driver of the isolation device, and obtains the link element corresponding to the driver as the first link element.

[0065] Through the above solution, the link elements corresponding to the driver of the isolation device are obtained, providing a data basis for the construction of subsequent call links.

[0066] In some embodiments, the using the second link identification plug-in to identify the call request to obtain a second identification result corresponding to the microservice includes:

[0067] Using the second link identification plug-in to identify the call request according to the microservice, and obtain a second link element corresponding to the microservice;

[0068] The second link element is used as the second identification result.

[0069] In the above scheme, the second link identification plug-in obtains all the call services corresponding to the call request, where the call service is an adjacent service that constitutes the call link; the second link identification plug-in screens the above call services according to the microservices, and determines that the call service includes the microservices in the internal database; the second link identification plug-in obtains the link element corresponding to the microservice to obtain the second link element. For example, the call request is that microservice A calls microservice C that queries the database through microservice B, then microservice A, microservice B and microservice C are the call services corresponding to the call request, the second link identification plug-in determines that the above call service includes microservice C in the internal database, and obtains the link element corresponding to microservice C as the second link element.

[0070] Through the above solution, the link elements corresponding to the microservice are obtained, providing a data basis for the construction of subsequent call links.

[0071] In some embodiments, step 103 specifically includes:

[0072] The first recognition result and the second recognition result are combined to obtain the call link.

[0073] In the above solution, the link element in the first recognition result is merged with the link element in the second recognition result, and the merged result is used as the call link.

[0074] Through the above scheme, the status monitoring of the isolation device is realized through the call link identification result of the isolation device, and the link tracking system's perception ability of the isolation device is improved.

[0075] It should be noted that the method of the embodiment of the present application can be performed by a single device, such as a computer or server. The method of this embodiment can also be applied to a distributed scenario and completed by multiple devices cooperating with each other. In the case of such a distributed scenario, one of the multiple devices can only perform one or more steps in the method of the embodiment of the present application, and the multiple devices will interact with each other to complete the described method.

[0076] It should be noted that the above describes some embodiments of the present application. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recorded in the claims can be performed in an order different from that in the above embodiments and still achieve the desired results. In addition, the processes depicted in the accompanying drawings do not necessarily require the specific order or continuous order shown to achieve the desired results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0077] Based on the same inventive concept, corresponding to any of the above-mentioned embodiment methods, the present application also provides a calling link identification device.

[0078] refer to Figure 2 , the call link identification device comprises:

[0079] The acquisition module 201 is configured to acquire a pre-built link identification plug-in, wherein the link identification plug-in is a plug-in built according to the driver of the isolation device;

[0080] The identification module 202 is configured to use the link identification plug-in to identify the call request of the internal database and obtain an identification result;

[0081] The construction module 203 is configured to construct a call link corresponding to the call request according to the recognition result.

[0082] In some embodiments, the acquisition module 201 includes:

[0083] A driving unit, configured to obtain a driving identifier corresponding to a driving of the isolation device, and construct a first link identification plug-in according to the driving identifier;

[0084] A microservice unit, configured to obtain a microservice of the internal database and construct a second link identification plug-in according to the microservice;

[0085] The plug-in merging unit is configured to use the first link identification plug-in and the second link identification plug-in as the link identification plug-in.

[0086] In some embodiments, the drive unit is specifically configured as:

[0087] Obtaining a drive identifier corresponding to a drive of the isolation device;

[0088] Collecting service information of the driver identifier to obtain an isolation link element;

[0089] The first link identification plug-in is constructed according to the isolated link element.

[0090] In some embodiments, the identification module 202 specifically includes:

[0091] A probe unit configured to obtain a link probe plug-in;

[0092] A request acquisition unit, configured to acquire a call request of the internal database through the link probe plug-in;

[0093] A first identification unit is configured to use the first link identification plug-in to identify the call request and obtain a first identification result corresponding to the drive identifier;

[0094] A second identification unit is configured to use the second link identification plug-in to identify the call request and obtain a second identification result corresponding to the microservice;

[0095] A result merging unit is configured to use the first recognition result and the second recognition result as the recognition result.

[0096] In some embodiments, the first identification unit is configured to:

[0097] Using the first link identification plug-in to identify the call request according to the isolated link element, and obtain a first link element corresponding to the isolated link element;

[0098] The first link element is used as the first identification result.

[0099] In some embodiments, the second identification unit is configured to:

[0100] Using the second link identification plug-in to identify the call request according to the microservice, and obtain a second link element corresponding to the microservice;

[0101] The second link element is used as the second identification result.

[0102] In some embodiments, the construction module 203 is specifically configured to: merge the first recognition result and the second recognition result to obtain the call link.

[0103] For the convenience of description, the above device is described in terms of functions divided into various modules. Of course, when implementing the present application, the functions of each module can be implemented in the same or multiple software and / or hardware.

[0104] The device of the above embodiment is used to implement the corresponding calling link identification method in any of the above embodiments, and has the beneficial effects of the corresponding method embodiment, which will not be repeated here.

[0105] Based on the same inventive concept, corresponding to any of the above-mentioned embodiments and methods, the present application also provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the program, the calling link identification method described in any of the above embodiments is implemented.

[0106] Figure 3 A more specific schematic diagram of the hardware structure of an electronic device provided in this embodiment is shown, and the device may include: a processor 1010, a memory 1020, an input / output interface 1030, a communication interface 1040, and a bus 1050. The processor 1010, the memory 1020, the input / output interface 1030, and the communication interface 1040 are connected to each other through the bus 1050 in the device.

[0107] The processor 1010 can be implemented by a general-purpose CPU (Central Processing Unit), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits, and is used to execute relevant programs to implement the technical solutions provided in the embodiments of this specification.

[0108] The memory 1020 may be implemented in the form of ROM (Read Only Memory), RAM (Random Access Memory), static storage device, dynamic storage device, etc. The memory 1020 may store an operating system and other application programs. When the technical solutions provided in the embodiments of this specification are implemented by software or firmware, the relevant program codes are stored in the memory 1020 and are called and executed by the processor 1010.

[0109] The input / output interface 1030 is used to connect the input / output module to realize information input and output. The input / output module can be configured in the device as a component (not shown in the figure), or it can be externally connected to the device to provide corresponding functions. The input device may include a keyboard, a mouse, a touch screen, a microphone, various sensors, etc., and the output device may include a display, a speaker, a vibrator, an indicator light, etc.

[0110] The communication interface 1040 is used to connect a communication module (not shown) to realize communication interaction between the device and other devices. The communication module can realize communication through a wired mode (such as USB, network cable, etc.) or a wireless mode (such as mobile network, WIFI, Bluetooth, etc.).

[0111] The bus 1050 includes a path that transmits information between the various components of the device (eg, the processor 1010, the memory 1020, the input / output interface 1030, and the communication interface 1040).

[0112] It should be noted that, although the above device only shows the processor 1010, the memory 1020, the input / output interface 1030, the communication interface 1040 and the bus 1050, in the specific implementation process, the device may also include other components necessary for normal operation. In addition, it can be understood by those skilled in the art that the above device may also only include the components necessary for implementing the embodiments of the present specification, and does not necessarily include all the components shown in the figure.

[0113] The electronic device of the above embodiment is used to implement the corresponding calling link identification method in any of the above embodiments, and has the beneficial effects of the corresponding method embodiment, which will not be described in detail here.

[0114] Based on the same inventive concept, corresponding to any of the above-mentioned embodiment methods, the present application also provides a non-transitory computer-readable storage medium, wherein the non-transitory computer-readable storage medium stores computer instructions, and the computer instructions are used to enable the computer to execute the call link identification method described in any of the above embodiments.

[0115] The computer-readable medium of this embodiment includes permanent and non-permanent, removable and non-removable media, and information storage can be implemented by any method or technology. Information can be computer-readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, read-only compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device.

[0116] The computer instructions stored in the storage medium of the above embodiment are used to enable the computer to execute the call link identification method described in any of the above embodiments, and have the beneficial effects of the corresponding method embodiments, which will not be repeated here.

[0117] Those skilled in the art should understand that the discussion of any of the above embodiments is merely illustrative and is not intended to imply that the scope of the present application (including the claims) is limited to these examples. In line with the concept of the present application, the technical features in the above embodiments or different embodiments may be combined, the steps may be implemented in any order, and there are many other variations of the different aspects of the embodiments of the present application as described above, which are not provided in detail for the sake of simplicity.

[0118] In addition, to simplify the description and discussion, and in order not to make the embodiments of the present application difficult to understand, the known power supply / ground connection with the integrated circuit (IC) chip and other components may or may not be shown in the provided drawings. In addition, the device can be shown in the form of a block diagram to avoid making the embodiments of the present application difficult to understand, and this also takes into account the fact that the details of the implementation of these block diagram devices are highly dependent on the platform to be implemented in the embodiments of the present application (that is, these details should be fully within the scope of understanding of those skilled in the art). In the case of elaborating specific details (e.g., circuits) to describe exemplary embodiments of the present application, it is obvious to those skilled in the art that the embodiments of the present application can be implemented without these specific details or when these specific details are changed. Therefore, these descriptions should be considered to be illustrative rather than restrictive.

[0119] Although the present application has been described in conjunction with specific embodiments of the present application, many replacements, modifications and variations of these embodiments will be apparent to those skilled in the art from the foregoing description. For example, other memory architectures (e.g., dynamic RAM (DRAM)) may use the embodiments discussed.

[0120] The embodiments of the present application are intended to cover all such substitutions, modifications and variations that fall within the broad scope of the appended claims. Therefore, any omissions, modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the embodiments of the present application should be included in the scope of protection of the present application.

Claims

1. A call link identification method, characterized in that: The method is applied to a link tracking system, wherein the system is connected to an isolation device and an internal database respectively; the method comprises: Acquire a pre-built link identification plug-in, wherein the link identification plug-in is a plug-in built according to a driver of the isolation device; Using the link identification plug-in to identify the call request of the internal database to obtain an identification result; Constructing a call link corresponding to the call request according to the recognition result; The link identification plug-in construction process includes: Obtaining a driver identifier corresponding to a driver of the isolation device, and constructing a first link identification plug-in according to the driver identifier; Acquire the microservice of the internal database, and construct a second link identification plug-in according to the microservice; Using the first link identification plug-in and the second link identification plug-in as the link identification plug-in; The step of using the link identification plug-in to identify the call request of the internal database to obtain an identification result includes: Get the link probe plugin; Obtaining a call request for the internal database through the link probe plug-in; Using the first link identification plug-in to identify the call request, and obtaining a first identification result corresponding to the driver identifier; Using the second link identification plug-in to identify the call request, and obtain a second identification result corresponding to the microservice; The first recognition result and the second recognition result are used as the recognition result.

2. The method according to claim 1, characterized in that The step of obtaining a driver identifier corresponding to a driver of the isolation device and constructing a first link identification plug-in according to the driver identifier includes: Obtaining a drive identifier corresponding to a drive of the isolation device; Collecting service information of the driver identifier to obtain an isolation link element; The first link identification plug-in is constructed according to the isolated link element.

3. The method according to claim 2, characterized in that The using the first link identification plug-in to identify the call request to obtain a first identification result corresponding to the driver identifier includes: Using the first link identification plug-in to identify the call request according to the isolated link element, and obtain a first link element corresponding to the isolated link element; The first link element is used as the first identification result.

4. The method according to claim 1, characterized in that: The using the second link identification plug-in to identify the call request to obtain a second identification result corresponding to the microservice includes: Using the second link identification plug-in to identify the call request according to the microservice, and obtain a second link element corresponding to the microservice; The second link element is used as the second identification result.

5. The method according to any one of claims 1 to 4, characterized in that: The constructing a call link corresponding to the call request according to the recognition result includes: The first recognition result and the second recognition result are combined to obtain the call link.

6. A call link identification device, characterized in that: The device is applied to a link tracking system, and the system is connected to an isolation device and an internal database respectively; the device comprises: An acquisition module is configured to acquire a pre-built link identification plug-in, wherein the link identification plug-in is a plug-in built according to a driver of the isolation device; An identification module, configured to use the link identification plug-in to identify the call request of the internal database and obtain an identification result; A construction module, configured to construct a call link corresponding to the call request according to the recognition result; The link identification plug-in construction process includes: Obtaining a driver identifier corresponding to a driver of the isolation device, and constructing a first link identification plug-in according to the driver identifier; Acquire the microservice of the internal database, and construct a second link identification plug-in according to the microservice; Wherein, the identification module is further configured as follows: Get the link probe plugin; Obtaining a call request for the internal database through the link probe plug-in; Using the first link identification plug-in to identify the call request, and obtaining a first identification result corresponding to the driver identifier; Using the second link identification plug-in to identify the call request, and obtain a second identification result corresponding to the microservice; The first recognition result and the second recognition result are used as the recognition result.

7. An electronic device, characterized in that: The method comprises a memory, a processor, and a computer program stored in the memory and executable by the processor, wherein the processor implements the method according to any one of claims 1 to 5 when executing the computer program.

8. A non-transitory computer-readable storage medium, characterized in that: The non-transitory computer-readable storage medium stores computer instructions, and the computer instructions are used to cause a computer to execute the method according to any one of claims 1 to 5.

Images