WO2021189899A1 - 链路状态的追踪方法、装置、电子设备及计算机存储介质 - Google Patents
链路状态的追踪方法、装置、电子设备及计算机存储介质 Download PDFInfo
- Publication number
- WO2021189899A1 WO2021189899A1 PCT/CN2020/131976 CN2020131976W WO2021189899A1 WO 2021189899 A1 WO2021189899 A1 WO 2021189899A1 CN 2020131976 W CN2020131976 W CN 2020131976W WO 2021189899 A1 WO2021189899 A1 WO 2021189899A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- link
- tracking
- user
- node
- target link
- Prior art date
Links
Images
Classifications
-
- 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/083—Network architectures or network communication protocols for network security for authentication of entities using passwords
-
- 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/04—Network management architectures or arrangements
- H04L41/044—Network management architectures or arrangements comprising hierarchical management structures
-
- 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/08—Configuration management of networks or network elements
- H04L41/085—Retrieval of network configuration; Tracking network configuration history
-
- 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/08—Configuration management of networks or network elements
- H04L41/0876—Aspects of the degree of configuration automation
-
- 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/0876—Network architectures or network communication protocols for network security for authentication of entities based on the identity of the terminal or configuration, e.g. MAC address, hardware or software configuration or device fingerprint
-
- 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
-
- 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/04—Protocols specially adapted for terminals or networks with limited capabilities; specially adapted for terminal portability
-
- 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/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1097—Protocols in which an application is distributed across nodes in the network for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
-
- 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/2866—Architectures; Arrangements
- H04L67/30—Profiles
Definitions
- This application relates to the field of data processing technology, and in particular to a method, device, electronic device, and computer-readable storage medium for tracking link status.
- the commonly used technical method is to configure the IP of the node and the ID of the link to which the node belongs in advance on each node of the link in different distributed systems according to the attributes of the distributed system itself, for example, based on the function of the link. To name the ID of the link, and to name the IP of the node based on the function of the node. This method needs to ensure in advance the consistency of the ID configuration of the link on each node in the same link and the uniformity of the IP configuration of the nodes on all nodes in the same link, so that the node status of the link in the distributed system can be viewed. .
- the inventor realizes that since the IP of the node and the ID of the link to which the node belongs are pre-configured according to the attributes of the distributed system itself, if the node status of the link is viewed in different distributed systems, it needs to be based on different distributions. In this type of system, the IP of the node and the ID of the link to which the node belongs are reconfigured, resulting in low portability of the link tracking method. Therefore, how to implement dynamic automatic link node state tracking for different distributed systems and improve the portability of the link tracking method has become an urgent problem to be solved.
- a method for tracking link status including:
- Target link information in the link log, where the target link information includes multiple nodes in the target link and the hierarchical relationship between each node;
- the link tracking statement is executed to obtain the status of the node in the target link that has been marked with the link tracking ID.
- a tracking device for link status comprising:
- the link log acquisition module is used to acquire the link log in the distributed system
- a target link information extraction module configured to extract target link information in the link log, where the target link information includes multiple nodes in the target link and the hierarchical relationship between each node;
- a tracking ID generating module configured to generate a tracking ID of the target link, and mark multiple nodes in the target link as the target link tracking ID;
- a node IP identification acquiring module configured to acquire the node IP identification of each node in the target link, and combine the node IP identifications of adjacent nodes in the target link into a hierarchical IP;
- the link tracking sentence generation module is used to obtain a target link tracking request, using the level IP as the request header of the target link tracking request, and using the link tracking ID as the request body of the link tracking request to obtain Link tracking statement;
- the link state tracking module is configured to execute the link tracking sentence to obtain the state of the node in the target link that has the link tracking ID marked.
- an electronic device which includes:
- Memory storing at least one instruction
- the processor executes the instructions stored in the memory to implement the following steps:
- Target link information in the link log, where the target link information includes multiple nodes in the target link and the hierarchical relationship between each node;
- the link tracking statement is executed to obtain the status of the node in the target link that has been marked with the link tracking ID.
- a computer-readable storage medium includes a storage data area and a storage program area, the storage data area stores created data, and the storage program area stores a computer program; wherein the computer program is executed by a processor to implement the following steps:
- Target link information in the link log, where the target link information includes multiple nodes in the target link and the hierarchical relationship between each node;
- the link tracking statement is executed to obtain the status of the node in the target link that has been marked with the link tracking ID.
- This application can track the status of link nodes in a distributed system, and improve the portability of the link tracking method.
- FIG. 1 is a schematic flowchart of a method for tracking link status provided by an embodiment of this application
- FIG. 2 is a schematic diagram of modules of a link state tracking device provided by an embodiment of this application.
- FIG. 3 is a schematic diagram of the internal structure of an electronic device that implements a method for tracking link status provided by an embodiment of the application;
- the execution subject of the link state tracking method provided in the embodiments of the present application includes, but is not limited to, at least one of the electronic devices that can be configured to execute the method provided in the embodiments of the present application, such as a server and a terminal.
- the link state tracking method may be executed by software or hardware installed on the terminal device or the server device, and the software may be a blockchain platform.
- the server includes but is not limited to: a single server, a server cluster, a cloud server or a cloud server cluster, etc.
- This application provides a method for tracking link status.
- FIG. 1 it is a schematic flowchart of a method for tracking link status provided by an embodiment of this application.
- the method can be executed by a device, and the device can be implemented by software and/or hardware.
- the link state tracking method includes:
- the link log is a log generated when the distributed system performs an operation. For example, when a distributed system performs a service invocation operation, multiple background services in the distributed system need to jointly complete the service invocation operation, and multiple background services together form a link, and each background service is in the process of executing the service invocation operation.
- the data generated is the link log.
- the obtaining the link log in the distributed system includes:
- the distributed system contains multiple background services.
- each background service will generate a link log.
- the link log generation event that appears in the background service A is monitored, it is based on the monitoring Search the generated link log in the background service A for the link log generation event, and search the generated link log in the background service B and the background service C according to the monitored link log generation event.
- the integrity of the link log is improved by searching for the link log in all the background services required to complete the service invocation operation.
- the method further includes:
- the user information includes the user's unique identifier and the user's password.
- the user's identity can be uniquely determined based on the user information, and then whether the user is an authorized user is determined. If the user is an authorized user, based on the monitored link
- the log generation event finds the generated link log.
- the embodiment of the present application can improve the security of link state tracking in the distributed system by verifying the user's identity.
- the determining whether the user is an authorized user according to the unique identifier of the user and the password of the user includes:
- the unique identifier of the user and the password of the user match the pre-stored information, it is determined that the user is an authorized user.
- the extracting target link information in the link log includes:
- the calculating the difference value between the predicted target link information and the standard target link information includes:
- the following difference value algorithm is used to calculate the difference value between the predicted target link information and the standard target link information
- I the predicted target link information
- Y is the standard target link information
- ⁇ is a preset constant
- N is the number of predicted target link information.
- the embodiment of the present application adjusts the parameters of the information extraction model through a gradient descent algorithm.
- the gradient descent algorithm includes but is not limited to: a batch gradient descent algorithm, a stochastic gradient descent algorithm, and a small batch gradient descent algorithm.
- the generating the tracking ID of the target link includes:
- the code generation sentence is executed to generate an ID code, and the ID code is determined to be the link tracking ID of the target link.
- the unique encoding function includes, but is not limited to, a GUID function.
- the GUID function is a function that can generate a 128-bit binary number identifier. No computer or computer cluster can use the GUID function to generate two identical binary number identifiers.
- a compiler is used to compile GUID functions into code generation sentences, ID codes are generated by executing code generation sentences, and binary digital identifiers (ie ID codes) generated by GUID functions are used as the link tracking ID of the target link to ensure The uniqueness of the link tracking ID is conducive to accurately obtaining the final status of different links.
- multiple nodes in the target link are marked as the target link tracking ID. For example, there are node Q, node P, node M, and node Z in the target link.
- the target link tracking ID is 1xxxxx0
- the obtaining the node IP identifier of each node in the target link includes:
- IP address table Query in the IP address table according to the device information to obtain the IP address corresponding to the device information, and determine that the IP address is the node IP identifier of each node in the target link.
- the embodiment of the present application may use the python sentence of the sentence data capture function to obtain the device information of each node of the target link from the file used to store the system information of the distributed system.
- the IP address table is preset by the user, and the IP address table includes device information of at least one node and an IP address uniquely corresponding to the device information.
- the embodiment of the present application combines the node IP identifiers of adjacent nodes in the target link into a hierarchical IP, so as to use the hierarchical IP to mark the hierarchical relationship between the adjacent nodes in the target link.
- the node IP of node E is 123.456.7.8
- the node IP of node R is 321.654.8.7
- the node IP of node E and node R are combined as Hierarchical IP: 123.456.7.8-321.654.8.7, using hierarchical IP: 123.456.7.8-321.654.8.7 to mark the hierarchical relationship between neighboring node E and node R.
- the node IP identifiers of adjacent nodes in the target link are combined into a hierarchical IP
- the node IP identifiers can be combined according to the hierarchical relationship between adjacent nodes in the target link. For example, if the hierarchical relationship between adjacent node E and node R is that node E calls node R, then the node IP identifiers of node E and node R are combined into a hierarchical IP: 123.456.7.8-321.654.8.7; if the adjacent node The hierarchical relationship between E and node R is that node R calls node E, and the node IP identifiers of node E and node R are combined into a hierarchical IP: 321.654.8.7-123.456.7.8.
- the target link tracking request may be predetermined by the user.
- the target link tracking request includes a request header and a request body.
- the request header is used to store the level IP to track the status of the node in the target link
- the request body is used to store the link tracking ID, which is used to track distributed The status of the complete target link in the system.
- the target link tracking ID is 1xxxxx0; the level IP is 123.456.7.8-321.654.8.7; write 123.456.7.8-321.654.8.7 into the request header, and write 1xxxxx0 into the request body to get the link tracking sentence.
- the executing the link tracking sentence to obtain the status of the node in the target link that has the link tracking ID marked includes:
- the link tracking sentence is executed according to the tracking time rule to obtain the state of the node in the target link that has the link tracking ID marked in the target link.
- custom processing function includes but is not limited to one or more of the following:
- U_TIME function used to customize the tracking time
- the U_DIV function is used to detect the compilation environment of a distributed system.
- a custom processing function to construct a tracking time rule includes:
- the custom processing function is compiled by a compiler corresponding to the compilation environment to obtain the tracking time rule.
- multiple nodes in the target link and the hierarchical relationship between each node are obtained, and the tracking ID of the target link is generated, and the multiple nodes in the target link are marked as the target link tracking ID, Obtain the node IP identifier of each node in the target link, and combine the node IP identifiers of adjacent nodes in the target link into a hierarchical IP, which realizes the automatic marking of the nodes of the target link without the need for each link in the target link.
- the link state tracking method proposed in this application can track the state of link nodes in a distributed system and improve the portability of the link tracking method.
- FIG. 2 it is a schematic diagram of the module of the tracking device of the link state of the present application.
- the link state tracking device 100 described in this application can be installed in an electronic device.
- the link state tracking device may include a link log acquisition module 101, a target link information extraction module 102, a tracking ID generation module 103, a node IP identification acquisition module 104, and a link tracking sentence generation module 105 ⁇ Link status tracking module 106.
- the module described in this application can also be called a unit, which refers to a series of computer program segments that can be executed by the processor of an electronic device and can complete fixed functions, and are stored in the memory of the electronic device.
- each module/unit is as follows:
- the link log obtaining module 101 is configured to obtain link logs in a distributed system
- the target link information extraction module 102 is configured to extract target link information in the link log, where the target link information includes multiple nodes in the target link and the hierarchical relationship between the nodes;
- the tracking ID generating module 103 is configured to generate a tracking ID of the target link, and mark multiple nodes in the target link as the target link tracking ID;
- the node IP identification acquiring module 104 is configured to acquire the node IP identification of each node in the target link, and combine the node IP identifications of adjacent nodes in the target link into a hierarchical IP;
- the link tracking sentence generating module 105 is configured to obtain a target link tracking request, using the level IP as the request header of the target link tracking request, and using the link tracking ID as the request body of the link tracking request, Get the link tracking sentence;
- the link status tracking module 106 is configured to execute the link tracking statement to obtain the status of the node in the target link that has the link tracking ID marked.
- each module of the link state tracking device is as follows:
- the link log obtaining module 101 is used to obtain link logs in a distributed system.
- the link log is a log generated when the distributed system performs an operation. For example, when a distributed system performs a service invocation operation, multiple background services in the distributed system need to jointly complete the service invocation operation, and multiple background services together form a link, and each background service is in the process of executing the service invocation operation.
- the data generated is the link log.
- link log obtaining module 101 is specifically configured to:
- the distributed system contains multiple background services.
- each background service will generate a link log.
- the background service A, the background service B, and the background service C need to complete the service invocation operation together.
- the link log generation event that appears in the background service A is monitored, it is based on the monitoring Find the generated link log in the background service A for the link log generation event, and search the generated link log in the background service B and the background service C according to the monitored link log generation event.
- the integrity of the link log is improved by searching the link log in all the background services required to complete the service invocation operation.
- the link state tracking device further includes an identity verification module, and the identity verification module is specifically configured to:
- the user information includes the user's unique identifier and the user's password.
- the user's identity can be uniquely determined based on the user information, and then whether the user is an authorized user is determined. If the user is an authorized user, based on the monitored link
- the log generation event finds the generated link log.
- the embodiment of the present application can improve the security of link state tracking in the distributed system by verifying the user's identity.
- the determining whether the user is an authorized user according to the unique identifier of the user and the password of the user includes:
- the unique identifier of the user and the password of the user match the pre-stored information, it is determined that the user is an authorized user.
- the target link information extraction module 102 is configured to extract target link information in the link log, where the target link information includes multiple nodes in the target link and the hierarchical relationship between the nodes.
- the target link information extraction module 102 is specifically configured to:
- the calculating the difference value between the predicted target link information and the standard target link information includes:
- the following difference value algorithm is used to calculate the difference value between the predicted target link information and the standard target link information
- I the predicted target link information
- Y is the standard target link information
- ⁇ is a preset constant
- N is the number of predicted target link information.
- the embodiment of the present application adjusts the parameters of the information extraction model through a gradient descent algorithm.
- the gradient descent algorithm includes but is not limited to: a batch gradient descent algorithm, a stochastic gradient descent algorithm, and a small batch gradient descent algorithm.
- the tracking ID generating module 103 is configured to generate a tracking ID of the target link, and mark multiple nodes in the target link as the target link tracking ID.
- the tracking ID generation module 103 is specifically configured to:
- the unique encoding function includes, but is not limited to, a GUID function.
- the GUID function is a function that can generate a 128-bit binary number identifier. No computer or computer cluster can use the GUID function to generate two identical binary number identifiers.
- a compiler is used to compile GUID functions into code generation sentences, ID codes are generated by executing code generation sentences, and binary digital identifiers (ie ID codes) generated by GUID functions are used as the link tracking ID of the target link to ensure The uniqueness of the link tracking ID is conducive to accurately obtaining the final status of different links.
- multiple nodes in the target link are marked as the target link tracking ID. For example, there are node Q, node P, node M, and node Z in the target link.
- the target link tracking ID is 1xxxxx0
- the node IP identifier obtaining module 104 is configured to obtain the node IP identifier of each node in the target link, and combine the node IP identifiers of adjacent nodes in the target link into a hierarchical IP.
- the node IP identification obtaining module 104 is specifically configured to:
- IP address table Query in the IP address table according to the device information to obtain the IP address corresponding to the device information, and determine that the IP address is the node IP identifier of each node in the target link;
- the embodiment of the present application may use the python sentence of the sentence data capture function to obtain the device information of each node of the target link from the file used to store the system information of the distributed system.
- the IP address table is preset by the user, and the IP address table includes device information of at least one node and an IP address uniquely corresponding to the device information.
- the embodiment of the present application combines the node IP identifiers of adjacent nodes in the target link into a hierarchical IP, so as to use the hierarchical IP to mark the hierarchical relationship between the adjacent nodes in the target link.
- the node IP of node E is 123.456.7.8
- the node IP of node R is 321.654.8.7
- the node IP of node E and node R are combined as Hierarchical IP: 123.456.7.8-321.654.8.7, using hierarchical IP: 123.456.7.8-321.654.8.7 to mark the hierarchical relationship between neighboring node E and node R.
- the node IP identifiers of adjacent nodes in the target link are combined into a hierarchical IP
- the node IP identifiers can be combined according to the hierarchical relationship between adjacent nodes in the target link. For example, if the hierarchical relationship between adjacent node E and node R is that node E calls node R, then the node IP identifiers of node E and node R are combined into a hierarchical IP: 123.456.7.8-321.654.8.7; if the adjacent node The hierarchical relationship between E and node R is that node R calls node E, and the node IP identifiers of node E and node R are combined into a hierarchical IP: 321.654.8.7-123.456.7.8.
- the link tracking sentence generating module 105 is used to obtain a target link tracking request, using the level IP as the request header of the target link tracking request, and using the link tracking ID as the request body of the link tracking request, Get the link tracking statement.
- the target link tracking request may be predetermined by the user.
- the target link tracking request includes a request header and a request body.
- the request header is used to store the level IP to track the status of the node in the target link
- the request body is used to store the link tracking ID, which is used to track distributed The status of the complete target link in the system.
- the target link tracking ID is 1xxxxx0; the level IP is 123.456.7.8-321.654.8.7; write 123.456.7.8-321.654.8.7 into the request header, and write 1xxxxx0 into the request body to get the link tracking sentence.
- the link status tracking module 106 is configured to execute the link tracking statement to obtain the status of the node in the target link that has the link tracking ID marked.
- the link state tracking module 106 is specifically configured to:
- the link tracking sentence is executed according to the tracking time rule to obtain the state of the node in the target link that has the link tracking ID marked in the target link.
- custom processing function includes but is not limited to one or more of the following:
- U_TIME function used to customize the tracking time
- the U_DIV function is used to detect the compilation environment of a distributed system.
- a custom processing function to construct a tracking time rule includes:
- the custom processing function is compiled by a compiler corresponding to the compilation environment to obtain the tracking time rule.
- multiple nodes in the target link and the hierarchical relationship between each node are obtained, and the tracking ID of the target link is generated, and the multiple nodes in the target link are marked as the target link tracking ID, Obtain the node IP identifier of each node in the target link, and combine the node IP identifiers of adjacent nodes in the target link into a hierarchical IP, which realizes the automatic marking of the nodes of the target link without the need for each link in the target link.
- the link state tracking device proposed in this application can track the state of link nodes in a distributed system and improve the portability of the link tracking method.
- FIG. 3 it is a schematic diagram of the structure of the electronic device implementing the method for tracking the link state of the present application.
- the electronic device 1 may include a processor 10, a memory 11, and a bus, and may also include a computer program stored in the memory 11 and running on the processor 10, such as a link state tracking program 12.
- the memory 11 includes at least one type of readable storage medium, and the readable storage medium includes flash memory, mobile hard disk, multimedia card, card-type memory (such as SD or DX memory, etc.), magnetic memory, magnetic disk, CD etc.
- the memory 11 may be an internal storage unit of the electronic device 1 in some embodiments, for example, a mobile hard disk of the electronic device 1.
- the memory 11 may also be an external storage device of the electronic device 1, such as a plug-in mobile hard disk, a smart media card (SMC), and a secure digital (Secure Digital) equipped on the electronic device 1. , SD) card, flash card (Flash Card), etc.
- the memory 11 may also include both an internal storage unit of the electronic device 1 and an external storage device.
- the memory 11 can be used not only to store application software and various data installed in the electronic device 1, such as the code of the link state tracking program 12, etc., but also to temporarily store data that has been output or will be output.
- the processor 10 may be composed of integrated circuits in some embodiments, for example, may be composed of a single packaged integrated circuit, or may be composed of multiple integrated circuits with the same function or different functions, including one or more Combinations of central processing unit (CPU), microprocessor, digital processing chip, graphics processor, and various control chips, etc.
- the processor 10 is the control unit of the electronic device, which uses various interfaces and lines to connect the various components of the entire electronic device, and runs or executes programs or modules stored in the memory 11 (for example, executing Link status tracking program, etc.), and call data stored in the memory 11 to execute various functions of the electronic device 1 and process data.
- the bus may be a peripheral component interconnect standard (PCI) bus or an extended industry standard architecture (EISA) bus, etc.
- PCI peripheral component interconnect standard
- EISA extended industry standard architecture
- the bus can be divided into address bus, data bus, control bus and so on.
- the bus is configured to implement connection and communication between the memory 11 and at least one processor 10 and the like.
- FIG. 3 only shows an electronic device with components. Those skilled in the art can understand that the structure shown in FIG. 3 does not constitute a limitation on the electronic device 1, and may include fewer or more components than shown in the figure. Components, or a combination of certain components, or different component arrangements.
- the electronic device 1 may also include a power source (such as a battery) for supplying power to various components.
- the power source may be logically connected to the at least one processor 10 through a power management device, thereby controlling power
- the device implements functions such as charge management, discharge management, and power consumption management.
- the power supply may also include any components such as one or more DC or AC power supplies, recharging devices, power failure detection circuits, power converters or inverters, and power status indicators.
- the electronic device 1 may also include various sensors, Bluetooth modules, Wi-Fi modules, etc., which will not be repeated here.
- the electronic device 1 may also include a network interface.
- the network interface may include a wired interface and/or a wireless interface (such as a WI-FI interface, a Bluetooth interface, etc.), which is usually used in the electronic device 1 Establish a communication connection with other electronic devices.
- the electronic device 1 may also include a user interface.
- the user interface may be a display (Display) and an input unit (such as a keyboard (Keyboard)).
- the user interface may also be a standard wired interface or a wireless interface.
- the display may be an LED display, a liquid crystal display, a touch-sensitive liquid crystal display, an OLED (Organic Light-Emitting Diode, organic light-emitting diode) touch device, etc.
- the display can also be appropriately called a display screen or a display unit, which is used to display the information processed in the electronic device 1 and to display a visualized user interface.
- the link state tracking program 12 stored in the memory 11 in the electronic device 1 is a combination of multiple instructions. When running in the processor 10, it can realize:
- Target link information in the link log, where the target link information includes multiple nodes in the target link and the hierarchical relationship between each node;
- the link tracking statement is executed to obtain the status of the node in the target link that has been marked with the link tracking ID.
- the integrated module/unit of the electronic device 1 is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer readable storage medium.
- the computer-readable storage medium may be volatile or non-volatile, and the computer-readable medium may include: any entity or device capable of carrying the computer program code, recording medium, U disk, Mobile hard disks, magnetic disks, optical disks, computer memory, read-only memory (ROM, Read-Only Memory).
- the computer usable storage medium may mainly include a storage program area and a storage data area, where the storage program area may store an operating system, a computer program required by at least one function, etc.; the storage data area may store a block chain node When the computer program is executed by the processor, it can realize:
- Target link information in the link log, where the target link information includes multiple nodes in the target link and the hierarchical relationship between each node;
- the link tracking statement is executed to obtain the status of the node in the target link that has been marked with the link tracking ID.
- modules described as separate components may or may not be physically separated, and the components displayed as modules may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the modules can be selected according to actual needs to achieve the objectives of the solutions of the embodiments.
- the functional modules in the various embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units may be integrated into one unit.
- the above-mentioned integrated unit may be implemented in the form of hardware, or may be implemented in the form of hardware plus software functional modules.
- the blockchain referred to in this application is a new application mode of computer technology such as distributed data storage, point-to-point transmission, consensus mechanism, and encryption algorithm.
- Blockchain essentially a decentralized database, is a series of data blocks associated with cryptographic methods. Each data block contains a batch of network transaction information for verification. The validity of the information (anti-counterfeiting) and the generation of the next block.
- the blockchain can include the underlying platform of the blockchain, the platform product service layer, and the application service layer.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Hardware Design (AREA)
- Computer Security & Cryptography (AREA)
- Computing Systems (AREA)
- General Engineering & Computer Science (AREA)
- Power Engineering (AREA)
- Automation & Control Theory (AREA)
- Debugging And Monitoring (AREA)
Abstract
本申请涉及数据处理技术,揭露了一种链路状态的追踪方法,包括:获取链路日志;提取链路日志中的目标链路信息;生成追踪ID,将目标链路中多个节点标记为目标链路追踪ID;获取节点IP标识,将目标链路中相邻节点的节点IP标识组合为层级IP;获取目标链路追踪请求,将所述层级IP作为目标链路追踪请求的请求头,将所述链路追踪ID作为链路追踪请求的请求体,得到链路追踪语句;执行链路追踪语句获取目标链路中已标记链路追踪ID的节点的状态。本申请还提出了链路状态的追踪装置、设备及计算机可读存储介质。此外,本申请还涉及区块链技术,链路日志可存储于区块链节点中。本申请可以对分布式***中链路节点的状态进行追踪,提高链路追踪方法的可移植性。
Description
本申请要求于2020年9月24日提交中国专利局、申请号为CN202011013687.4,发明名称为“链路状态的追踪方法、装置、电子设备及计算机存储介质”的中国专利申请的优先权,其全部内容通过引用结合在本申请中。
本申请涉及数据处理技术领域,尤其涉及一种链路状态的追踪方法、装置、电子设备及计算机可读存储介质。
在对分布式***进行维护时,需要查看分布式***中链路的节点状态。现有技术中,常用的技术方法是在不同分布式***中链路的每个节点上提前根据分布式***自身的属性来配置节点的IP和节点所属链路的ID,例如以链路的功能来命名链路的ID,以节点的功能来命名节点的IP。该方法需要预先保证同一链路中每个节点上链路的ID配置的一致性、同一链路中所有节点上节点的IP配置的统一性,才可以实现查看分布式***中链路的节点状态。发明人意识到由于节点的IP和节点所属链路的ID是根据分布式***自身的属性预先配置完成的,因此,若在不同的分布式***查看中链路的节点状态,需要根据不同的分布式***重新配置节点的IP和节点所属链路的ID,造成链路追踪方法的可移植性不高。因此如何实现对不同的分布式***进行动态的自动化链路节点的状态追踪,提高链路追踪方法的可移植性,成为了亟待解决的问题。
发明内容
一种链路状态的追踪方法,包括:
获取分布式***中的链路日志;
提取所述链路日志中的目标链路信息,所述目标链路信息包括目标链路中的多个节点和各节点之间的层级关系;
生成所述目标链路的追踪ID,将所述目标链路中多个节点标记为所述目标链路追踪ID;
获取所述目标链路中各节点的节点IP标识,将所述目标链路中相邻节点的节点IP标识组合为层级IP;
获取目标链路追踪请求,将所述层级IP作为所述目标链路追踪请求的请求头,将所述链路追踪ID作为链路追踪请求的请求体,得到链路追踪语句;
执行所述链路追踪语句获取所述目标链路中已标记所述链路追踪ID的节点的状态。
一种链路状态的追踪装置,所述装置包括:
链路日志获取模块,用于获取分布式***中的链路日志;
目标链路信息提取模块,用于提取所述链路日志中的目标链路信息,所述目标链路信息包括目标链路中的多个节点和各节点之间的层级关系;
追踪ID生成模块,用于生成所述目标链路的追踪ID,将所述目标链路中多个节点标记为所述目标链路追踪ID;
节点IP标识获取模块,用于获取所述目标链路中各节点的节点IP标识,将所述目标链路中相邻节点的节点IP标识组合为层级IP;
链路追踪语句生成模块,用于获取目标链路追踪请求,将所述层级IP作为目标链路追踪请求的请求头,将所述链路追踪ID作为所述链路追踪请求的请求体,得到链路追踪语句;
链路状态追踪模块,用于执行所述链路追踪语句获取所述目标链路中已标记所述链路 追踪ID的节点的状态。
为了解决上述问题,本申请还提供一种电子设备,所述电子设备包括:
存储器,存储至少一个指令;及
处理器,执行所述存储器中存储的指令以实现如下步骤:
获取分布式***中的链路日志;
提取所述链路日志中的目标链路信息,所述目标链路信息包括目标链路中的多个节点和各节点之间的层级关系;
生成所述目标链路的追踪ID,将所述目标链路中多个节点标记为所述目标链路追踪ID;
获取所述目标链路中各节点的节点IP标识,将所述目标链路中相邻节点的节点IP标识组合为层级IP;
获取目标链路追踪请求,将所述层级IP作为所述目标链路追踪请求的请求头,将所述链路追踪ID作为链路追踪请求的请求体,得到链路追踪语句;
执行所述链路追踪语句获取所述目标链路中已标记所述链路追踪ID的节点的状态。
一种计算机可读存储介质,包括存储数据区和存储程序区,存储数据区存储创建的数据,存储程序区存储有计算机程序;其中,所述计算机程序被处理器执行时实现如下步骤:
获取分布式***中的链路日志;
提取所述链路日志中的目标链路信息,所述目标链路信息包括目标链路中的多个节点和各节点之间的层级关系;
生成所述目标链路的追踪ID,将所述目标链路中多个节点标记为所述目标链路追踪ID;
获取所述目标链路中各节点的节点IP标识,将所述目标链路中相邻节点的节点IP标识组合为层级IP;
获取目标链路追踪请求,将所述层级IP作为所述目标链路追踪请求的请求头,将所述链路追踪ID作为链路追踪请求的请求体,得到链路追踪语句;
执行所述链路追踪语句获取所述目标链路中已标记所述链路追踪ID的节点的状态。
本申请可以对分布式***中链路节点的状态进行追踪,提高链路追踪方法的可移植性。
图1为本申请一实施例提供的链路状态的追踪方法的流程示意图;
图2为本申请一实施例提供的链路状态的追踪装置的模块示意图;
图3为本申请一实施例提供的实现链路状态的追踪方法的电子设备的内部结构示意图;
本申请目的的实现、功能特点及优点将结合实施例,参照附图做进一步说明。
应当理解,此处所描述的具体实施例仅仅用以解释本申请,并不用于限定本申请。
本申请实施例提供的链路状态的追踪方法的执行主体包括但不限于服务端、终端等能够被配置为执行本申请实施例提供的该方法的电子设备中的至少一种。换言之,所述链路状态的追踪方法可以由安装在终端设备或服务端设备的软件或硬件来执行,所述软件可以是区块链平台。所述服务端包括但不限于:单台服务器、服务器集群、云端服务器或云端服务器集群等。
本申请提供一种链路状态的追踪方法。参照图1所示,为本申请一实施例提供的链路状态的追踪方法的流程示意图。该方法可以由一个装置执行,该装置可以由软件和/或硬件实现。
在本实施例中,链路状态的追踪方法包括:
S1、获取分布式***中的链路日志。
本申请实施例中,所述链路日志为分布式***在执行操作时产生的日志。例如,分布 式***在执行服务调用操作时,需要分布式***中的多个后台服务共同完成服务调用操作,多个后台服务共同组成一条链路,每个后台服务在执行服务调用操作的过程中所产生的数据,即为链路日志。
详细地,所述获取分布式***中的链路日志,包括:
当监听到分布式***的第一后台服务中存在链路日志生成事件时,根据监听到的链路日志生成事件在所述第一后台服务和所述第一后台服务以外的其他后台服务中查找生成的链路日志。
分布式***中包含多个后台服务,分布式***在执行进程时,由于需要多个后台服务相互配合,因此每个后台服务均会产生链路日志,为了获取完整的链路日志,需要在所有后台服务中查找生成的链路日志。例如,分布式***在完成服务调用操作时,需要由后台服务A、后台服务B与后台服务C共同完成服务调用操作,当监听到后台服务A中出现的链路日志生成事件时,根据监听到的链路日志生成事件在后台服务A中查找生成的链路日志,并根据监听到的链路日志生成事件在后台服务B与后台服务C中查找生成的链路日志。通过在完成服务调用操作所需的所有后台服务中查找链路日志,提高了链路日志的完整性。
进一步地,所述获取分布式***中的链路日志之前,所述方法还包括:
接收链路状态追踪指令;
提取所述链路状态追踪指令中的用户信息,所述用户信息包括用户的唯一标识和所述用户的密码;
根据所述用户的唯一标识和所述用户的密码,判断所述用户是否是授权用户;
若所述用户是授权用户,执行所述获取分布式***中的链路日志的操作。
本申请实施例中,用户信息包括用户的唯一标识和所述用户的密码,根据用户信息可唯一确定用户的身份,进而判定用户是否是授权用户,若用户为授权用户,根据监听到的链路日志生成事件查找生成的链路日志。
本申请实施例通过对用户身份的验证,可提高分布式***中链路状态追踪的安全性。
具体地,所述根据所述用户的唯一标识和所述用户的密码,判断所述用户是否是授权用户,包括:
当所述用户的唯一标识和所述用户的密码中的任意一项与预先存储信息不匹配时,确定所述用户不是授权用户;
当所述用户的唯一标识和所述用户的密码与预先存储信息都匹配时,确定所述用户是授权用户。
S2、提取所述链路日志中的目标链路信息,所述目标链路信息包括目标链路中的多个节点和各节点之间的层级关系。
本申请实施例中,所述提取所述链路日志中的目标链路信息,包括:
获取训练链路日志以及所述训练链路日志对应的标准目标链路信息;
利用预设的信息提取模型对所述训练链路日志进行特征提取,得到预测目标链路信息;
计算所述预测目标链路信息和所述标准目标链路信息之间的差异值;
若所述差异值大于误差阈值,则调整所述信息提取模型的参数后重新进行特征提取;
若所述差异值小于所述误差阈值,则生成训练完成的信息提取模型;
利用训练完成的信息提取模型对所述轨迹数据集进行信息提取,得到目标链路信息。
较佳地,所述计算所述预测目标链路信息和所述标准目标链路信息之间的差异值,包括:
详细地,本申请实施例通过梯度下降算法调整所述信息提取模型的参数,所述梯度下降算法包括但不限于:批量梯度下降算法、随机梯度下降算法和小批量梯度下降算法。
S3、生成所述目标链路的追踪ID,将所述目标链路中多个节点标记为所述目标链路追踪ID。
本申请实施例中,所述生成所述目标链路的追踪ID,包括:
获取唯一编码函数;
利用编译器将所述唯一编码函数编译为编码生成语句;
执行所述编码生成语句生成ID编码,确定所述ID编码为所述目标链路的链路追踪ID。
详细地,所述唯一编码函数包括但不限于GUID函数。GUID函数为一种可生成长度为128位的二进制数字标识符的函数,任何计算机或计算机集群都无法使用GUID函数生成两个相同的二进制数字标识符。
本申请实施例利用编译器将GUID函数编译为编码生成语句,通过执行编码生成语句生成ID编码,利用GUID函数生成的二进制数字标识符(即ID编码)作为目标链路的链路追踪ID,保证了链路追踪ID的唯一性,有利于准确获取最终不同链路的状态。
本申请实施例中,获取链路追踪ID后,将所述目标链路中多个节点标记为所述目标链路追踪ID。例如,目标链路中存在节点Q、节点P、节点M以及节点Z,当目标链路追踪ID为1xxxxx0时,将目标链路中的节点Q、节点P、节点M以及节点Z添加1xxxxx0的标记。
S4、获取所述目标链路中各节点的节点IP标识,将所述目标链路中相邻节点的节点IP标识组合为层级IP。
本申请实施例中,所述获取所述目标链路中各节点的节点IP标识,包括:
获取所述目标链路的各节点的设备信息;
根据所述设备信息在IP地址表中查询,得到所述设备信息对应的IP地址,确定所述IP地址为所述目标链路中各节点的节点IP标识。
具体地,本申请实施例可利用句数据抓取功能的python语句从用于存储分布式***的***信息的文件中所述目标链路的各节点的设备信息。
详细地,本申请实施例中,所述IP地址表为用户预先设定的,所述IP地址表中包含至少一个节点的设备信息,以及设备信息唯一对应的IP地址。
进一步地,本申请实施例将目标链路中相邻节点的节点IP标识组合为层级IP,以使用层级IP对目标链路中相邻节点之间的层级关系进行标记。例如,目标链路中存在相邻节点E与节点R,节点E的节点IP标识为123.456.7.8,节点R的节点IP标识为321.654.8.7,则将节点E与节点R的节点IP标识组合为层级IP:123.456.7.8-321.654.8.7,利用层级IP:123.456.7.8-321.654.8.7对相邻节点E与节点R之间的层级关系进行标记。
较佳地,将目标链路中相邻节点的节点IP标识组合为层级IP时,可根据目标链路中相邻节点之间的层级关系对节点IP标识进行组合。例如,若相邻节点E与节点R之间的层级关系为节点E调用节点R,则将节点E与节点R的节点IP标识组合为层级IP:123.456.7.8-321.654.8.7;若相邻节点E与节点R之间的层级关系为节点R调用节点E,则将节点E与节点R的节点IP标识组合为层级IP:321.654.8.7-123.456.7.8。
S5、获取目标链路追踪请求,将所述层级IP作为目标链路追踪请求的请求头,将所述链路追踪ID作为链路追踪请求的请求体,得到链路追踪语句。
本申请实施例中,所述目标链路追踪请求可由用户预先给定。所述目标链路追踪请求包括请求头和请求体,其中,请求头用于存放层级IP,用于追踪目标链路中的节点状态,请求体用于存放链路追踪ID,用于追踪分布式***中完整的目标链路的状态。
例如,目标链路追踪ID为1xxxxx0;层级IP为123.456.7.8-321.654.8.7;将123.456.7.8-321.654.8.7写入请求头,将1xxxxx0写入请求体,得到链路追踪语句。
S6、执行所述链路追踪语句获取所述目标链路中已标记所述链路追踪ID的节点的状态。
本申请实施例中,所述执行所述链路追踪语句获取所述目标链路中已标记所述链路追踪ID的节点的状态,包括:
利用自定义处理函数构建追踪时间规则;
根据所述追踪时间规则执行所述链路追踪语句获取目标链路中目标链路中已标记所述链路追踪ID的节点的状态。
详细地,所述自定义处理函数包括但不限于以下一项或多项:
IF函数,用于判断追踪条件;
TO_DATE函数,用于表示日期;
U_TIME函数,用于自定义追踪的时间;
U_DIV函数,用于检测分布式***的编译环境。
具体地,所述利用自定义处理函数构建追踪时间规则,包括:
获取与预设追踪时间对应的自定义处理函数;
检测分布式***的编译环境;
通过与所述编译环境对应的编译器对所述自定义处理函数进行编译,得到所述追踪时间规则。
本申请实施例中,通过构建自定义处理函数可以实现根据追踪时间规则对所述分布式***的目标链路中已标记所述链路追踪ID的状态进行追踪,从而避免频繁或持续追踪占用大量***资源,造成追踪效率低下的问题。
本申请实施例通过获取目标链路中的多个节点和各节点之间的层级关系,并生成目标链路的追踪ID,将目标链路中多个节点标记为所述目标链路追踪ID,获取目标链路中各节点的节点IP标识,将目标链路中相邻节点的节点IP标识组合为层级IP,实现了自动化对目标链路的节点进行标记,而无需在目标链路的每个节点上提前根据分布式***自身的属性来配置节点的IP和节点所属链路的ID,避免了在不同分布式***中进行链路节点状态的调用时,需要根据不同的分布式***重新配置节点的IP和节点所属链路的ID的问题,提高链路追踪方法的可移植性。因此本申请提出的链路状态的追踪方法,可以对分布式***中链路节点的状态进行追踪,提高链路追踪方法的可移植性。
如图2所示,是本申请链路状态的追踪装置的模块示意图。
本申请所述链路状态的追踪装置100可以安装于电子设备中。根据实现的功能,所述链路状态的追踪装置可以包括链路日志获取模块101、目标链路信息提取模块102、追踪ID生成模块103、节点IP标识获取模块104、链路追踪语句生成模块105和链路状态追踪模块106。本申请所述模块也可以称之为单元,是指一种能够被电子设备处理器所执行,并且能够完成固定功能的一系列计算机程序段,其存储在电子设备的存储器中。
在本实施例中,关于各模块/单元的功能如下:
所述链路日志获取模块101,用于获取分布式***中的链路日志;
所述目标链路信息提取模块102,用于提取所述链路日志中的目标链路信息,所述目标链路信息包括目标链路中的多个节点和各节点之间的层级关系;
所述追踪ID生成模块103,用于生成所述目标链路的追踪ID,将所述目标链路中多个节点标记为所述目标链路追踪ID;
所述节点IP标识获取模块104,用于获取所述目标链路中各节点的节点IP标识,将所述目标链路中相邻节点的节点IP标识组合为层级IP;
所述链路追踪语句生成模块105,用于获取目标链路追踪请求,将所述层级IP作为目标链路追踪请求的请求头,将所述链路追踪ID作为链路追踪请求的请求体,得到链路追踪语句;
所述链路状态追踪模块106,用于执行所述链路追踪语句获取所述目标链路中已标记所述链路追踪ID的节点的状态。
详细地,所述链路状态的追踪装置各模块的具体实施方式如下:
所述链路日志获取模块101,用于获取分布式***中的链路日志。
本申请实施例中,所述链路日志为分布式***在执行操作时产生的日志。例如,分布式***在执行服务调用操作时,需要分布式***中的多个后台服务共同完成服务调用操作,多个后台服务共同组成一条链路,每个后台服务在执行服务调用操作的过程中所产生的数据,即为链路日志。
详细地,所述链路日志获取模块101具体用于:
当监听到分布式***的第一后台服务中存在链路日志生成事件时,根据监听到的链路日志生成事件在所述第一后台服务和所述第一后台服务以外的其他后台服务中查找生成的链路日志。
分布式***中包含多个后台服务,分布式***在执行进程时,由于需要多个后台服务相互配合,因此每个后台服务均会产生链路日志,为了获取完整的链路日志,需要在所有后台服务中查找生成的链路日志。例如,分布式***在完成服务调用操作时,需要由后台服务A、后台服务B与后台服务C共同完成服务调用操作,当监听到后台服务A中出现的链路日志生成事件时,根据监听到的链路日志生成事件在后台服务A中查找生成的链路日志,并根据监听到的链路日志生成事件在后台服务B与后台服务C中查找生成的链路日志。通过在完成服务调用操作所需的所有后台服务中查找链路日志,提高了链路日志的完整性。
进一步地,所述链路状态的追踪装置还包括身份验证模块,所述身份验证模块具体用于:
接收链路状态追踪指令;
提取所述链路状态追踪指令中的用户信息,所述用户信息包括用户的唯一标识和所述用户的密码;
根据所述用户的唯一标识和所述用户的密码,判断所述用户是否是授权用户;
若所述用户是授权用户,执行所述获取分布式***中的链路日志的操作。
本申请实施例中,用户信息包括用户的唯一标识和所述用户的密码,根据用户信息可唯一确定用户的身份,进而判定用户是否是授权用户,若用户为授权用户,根据监听到的链路日志生成事件查找生成的链路日志。
本申请实施例通过对用户身份的验证,可提高分布式***中链路状态追踪的安全性。
具体地,所述根据所述用户的唯一标识和所述用户的密码,判断所述用户是否是授权用户,包括:
当所述用户的唯一标识和所述用户的密码中的任意一项与预先存储信息不匹配时,确定所述用户不是授权用户;
当所述用户的唯一标识和所述用户的密码与预先存储信息都匹配时,确定所述用户是授权用户。
所述目标链路信息提取模块102,用于提取所述链路日志中的目标链路信息,所述目标链路信息包括目标链路中的多个节点和各节点之间的层级关系。
本申请实施例中,所述目标链路信息提取模块102具体用于:
获取训练链路日志以及所述训练链路日志对应的标准目标链路信息;
利用预设的信息提取模型对所述训练链路日志进行特征提取,得到预测目标链路信息;
计算所述预测目标链路信息和所述标准目标链路信息之间的差异值;
若所述差异值大于误差阈值,则调整所述信息提取模型的参数后重新进行特征提取;
若所述差异值小于所述误差阈值,则生成训练完成的信息提取模型;
利用训练完成的信息提取模型对所述轨迹数据集进行信息提取,得到目标链路信息。
较佳地,所述计算所述预测目标链路信息和所述标准目标链路信息之间的差异值,包括:
详细地,本申请实施例通过梯度下降算法调整所述信息提取模型的参数,所述梯度下降算法包括但不限于:批量梯度下降算法、随机梯度下降算法和小批量梯度下降算法。
所述追踪ID生成模块103,用于生成所述目标链路的追踪ID,将所述目标链路中多个节点标记为所述目标链路追踪ID。
本申请实施例中,所述追踪ID生成模块103具体用于:
获取唯一编码函数;
利用编译器将所述唯一编码函数编译为编码生成语句;
执行所述编码生成语句生成ID编码,确定所述ID编码为所述目标链路的链路追踪ID;
将所述目标链路中多个节点标记为所述目标链路追踪ID。
详细地,所述唯一编码函数包括但不限于GUID函数。GUID函数为一种可生成长度为128位的二进制数字标识符的函数,任何计算机或计算机集群都无法使用GUID函数生成两个相同的二进制数字标识符。
本申请实施例利用编译器将GUID函数编译为编码生成语句,通过执行编码生成语句生成ID编码,利用GUID函数生成的二进制数字标识符(即ID编码)作为目标链路的链路追踪ID,保证了链路追踪ID的唯一性,有利于准确获取最终不同链路的状态。
本申请实施例中,获取链路追踪ID后,将所述目标链路中多个节点标记为所述目标链路追踪ID。例如,目标链路中存在节点Q、节点P、节点M以及节点Z,当目标链路追踪ID为1xxxxx0时,将目标链路中的节点Q、节点P、节点M以及节点Z添加1xxxxx0的标记。
所述节点IP标识获取模块104,用于获取所述目标链路中各节点的节点IP标识,将所述目标链路中相邻节点的节点IP标识组合为层级IP。
本申请实施例中,所述节点IP标识获取模块104具体用于:
获取所述目标链路的各节点的设备信息;
根据所述设备信息在IP地址表中查询,得到所述设备信息对应的IP地址,确定所述IP地址为所述目标链路中各节点的节点IP标识;
将所述目标链路中相邻节点的节点IP标识组合为层级IP。
具体地,本申请实施例可利用句数据抓取功能的python语句从用于存储分布式***的***信息的文件中所述目标链路的各节点的设备信息。
详细地,本申请实施例中,所述IP地址表为用户预先设定的,所述IP地址表中包含至少一个节点的设备信息,以及设备信息唯一对应的IP地址。
进一步地,本申请实施例将目标链路中相邻节点的节点IP标识组合为层级IP,以使用层级IP对目标链路中相邻节点之间的层级关系进行标记。例如,目标链路中存在相邻节点E与节点R,节点E的节点IP标识为123.456.7.8,节点R的节点IP标识为321.654.8.7,则将节点E与节点R的节点IP标识组合为层级IP:123.456.7.8-321.654.8.7,利用层级IP:123.456.7.8-321.654.8.7对相邻节点E与节点R之间的层级关系进行标记。
较佳地,将目标链路中相邻节点的节点IP标识组合为层级IP时,可根据目标链路中相邻节点之间的层级关系对节点IP标识进行组合。例如,若相邻节点E与节点R之间的层级关系为节点E调用节点R,则将节点E与节点R的节点IP标识组合为层级IP:123.456.7.8-321.654.8.7;若相邻节点E与节点R之间的层级关系为节点R调用节点E,则将节点E与节点R的节点IP标识组合为层级IP:321.654.8.7-123.456.7.8。
所述链路追踪语句生成模块105,用于获取目标链路追踪请求,将所述层级IP作为目标链路追踪请求的请求头,将所述链路追踪ID作为链路追踪请求的请求体,得到链路追踪语句。
本申请实施例中,所述目标链路追踪请求可由用户预先给定。所述目标链路追踪请求包括请求头和请求体,其中,请求头用于存放层级IP,用于追踪目标链路中的节点状态,请求体用于存放链路追踪ID,用于追踪分布式***中完整的目标链路的状态。
例如,目标链路追踪ID为1xxxxx0;层级IP为123.456.7.8-321.654.8.7;将123.456.7.8-321.654.8.7写入请求头,将1xxxxx0写入请求体,得到链路追踪语句。
所述链路状态追踪模块106,用于执行所述链路追踪语句获取所述目标链路中已标记所述链路追踪ID的节点的状态。
本申请实施例中,所述链路状态追踪模块106具体用于:
利用自定义处理函数构建追踪时间规则;
根据所述追踪时间规则执行所述链路追踪语句获取目标链路中目标链路中已标记所述链路追踪ID的节点的状态。
详细地,所述自定义处理函数包括但不限于以下一项或多项:
IF函数,用于判断追踪条件;
TO_DATE函数,用于表示日期;
U_TIME函数,用于自定义追踪的时间;
U_DIV函数,用于检测分布式***的编译环境。
具体地,所述利用自定义处理函数构建追踪时间规则,包括:
获取与预设追踪时间对应的自定义处理函数;
检测分布式***的编译环境;
通过与所述编译环境对应的编译器对所述自定义处理函数进行编译,得到所述追踪时间规则。
本申请实施例中,通过构建自定义处理函数可以实现根据追踪时间规则对所述分布式***的目标链路中已标记所述链路追踪ID的状态进行追踪,从而避免频繁或持续追踪占用大量***资源,造成追踪效率低下的问题。
本申请实施例通过获取目标链路中的多个节点和各节点之间的层级关系,并生成目标链路的追踪ID,将目标链路中多个节点标记为所述目标链路追踪ID,获取目标链路中各节点的节点IP标识,将目标链路中相邻节点的节点IP标识组合为层级IP,实现了自动化对目标链路的节点进行标记,而无需在目标链路的每个节点上提前根据分布式***自身的属性来配置节点的IP和节点所属链路的ID,避免了在不同分布式***中进行链路节点状态的调用时,需要根据不同的分布式***重新配置节点的IP和节点所属链路的ID的问题,提高链路追踪方法的可移植性。因此本申请提出的链路状态的追踪装置,可以对分布式***中链路节点的状态进行追踪,提高链路追踪方法的可移植性。
如图3所示,是本申请实现链路状态的追踪方法的电子设备的结构示意图。
所述电子设备1可以包括处理器10、存储器11和总线,还可以包括存储在所述存储器11中并可在所述处理器10上运行的计算机程序,如链路状态的追踪程序12。
其中,所述存储器11至少包括一种类型的可读存储介质,所述可读存储介质包括闪存、移动硬盘、多媒体卡、卡型存储器(例如:SD或DX存储器等)、磁性存储器、磁盘、光盘等。所述存储器11在一些实施例中可以是电子设备1的内部存储单元,例如该电子设备1的移动硬盘。所述存储器11在另一些实施例中也可以是电子设备1的外部存储设备,例如电子设备1上配备的插接式移动硬盘、智能存储卡(Smart Media Card,SMC)、安全数字(Secure Digital,SD)卡、闪存卡(Flash Card)等。进一步地,所述存储器11还可以既包括电子设备1的内部存储单元也包括外部存储设备。所述存储器11不仅可以用于存储安装于电子设备1的应用软件及各类数据,例如链路状态的追踪程序12的代码等,还可以用于暂时地存储已经输出或者将要输出的数据。
所述处理器10在一些实施例中可以由集成电路组成,例如可以由单个封装的集成电路所组成,也可以是由多个相同功能或不同功能封装的集成电路所组成,包括一个或者多个中央处理器(Central Processing unit,CPU)、微处理器、数字处理芯片、图形处理器及各种控制芯片的组合等。所述处理器10是所述电子设备的控制核心(Control Unit),利用各种接口和线路连接整个电子设备的各个部件,通过运行或执行存储在所述存储器11内的程序或者模块(例如执行链路状态的追踪程序等),以及调用存储在所述存储器11内的数据,以执行电子设备1的各种功能和处理数据。
所述总线可以是外设部件互连标准(peripheral component interconnect,简称PCI)总线或扩展工业标准结构(extended industry standard architecture,简称EISA)总线等。该总线可以分为地址总线、数据总线、控制总线等。所述总线被设置为实现所述存储器11以及至少一个处理器10等之间的连接通信。
图3仅示出了具有部件的电子设备,本领域技术人员可以理解的是,图3示出的结构并不构成对所述电子设备1的限定,可以包括比图示更少或者更多的部件,或者组合某些部件,或者不同的部件布置。
例如,尽管未示出,所述电子设备1还可以包括给各个部件供电的电源(比如电池),优选地,电源可以通过电源管理装置与所述至少一个处理器10逻辑相连,从而通过电源管理装置实现充电管理、放电管理、以及功耗管理等功能。电源还可以包括一个或一个以上的直流或交流电源、再充电装置、电源故障检测电路、电源转换器或者逆变器、电源状态指示器等任意组件。所述电子设备1还可以包括多种传感器、蓝牙模块、Wi-Fi模块等,在此不再赘述。
进一步地,所述电子设备1还可以包括网络接口,可选地,所述网络接口可以包括有线接口和/或无线接口(如WI-FI接口、蓝牙接口等),通常用于在该电子设备1与其他电子设备之间建立通信连接。
可选地,该电子设备1还可以包括用户接口,用户接口可以是显示器(Display)、输入单元(比如键盘(Keyboard)),可选地,用户接口还可以是标准的有线接口、无线接口。可选地,在一些实施例中,显示器可以是LED显示器、液晶显示器、触控式液晶显示器以及OLED(Organic Light-Emitting Diode,有机发光二极管)触摸器等。其中,显示器也可以适当的称为显示屏或显示单元,用于显示在电子设备1中处理的信息以及用于显示可视化的用户界面。
应该了解,所述实施例仅为说明之用,在专利申请范围上并不受此结构的限制。
所述电子设备1中的所述存储器11存储的链路状态的追踪程序12是多个指令的组合,在所述处理器10中运行时,可以实现:
获取分布式***中的链路日志;
提取所述链路日志中的目标链路信息,所述目标链路信息包括目标链路中的多个节点和各节点之间的层级关系;
生成所述目标链路的追踪ID,将所述目标链路中多个节点标记为所述目标链路追踪ID;
获取所述目标链路中各节点的节点IP标识,将所述目标链路中相邻节点的节点IP标识组合为层级IP;
获取目标链路追踪请求,将所述层级IP作为所述目标链路追踪请求的请求头,将所述链路追踪ID作为链路追踪请求的请求体,得到链路追踪语句;
执行所述链路追踪语句获取所述目标链路中已标记所述链路追踪ID的节点的状态。
进一步地,所述电子设备1集成的模块/单元如果以软件功能单元的形式实现并作为独立的产品销售或使用时,可以存储在一个计算机可读取存储介质中。所述计算机可读存储介质可以是易失性的,也可以是非易失性的,所述计算机可读介质可以包括:能够携带所述计算机程序代码的任何实体或装置、记录介质、U盘、移动硬盘、磁碟、光盘、计算机存储器、只读存储器(ROM,Read-Only Memory)。
进一步地,所述计算机可用存储介质可主要包括存储程序区和存储数据区,其中,存储程序区可存储操作***、至少一个功能所需的计算机程序等;存储数据区可存储根据区块链节点的使用所创建的数据等,所述计算机程序被处理器执行时,可以实现:
获取分布式***中的链路日志;
提取所述链路日志中的目标链路信息,所述目标链路信息包括目标链路中的多个节点和各节点之间的层级关系;
生成所述目标链路的追踪ID,将所述目标链路中多个节点标记为所述目标链路追踪ID;
获取所述目标链路中各节点的节点IP标识,将所述目标链路中相邻节点的节点IP标识组合为层级IP;
获取目标链路追踪请求,将所述层级IP作为所述目标链路追踪请求的请求头,将所述链路追踪ID作为链路追踪请求的请求体,得到链路追踪语句;
执行所述链路追踪语句获取所述目标链路中已标记所述链路追踪ID的节点的状态。
本申请之计算机可读存储介质的具体实施方式与上述链路状态的追踪方法的具体实施方式大致相同,在此不再赘述。
在本申请所提供的几个实施例中,应该理解到,所揭露的设备,装置和方法,可以通过其它的方式实现。例如,以上所描述的装置实施例仅仅是示意性的,例如,所述模块的划分,仅仅为一种逻辑功能划分,实际实现时可以有另外的划分方式。
所述作为分离部件说明的模块可以是或者也可以不是物理上分开的,作为模块显示的部件可以是或者也可以不是物理单元,即可以位于一个地方,或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部模块来实现本实施例方案的目的。
另外,在本申请各个实施例中的各功能模块可以集成在一个处理单元中,也可以是各个单元单独物理存在,也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现,也可以采用硬件加软件功能模块的形式实现。
对于本领域技术人员而言,显然本申请不限于上述示范性实施例的细节,而且在不背离本申请的精神或基本特征的情况下,能够以其他的具体形式实现本申请。
因此,无论从哪一点来看,均应将实施例看作是示范性的,而且是非限制性的,本申请的范围由所附权利要求而不是上述说明限定,因此旨在将落在权利要求的等同要件的含义和范围内的所有变化涵括在本申请内。不应将权利要求中的任何附关联图表记视为限制所涉及的权利要求。
本申请所指区块链是分布式数据存储、点对点传输、共识机制、加密算法等计算机技术的新型应用模式。区块链(Blockchain),本质上是一个去中心化的数据库,是一串使用密码学方法相关联产生的数据块,每一个数据块中包含了一批次网络交易的信息,用于验证 其信息的有效性(防伪)和生成下一个区块。区块链可以包括区块链底层平台、平台产品服务层以及应用服务层等。
此外,显然“包括”一词不排除其他单元或步骤,单数不排除复数。***权利要求中陈述的多个单元或装置也可以由一个单元或装置通过软件或者硬件来实现。第二等词语用来表示名称,而并不表示任何特定的顺序。
最后应说明的是,以上实施例仅用以说明本申请的技术方案而非限制,尽管参照较佳实施例对本申请进行了详细说明,本领域的普通技术人员应当理解,可以对本申请的技术方案进行修改或等同替换,而不脱离本申请技术方案的精神和范围。
Claims (20)
- 一种链路状态的追踪方法,其中,所述方法包括:获取分布式***中的链路日志;提取所述链路日志中的目标链路信息,所述目标链路信息包括目标链路中的多个节点和各节点之间的层级关系;生成所述目标链路的追踪ID,将所述目标链路中多个节点标记为所述目标链路追踪ID;获取所述目标链路中各节点的节点IP标识,将所述目标链路中相邻节点的节点IP标识组合为层级IP;获取目标链路追踪请求,将所述层级IP作为所述目标链路追踪请求的请求头,将所述链路追踪ID作为链路追踪请求的请求体,得到链路追踪语句;执行所述链路追踪语句获取所述目标链路中已标记所述链路追踪ID的节点的状态。
- 如权利要求1所述的链路状态的追踪方法,其中,所述获取分布式***中的链路日志,包括:当监听到分布式***的第一后台服务中存在链路日志生成事件时,根据监听到的链路日志生成事件在所述第一后台服务和所述第一后台服务以外的其他后台服务中查找生成的链路日志。
- 如权利要求1所述的链路状态的追踪方法,其中,所述获取分布式***中的链路日志之前,所述方法还包括:接收链路状态追踪指令;提取所述链路状态追踪指令中的用户信息,所述用户信息包括用户的唯一标识和所述用户的密码;根据所述用户的唯一标识和所述用户的密码,判断所述用户是否是授权用户;若所述用户是授权用户,执行所述获取分布式***中的链路日志的操作。
- 如权利要求3所述的链路状态的追踪方法,其中,所述根据所述用户的唯一标识和所述用户的密码,判断所述用户是否是授权用户,包括:当所述用户的唯一标识和所述用户的密码中的任意一项与预先存储信息不匹配时,确定所述用户不是授权用户;当所述用户的唯一标识和所述用户的密码与预先存储信息都匹配时,确定所述用户是授权用户。
- 如权利要求1至4中任一项所述的链路状态的追踪方法,其中,所述生成所述目标链路的追踪ID,包括:获取唯一编码函数;利用编译器将所述唯一编码函数编译为编码生成语句;执行所述编码生成语句生成ID编码,确定所述ID编码为所述目标链路的链路追踪ID。
- 如权利要求1所述的链路状态的追踪方法,其中,所述执行所述链路追踪语句获取所述目标链路中已标记所述链路追踪ID的节点的状态,包括:利用自定义处理函数构建追踪时间规则;根据所述追踪时间规则执行所述链路追踪语句获取目标链路中目标链路中已标记所述链路追踪ID的节点的状态。
- 如权利要求6所述的链路状态的追踪方法,其中,所述利用自定义处理函数构建追踪时间规则,包括:获取与预设追踪时间对应的自定义处理函数;检测分布式***的编译环境;通过与所述编译环境对应的编译器对所述自定义处理函数进行编译,得到所述追踪时间规则。
- 一种链路状态的追踪装置,其中,所述装置包括:链路日志获取模块,用于获取分布式***中的链路日志;目标链路信息提取模块,用于提取所述链路日志中的目标链路信息,所述目标链路信息包括目标链路中的多个节点和各节点之间的层级关系;追踪ID生成模块,用于生成所述目标链路的追踪ID,将所述目标链路中多个节点标记为所述目标链路追踪ID;节点IP标识获取模块,用于获取所述目标链路中各节点的节点IP标识,将所述目标链路中相邻节点的节点IP标识组合为层级IP;链路追踪语句生成模块,用于获取目标链路追踪请求,将所述层级IP作为所述目标链路追踪请求的请求头,将所述链路追踪ID作为链路追踪请求的请求体,得到链路追踪语句;链路状态追踪模块,用于执行所述链路追踪语句获取所述目标链路中已标记所述链路追踪ID的节点的状态。
- 一种电子设备,其中,所述电子设备包括:至少一个处理器;以及,与所述至少一个处理器通信连接的存储器;其中,所述存储器存储有可被所述至少一个处理器执行的指令,所述指令被所述至少一个处理器执行,以使所述至少一个处理器能够执行如下步骤:获取分布式***中的链路日志;提取所述链路日志中的目标链路信息,所述目标链路信息包括目标链路中的多个节点和各节点之间的层级关系;生成所述目标链路的追踪ID,将所述目标链路中多个节点标记为所述目标链路追踪ID;获取所述目标链路中各节点的节点IP标识,将所述目标链路中相邻节点的节点IP标识组合为层级IP;获取目标链路追踪请求,将所述层级IP作为所述目标链路追踪请求的请求头,将所述链路追踪ID作为链路追踪请求的请求体,得到链路追踪语句;执行所述链路追踪语句获取所述目标链路中已标记所述链路追踪ID的节点的状态。
- 如权利要求9所述的电子设备,其中,所述获取分布式***中的链路日志,包括:当监听到分布式***的第一后台服务中存在链路日志生成事件时,根据监听到的链路日志生成事件在所述第一后台服务和所述第一后台服务以外的其他后台服务中查找生成的链路日志。
- 如权利要求9所述的电子设备,其中,所述获取分布式***中的链路日志之前,所述至少一个处理器还执行如下步骤:接收链路状态追踪指令;提取所述链路状态追踪指令中的用户信息,所述用户信息包括用户的唯一标识和所述用户的密码;根据所述用户的唯一标识和所述用户的密码,判断所述用户是否是授权用户;若所述用户是授权用户,执行所述获取分布式***中的链路日志的操作。
- 如权利要求11所述的电子设备,其中,所述根据所述用户的唯一标识和所述用户的密码,判断所述用户是否是授权用户,包括:当所述用户的唯一标识和所述用户的密码中的任意一项与预先存储信息不匹配时,确定所述用户不是授权用户;当所述用户的唯一标识和所述用户的密码与预先存储信息都匹配时,确定所述用户是 授权用户。
- 如权利要求9至12中任一项所述的电子设备,其中,所述生成所述目标链路的追踪ID,包括:获取唯一编码函数;利用编译器将所述唯一编码函数编译为编码生成语句;执行所述编码生成语句生成ID编码,确定所述ID编码为所述目标链路的链路追踪ID。
- 如权利要求9所述的电子设备,其中,所述执行所述链路追踪语句获取所述目标链路中已标记所述链路追踪ID的节点的状态,包括:利用自定义处理函数构建追踪时间规则;根据所述追踪时间规则执行所述链路追踪语句获取目标链路中目标链路中已标记所述链路追踪ID的节点的状态。
- 如权利要求14所述的电子设备,其中,所述利用自定义处理函数构建追踪时间规则,包括:获取与预设追踪时间对应的自定义处理函数;检测分布式***的编译环境;通过与所述编译环境对应的编译器对所述自定义处理函数进行编译,得到所述追踪时间规则。
- 一种计算机可读存储介质,包括存储数据区和存储程序区,存储数据区存储创建的数据,存储程序区存储有计算机程序;其中,所述计算机程序被处理器执行时实现如下步骤:获取分布式***中的链路日志;提取所述链路日志中的目标链路信息,所述目标链路信息包括目标链路中的多个节点和各节点之间的层级关系;生成所述目标链路的追踪ID,将所述目标链路中多个节点标记为所述目标链路追踪ID;获取所述目标链路中各节点的节点IP标识,将所述目标链路中相邻节点的节点IP标识组合为层级IP;获取目标链路追踪请求,将所述层级IP作为所述目标链路追踪请求的请求头,将所述链路追踪ID作为链路追踪请求的请求体,得到链路追踪语句;执行所述链路追踪语句获取所述目标链路中已标记所述链路追踪ID的节点的状态。
- 如权利要求16所述的计算机可读存储介质,其中,所述获取分布式***中的链路日志,包括:当监听到分布式***的第一后台服务中存在链路日志生成事件时,根据监听到的链路日志生成事件在所述第一后台服务和所述第一后台服务以外的其他后台服务中查找生成的链路日志。
- 如权利要求16所述的计算机可读存储介质,其中,所述获取分布式***中的链路日志之前,所述计算机程序被处理器执行时还实现如下步骤:接收链路状态追踪指令;提取所述链路状态追踪指令中的用户信息,所述用户信息包括用户的唯一标识和所述用户的密码;根据所述用户的唯一标识和所述用户的密码,判断所述用户是否是授权用户;若所述用户是授权用户,执行所述获取分布式***中的链路日志的操作。
- 如权利要求18所述的计算机可读存储介质,其中,所述根据所述用户的唯一标识和所述用户的密码,判断所述用户是否是授权用户,包括:当所述用户的唯一标识和所述用户的密码中的任意一项与预先存储信息不匹配时,确定所述用户不是授权用户;当所述用户的唯一标识和所述用户的密码与预先存储信息都匹配时,确定所述用户是授权用户。
- 如权利要求16至19中任一项所述的计算机可读存储介质,其中,所述生成所述目标链路的追踪ID,包括:获取唯一编码函数;利用编译器将所述唯一编码函数编译为编码生成语句;执行所述编码生成语句生成ID编码,确定所述ID编码为所述目标链路的链路追踪ID。
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202011013687.4 | 2020-09-24 | ||
CN202011013687.4A CN112134739B (zh) | 2020-09-24 | 2020-09-24 | 链路状态的追踪方法、装置、电子设备及计算机存储介质 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2021189899A1 true WO2021189899A1 (zh) | 2021-09-30 |
Family
ID=73840184
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2020/131976 WO2021189899A1 (zh) | 2020-09-24 | 2020-11-26 | 链路状态的追踪方法、装置、电子设备及计算机存储介质 |
Country Status (2)
Country | Link |
---|---|
CN (1) | CN112134739B (zh) |
WO (1) | WO2021189899A1 (zh) |
Cited By (13)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN114448776A (zh) * | 2022-01-28 | 2022-05-06 | 吉林亿联银行股份有限公司 | 一种链路追踪方法及装置 |
CN114679487A (zh) * | 2022-03-25 | 2022-06-28 | 度小满科技(北京)有限公司 | 链路处理方法、装置、存储介质、处理器 |
CN114691690A (zh) * | 2022-03-31 | 2022-07-01 | 烽台科技(北京)有限公司 | 一种数据同步方法、装置、计算机设备及介质 |
CN114860216A (zh) * | 2022-07-07 | 2022-08-05 | 麒麟软件有限公司 | 一种用于集成开发环境的c程序动态追踪方法及*** |
CN115174366A (zh) * | 2022-05-30 | 2022-10-11 | 阿里巴巴(中国)有限公司 | 数据处理方法以及装置 |
CN115470752A (zh) * | 2022-09-22 | 2022-12-13 | 沐曦科技(北京)有限公司 | 基于追踪文件的芯片功能验证*** |
CN115757303A (zh) * | 2022-11-14 | 2023-03-07 | 华青融天(北京)软件股份有限公司 | 分布式***中的指标追踪方法及装置 |
CN116225880A (zh) * | 2023-05-05 | 2023-06-06 | 支付宝(杭州)信息技术有限公司 | 用于链路追踪的方法、装置及*** |
CN116756044A (zh) * | 2023-08-11 | 2023-09-15 | 杭州罗莱迪思科技股份有限公司 | 一种基于数据链路追踪的rpc远程调试方法、装置及应用 |
CN116962407A (zh) * | 2023-07-31 | 2023-10-27 | 上海中汇亿达金融信息技术有限公司 | 分布式链路标签的处理方法,装置及应用 |
CN117632445A (zh) * | 2024-01-25 | 2024-03-01 | 杭州阿里云飞天信息技术有限公司 | 请求处理方法以及装置、任务执行方法以及装置 |
CN117891749A (zh) * | 2024-03-18 | 2024-04-16 | 卓望数码技术(深圳)有限公司 | Api应用安全监测方法、装置、设备及存储介质 |
CN117952041A (zh) * | 2024-03-26 | 2024-04-30 | 成都融见软件科技有限公司 | 基于驱动源码的x值追踪方法、电子设备和介质 |
Families Citing this family (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN112738218A (zh) * | 2020-12-28 | 2021-04-30 | 平安消费金融有限公司 | 基于区块链的跨会话链路追踪方法、装置及存储介质 |
CN115001952B (zh) * | 2022-05-25 | 2023-09-19 | 中移互联网有限公司 | 一种业务接口的故障定位方法及装置 |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN105573824A (zh) * | 2014-10-10 | 2016-05-11 | 腾讯科技(深圳)有限公司 | 分布式计算***的监控方法及*** |
US10133619B1 (en) * | 2015-06-08 | 2018-11-20 | Nutanix, Inc. | Cluster-wide virtual machine health monitoring |
CN110245035A (zh) * | 2019-05-20 | 2019-09-17 | 平安普惠企业管理有限公司 | 一种链路跟踪方法及装置 |
CN110569222A (zh) * | 2019-08-23 | 2019-12-13 | 浙江大搜车软件技术有限公司 | 链路追踪方法、装置、计算机设备和可读存储介质 |
Family Cites Families (13)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8949395B2 (en) * | 2004-06-01 | 2015-02-03 | Inmage Systems, Inc. | Systems and methods of event driven recovery management |
US8307010B2 (en) * | 2008-09-26 | 2012-11-06 | Microsoft Corporation | Data feature tracking through hierarchical node sets |
CN103124225B (zh) * | 2012-12-19 | 2015-12-02 | 杭州华为数字技术有限公司 | 多节点初始化的检测方法及装置、*** |
CN105704189B (zh) * | 2014-11-27 | 2020-01-10 | 中兴通讯股份有限公司 | 一种上下层链路之间的关联方法、装置和*** |
CN106790718A (zh) * | 2017-03-16 | 2017-05-31 | 北京搜狐新媒体信息技术有限公司 | 服务调用链路分析方法及*** |
US11036797B2 (en) * | 2017-10-12 | 2021-06-15 | Adtran, Inc. | Efficient storage and utilization of a hierarchical data set |
CN108183927A (zh) * | 2017-11-22 | 2018-06-19 | 链家网(北京)科技有限公司 | 一种分布式***中链路调用的监控方法及*** |
CN108462750A (zh) * | 2018-03-22 | 2018-08-28 | 平安好房(上海)电子商务有限公司 | 分布式调用追踪方法、业务***、监控***及存储介质 |
CN111625431B (zh) * | 2019-02-28 | 2022-04-22 | 华为技术有限公司 | 一种日志信息生成方法、装置及电子设备 |
CN110113200A (zh) * | 2019-04-29 | 2019-08-09 | 平安科技(深圳)有限公司 | 链路***与日志***的关联方法、装置及存储介质 |
CN110908997B (zh) * | 2019-10-09 | 2022-10-14 | 支付宝(杭州)信息技术有限公司 | 数据血缘构建方法、装置、服务器及可读存储介质 |
CN110908780B (zh) * | 2019-10-12 | 2023-07-21 | 中国平安财产保险股份有限公司 | 调度平台的任务梳理方法、装置、设备及存储介质 |
CN110830577B (zh) * | 2019-11-08 | 2022-02-11 | 深圳前海环融联易信息科技服务有限公司 | 服务请求调用追踪方法、装置、计算机设备及存储介质 |
-
2020
- 2020-09-24 CN CN202011013687.4A patent/CN112134739B/zh active Active
- 2020-11-26 WO PCT/CN2020/131976 patent/WO2021189899A1/zh active Application Filing
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN105573824A (zh) * | 2014-10-10 | 2016-05-11 | 腾讯科技(深圳)有限公司 | 分布式计算***的监控方法及*** |
US10133619B1 (en) * | 2015-06-08 | 2018-11-20 | Nutanix, Inc. | Cluster-wide virtual machine health monitoring |
CN110245035A (zh) * | 2019-05-20 | 2019-09-17 | 平安普惠企业管理有限公司 | 一种链路跟踪方法及装置 |
CN110569222A (zh) * | 2019-08-23 | 2019-12-13 | 浙江大搜车软件技术有限公司 | 链路追踪方法、装置、计算机设备和可读存储介质 |
Cited By (24)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN114448776A (zh) * | 2022-01-28 | 2022-05-06 | 吉林亿联银行股份有限公司 | 一种链路追踪方法及装置 |
CN114679487A (zh) * | 2022-03-25 | 2022-06-28 | 度小满科技(北京)有限公司 | 链路处理方法、装置、存储介质、处理器 |
CN114679487B (zh) * | 2022-03-25 | 2023-12-22 | 度小满科技(北京)有限公司 | 链路处理方法、装置、存储介质、处理器 |
CN114691690A (zh) * | 2022-03-31 | 2022-07-01 | 烽台科技(北京)有限公司 | 一种数据同步方法、装置、计算机设备及介质 |
CN115174366B (zh) * | 2022-05-30 | 2023-10-20 | 浙江天猫技术有限公司 | 数据处理方法以及装置 |
CN115174366A (zh) * | 2022-05-30 | 2022-10-11 | 阿里巴巴(中国)有限公司 | 数据处理方法以及装置 |
CN114860216A (zh) * | 2022-07-07 | 2022-08-05 | 麒麟软件有限公司 | 一种用于集成开发环境的c程序动态追踪方法及*** |
CN114860216B (zh) * | 2022-07-07 | 2022-11-08 | 麒麟软件有限公司 | 一种用于集成开发环境的c程序动态追踪方法及*** |
CN115470752A (zh) * | 2022-09-22 | 2022-12-13 | 沐曦科技(北京)有限公司 | 基于追踪文件的芯片功能验证*** |
CN115470752B (zh) * | 2022-09-22 | 2023-07-14 | 沐曦科技(北京)有限公司 | 基于追踪文件的芯片功能验证*** |
CN115757303B (zh) * | 2022-11-14 | 2024-05-03 | 华青融天(北京)软件股份有限公司 | 分布式***中的指标追踪方法及装置 |
CN115757303A (zh) * | 2022-11-14 | 2023-03-07 | 华青融天(北京)软件股份有限公司 | 分布式***中的指标追踪方法及装置 |
CN116225880A (zh) * | 2023-05-05 | 2023-06-06 | 支付宝(杭州)信息技术有限公司 | 用于链路追踪的方法、装置及*** |
CN116225880B (zh) * | 2023-05-05 | 2023-09-08 | 支付宝(杭州)信息技术有限公司 | 用于链路追踪的方法、装置及*** |
CN116962407A (zh) * | 2023-07-31 | 2023-10-27 | 上海中汇亿达金融信息技术有限公司 | 分布式链路标签的处理方法,装置及应用 |
CN116962407B (zh) * | 2023-07-31 | 2024-02-13 | 上海中汇亿达金融信息技术有限公司 | 分布式链路标签的处理方法和装置、分布式链路追踪***及分布式*** |
CN116756044B (zh) * | 2023-08-11 | 2023-11-21 | 杭州罗莱迪思科技股份有限公司 | 一种基于数据链路追踪的rpc远程调试方法、装置及应用 |
CN116756044A (zh) * | 2023-08-11 | 2023-09-15 | 杭州罗莱迪思科技股份有限公司 | 一种基于数据链路追踪的rpc远程调试方法、装置及应用 |
CN117632445A (zh) * | 2024-01-25 | 2024-03-01 | 杭州阿里云飞天信息技术有限公司 | 请求处理方法以及装置、任务执行方法以及装置 |
CN117632445B (zh) * | 2024-01-25 | 2024-04-30 | 杭州阿里云飞天信息技术有限公司 | 请求处理方法以及装置、任务执行方法以及装置 |
CN117891749A (zh) * | 2024-03-18 | 2024-04-16 | 卓望数码技术(深圳)有限公司 | Api应用安全监测方法、装置、设备及存储介质 |
CN117891749B (zh) * | 2024-03-18 | 2024-06-04 | 卓望数码技术(深圳)有限公司 | Api应用安全监测方法、装置、设备及存储介质 |
CN117952041A (zh) * | 2024-03-26 | 2024-04-30 | 成都融见软件科技有限公司 | 基于驱动源码的x值追踪方法、电子设备和介质 |
CN117952041B (zh) * | 2024-03-26 | 2024-06-07 | 成都融见软件科技有限公司 | 基于驱动源码的x值追踪方法、电子设备和介质 |
Also Published As
Publication number | Publication date |
---|---|
CN112134739A (zh) | 2020-12-25 |
CN112134739B (zh) | 2022-07-08 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2021189899A1 (zh) | 链路状态的追踪方法、装置、电子设备及计算机存储介质 | |
WO2021189826A1 (zh) | 报文生成方法、装置、电子设备及计算机可读存储介质 | |
WO2021212757A1 (zh) | 集群的升级维护方法、装置、电子设备及存储介质 | |
CN112579098B (zh) | 软件发布方法、装置、电子设备及可读存储介质 | |
CN111950621A (zh) | 基于人工智能的目标数据检测方法、装置、设备及介质 | |
CN113806434A (zh) | 大数据处理方法、装置、设备及介质 | |
CN111694844A (zh) | 基于配置算法的企业运行数据分析方法、装置及电子设备 | |
WO2022179119A1 (zh) | 数据核对方法、装置、电子设备及可读存储介质 | |
CN113489704A (zh) | 基于流量的敏感数据识别方法、装置、电子设备及介质 | |
CN112580079A (zh) | 权限配置方法、装置、电子设备及可读存储介质 | |
CN111985545A (zh) | 基于人工智能的目标数据检测方法、装置、设备及介质 | |
CN113434542B (zh) | 数据关系识别方法、装置、电子设备及存储介质 | |
CN115129753A (zh) | 数据血缘关系分析方法、装置、电子设备及存储介质 | |
CN112104662B (zh) | 远端数据读写方法、装置、设备及计算机可读存储介质 | |
CN112486957A (zh) | 数据库迁移检测方法、装置、设备及存储介质 | |
CN112486532A (zh) | 配置文件的管理方法、装置、电子设备及存储介质 | |
CN115086047B (zh) | 接口鉴权方法、装置、电子设备及存储介质 | |
CN113849520B (zh) | 异常sql的智能识别方法、装置、电子设备及存储介质 | |
CN112925753B (zh) | 文件追加写入方法、装置、电子设备及存储介质 | |
CN112257078B (zh) | 一种基于tee技术的区块链加解密服务安全可信*** | |
CN115102770A (zh) | 基于用户权限的资源访问方法、装置、设备及存储介质 | |
CN115033605A (zh) | 数据查询方法、装置、电子设备及存储介质 | |
CN114185588A (zh) | 增量包生成方法、装置、设备及存储介质 | |
CN114036068A (zh) | 基于隐私安全的更新检测方法、装置、设备及存储介质 | |
CN112667244A (zh) | 数据校验方法、装置、电子设备及计算机可读存储介质 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 20927625 Country of ref document: EP Kind code of ref document: A1 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 20927625 Country of ref document: EP Kind code of ref document: A1 |