WO2020233015A1 - 一种链路跟踪方法及装置 - Google Patents
一种链路跟踪方法及装置 Download PDFInfo
- Publication number
- WO2020233015A1 WO2020233015A1 PCT/CN2019/117987 CN2019117987W WO2020233015A1 WO 2020233015 A1 WO2020233015 A1 WO 2020233015A1 CN 2019117987 W CN2019117987 W CN 2019117987W WO 2020233015 A1 WO2020233015 A1 WO 2020233015A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- target
- link information
- log
- link
- information
- Prior art date
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
- G06F11/079—Root cause analysis, i.e. error or fault diagnosis
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/18—File system types
- G06F16/1805—Append-only file systems, e.g. using logs or journals to store data
- G06F16/1815—Journaling file systems
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/22—Indexing; Data structures therefor; Storage structures
- G06F16/2282—Tablespace storage structures; Management thereof
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/24—Querying
- G06F16/245—Query processing
- G06F16/2455—Query execution
- G06F16/24553—Query execution of query operations
Definitions
- This application relates to the field of computer technology, and in particular to a link tracking method and device.
- microservices As a loosely coupled service-oriented architecture, microservices have received great attention in recent years. In practical applications, with the development of business, the number of microservices is increasing, and the calling relationship between services is becoming more and more complex. A request may be obtained through collaborative calls of multiple microservices to obtain results. Therefore, the overall situation The service link tracking is very necessary. Once a request fails a callback, the service tracking can be used to find the source of the error and modify it.
- the embodiment of the present application provides a microservice dependency analysis method and device, which can save server resources and improve the execution efficiency of dependency analysis.
- the embodiments of the present application provide a link tracking method and device, which can quickly locate the error source of a link abnormality, thereby improving the efficiency of link abnormality processing.
- One aspect of the embodiments of the present application provides a link tracking method, which includes:
- a link tracking device which includes:
- a link information acquisition module configured to acquire global link information and service identifiers, and generate a mapping relationship table between the service identifiers and each piece of link information in the global link information;
- the link information display module is configured to obtain a link query request, obtain target link information according to the link query request, and display the target link information on the link tracking display page;
- the log file obtaining module is configured to obtain a log switch instruction for the target link information, obtain the target service identifier corresponding to the target link information from the mapping relationship table according to the log switch instruction, and obtain the target service Identify the corresponding target log file, and switch and display the displayed target link information as the target log file.
- a link tracking device including: a processor and a memory
- the processor is connected to a memory, where the memory is used to store program code, and the processor is used to call the program code to execute the method in one aspect of the embodiments of the present application.
- Another aspect of the embodiments of the present application provides a computer non-volatile readable storage medium, the computer non-volatile readable storage medium stores a computer program, the computer program includes program instructions, and the program instructions are When executed by the processor, the method in one aspect of the embodiment of the present application is executed.
- the queried target link information can be displayed on the link tracking display page, but it can also be directly linked to the log file corresponding to the above target link information, which can quickly locate the root cause of the link abnormality. Thereby improving the efficiency of link exception handling.
- FIG. 1 is a schematic flowchart of a link tracking method provided by an embodiment of the present application
- FIG. 2 is a schematic flowchart of another link tracking method provided by an embodiment of the present application.
- FIG. 3 is a schematic structural diagram of a link tracking device provided by an embodiment of the present application.
- Fig. 4 is a schematic structural diagram of another link tracking device provided by an embodiment of the present application.
- Microservice architecture can refer to splitting the overall business into many services with specific and clear functions, and through the cooperation of many scattered small services, more complex problems can be solved.
- the microservice architecture most of the functional modules are deployed and run separately, interacting with each other through the bus, and they are all stateless services.
- the front and back business flows will be processed by multiple microservices.
- the user can only know the final processing result of the business flow, but cannot know the processing sequence of the business flow and the processing results of each microservice passed. If there is an error in the business flow And exceptions, you need to log in to each server to view the log files to find and locate the problem, which takes too much time, resulting in too low efficiency in finding and locating the problem.
- Link tracking can be recorded in the logical track of a specific request, that is, it can record all the work information completed by the system in the specific request.
- the logical track can include each service passed by the specific request and the time stamp of each service. The time spent on processing each service, and the performance of each service.
- the execution status of each of the above services can refer to whether the execution is successful, whether a retry is performed, and whether the execution failure has an impact on the entire request. Based on the above tracked information, the abnormal cause of the error in the service flow can be inquired and located.
- the method provided in this embodiment of the application can collect link information while collecting service-related data (service identification) during the link tracking process, and generate service identification and global link The mapping relationship table between each link information in the information.
- the target link information can be obtained from the above link information according to the parameter information in the link query request (for example, query service type parameters, query time range parameters), and then The tracking display page displays the obtained target link information. You can set a jump interface for the target link information on the link tracking display page, and you can obtain log switching for the target link information based on the jump interface.
- the target service identifier corresponding to the target link information can be obtained from the above-mentioned mapping relationship table, and the target log file corresponding to the above-mentioned target service identifier can be obtained from the log system, and it will be displayed on the above-mentioned link tracking display page
- the target link information is switched to display the target log file, that is, the link tracking display page can be directly associated with the target log file corresponding to the target link information, and the problem can be quickly inquired and located.
- FIG. 1 is a schematic flowchart of a link tracking method according to an embodiment of the present application. As shown in FIG. 1, the method provided in the embodiment of the present application will be described in detail below in conjunction with step S101 to step S103.
- S101 Obtain global link information and service identifiers, and generate a mapping relationship table between the service identifiers and each piece of link information in the global link information.
- the link tracking system can track the complete link call for each request, collect global link information and service identification, that is, collect link information on the complete link call corresponding to each request. And the service identifier, and generate a mapping relationship table between the above-mentioned service identifier and each piece of link information, so that the service identifier corresponding to the link information can be inquired from the above-mentioned mapping relationship table subsequently.
- the above-mentioned link information may include the start time of the call, the call type, the requested service name, the call time, the call result, the abnormal information, etc.
- the above-mentioned service identifier may be represented by numbers or other characters.
- the link tracking system can include four parts: data collection, data storage, data query, and data display.
- Zipkin link tracking system
- Zipkin can be used for link tracking.
- Zipkin is a distributed tracking system that can aggregate the call delay data of various business systems to achieve link call monitoring and tracking .
- Zipkin can collect data in a chronological order in the microservice architecture, and can manage the collected data and query useful data.
- Zipkin involves the following four components: collector (data collection), storage (data storage), search (data query) and UI (data display).
- collector can be used to receive link monitoring data transmitted by various applications
- storage can be used to Stores the link monitoring data received by the above collector, and supports In-Memory (stored in memory and stored in compressed columns), MySQL (relational database management system), Cassandra (hybrid non-relational database), ElasticSearch (The search server can provide a full-text search engine with distributed multi-user capabilities) 4 data storage methods, search can be used to query the data stored in storage, mainly for UI use, UI means it can provide a simple web interface for display search result.
- the collected link tracking data can be converted into Zipkin's general tracking data through transport and sent to Zipkin. Zipkin can verify the received link tracking data.
- Zipkin is configured with http (Hyper Text Transfer Protocol), kafka (high-throughput distributed publish-and-subscribe messaging system), and scribe (log collection system) three types of transport, that is, through the above http,
- the tracking data sent by the three types of kafka and scribe requests is the universal tracking data for Zipkin.
- the link tracking data received by the collector may include link information and service identification.
- the received link information and service The identifiers are all stored, and in the storage process, a mapping relationship table between a service identifier and each piece of link information can be generated, so as to distinguish the link information corresponding to different services.
- the service ID can be used to uniquely identify the service information, that is, the same service uses the same service ID.
- S102 Obtain a link query request, obtain target link information according to the link query request, and display the target link information on a link tracking display page.
- the link tracking system can provide a query function for the obtained link information.
- the link tracking system can obtain the link query request initiated by the user.
- the complete link information corresponding to the above-mentioned user request can be retrieved from the above-mentioned global link information, and the target link information with call abnormality can be determined.
- you can It is displayed on the display page of the link tracking system so that the user can locate the problem based on the above-mentioned target link information.
- a simple Application Program Interface can be provided for querying and retrieving link information.
- the query results can be displayed on Zipkin's link tracking display page UI on.
- the storage stores the link information of all call chains in the Zipkin tracking process.
- the target link information determined above is displayed on the UI interface.
- the query target link information is as follows: system A calls system B, system B calls system C, system C calls system D, then the link information on the UI interface can be displayed It is A ⁇ B ⁇ C ⁇ D.
- Zipkin's UI interface can also display the number of transactions per second (TPS) of the interface in a certain period of time, the average time, maximum time, minimum time and other information, which can be intuitively known.
- TPS transactions per second
- the utilization rate of each interface and the performance of the system can facilitate the operation and maintenance of monitoring server performance information.
- a corresponding link method can be added to the above target link information, so that the user can click the link to switch the interface, and the link tracking system can obtain the link based on the above link.
- the log switching instruction for the target link information generated by the method, based on the log switching instruction, the target service identifier corresponding to the target link information can be obtained from the mapping relationship table, and the target service identifier can be queried from the log system Corresponding target log file, and switch the target link information displayed on the link tracking display page to display the above target log file.
- the link tracking system can retrieve the target business identifier as a keyword in the log system, and display all log files in the log system that match the above target business identifier (ie target log files) on the above link tracking display page .
- a link method can be added to the above target link information on the UI interface, and the log for the above target link information can be obtained through the above link method.
- the switching instruction can enter the log system according to the log switching instruction, and the target service identifier corresponding to the target link information can be queried from the above mapping relationship table, and then all related to the target service identifier can be obtained from the log system Log files and display them on the UI interface.
- the embodiment of the application obtains the service identifier while obtaining the global link information, and generates a mapping relationship table between the service identifier and each link information in the global link information.
- a link query request is received, Obtain the target link information that matches the link query request from the above global link information, and display the above target link information on the link tracking display page, by obtaining the log switching instruction for the above target link information, Obtain the target service identifier corresponding to the target link information from the above mapping relationship table, and then obtain the target log file corresponding to the target service identifier from the log system, and display the target link on the link tracking display page.
- the information is switched to display the above target log file.
- the queried target link information can be displayed on the link tracking display page, but it can also be directly linked to the log file corresponding to the above target link information, which can quickly locate the source of the link abnormal error. , Thereby improving the efficiency of link exception handling.
- FIG. 2 is a schematic flowchart of another link tracking method provided by an embodiment of the present application. As shown in FIG. 2, the method provided in the embodiment of the present application will be described in detail below in conjunction with step S201-step S209.
- S201 Obtain global link information and service identifiers, and generate a mapping relationship table between the service identifiers and each piece of link information in the global link information.
- step S201 For the specific implementation of the foregoing step S201, reference may be made to the description of step S101 in the embodiment corresponding to FIG. 1, which will not be repeated here.
- S202 Obtain a link query request, and obtain a query service type parameter and a query time range parameter in the link query request.
- the link tracking system can extract the query service type parameter and query time range parameter from the link query request.
- the above query service type parameter can be used to indicate the service type corresponding to the above user request
- the above query time range parameter can be used to indicate the time range of the above user request, because the link information can include the timestamp of each service.
- the processing time of each service and other information, so the target time range for querying link information can be determined through the above query time range parameter.
- S203 Obtain link information to be detected that matches the query service type parameter and the query time range parameter from the global link information, and obtain a target tag of the link information to be detected.
- the link information to be detected that matches the user request can be obtained from the global link information according to the above query service type parameter and the above time range parameter.
- Information for the above link information to be detected, the link tracking system can mark differently according to the link information, for example, use different colors for marking, black can be used to indicate the normal link information is called, and red can be used to Indicates the link information of the abnormal call.
- S204 Determine the link information to be detected whose target is marked as an abnormal mark as target link information, and display the target link information on the link tracking display page.
- the part of the link information marked as an abnormal mark in the link information to be detected is determined as the target link information, and the target link information is displayed on the link tracking interface.
- red is used as the abnormal link information.
- the link information to be detected is: A system calls B system, B system calls C system, C system calls D system, D system calls again The E system and the F system, where the link information that calls the link C ⁇ D ⁇ F is marked in red, and the link C ⁇ D ⁇ F is determined as the target link information.
- the above-mentioned link tracking display page can provide corresponding log switch buttons for the above-mentioned target link information while displaying the above-mentioned target link information.
- the user can click the above-mentioned log switch button to issue a touch Signal, when the link tracking system obtains the touch signal, it can generate the click instruction corresponding to the log switch button according to the touch signal.
- the above log switch button can be expressed as a link mode to realize the jump of the display content on the link tracking display page.
- S206 Generate a log switch instruction for the target link information according to the click instruction, and obtain a target service identifier corresponding to the target link information from the mapping table according to the log switch instruction.
- the log switch instruction corresponding to the target link information can be generated according to the click instruction, that is, the instruction to jump the displayed target link information to the log file on the link tracking display page,
- the log switching instruction may include relevant content of the target link information, and the target service identifier of the target link information may be obtained from the above-mentioned mapping relationship table.
- a jump interface can be set for the target link information on the link tracking display page.
- the jump interface is triggered according to the touch signal.
- the target link information can be used as a link method, that is, the user can send a touch signal by clicking on the target link information, and the link tracking system can obtain the touch signal to generate a log Switching instructions, so that the target service identifier of the target link information can be obtained from the above mapping relationship table.
- S207 Obtain at least one log server to which the target service identifier belongs from the log system, as the at least one target log server.
- each call chain will go through multiple services, so log files will be generated on the server corresponding to each service. It can also be understood that each business will go through multiple services.
- the log corresponding to the above business The files will be scattered on multiple independent servers. Multiple servers with scattered log files corresponding to the target service identifiers can be used as target log servers from the log system.
- the above-mentioned target log server can be determined by the above-mentioned target business identifier. After entering the log system, the target business identifier can be used as a key to query all log files. If the business identifier in the log file is the same as the above-mentioned target business identifier , The server where the above log file is located is determined as the target log server. For example, if the target business ID is 1, the keyword "Business ID 1" is used to match the business ID recorded in the log file. If the same value is 1, it means the match is successful and the key "Business ID 1" will be included. The server where the word log is located is determined as the target log server.
- S208 Acquire multiple log files corresponding to the target service identifier from the target log server.
- multiple log files matching the target service identifier on all the target log servers can be obtained, that is, the location and content of all log files corresponding to the target service identifier can be determined.
- S209 Encapsulate the multiple obtained log files into a target log file, and switch and display the displayed target link information as the target log file.
- the multiple log files obtained above can be summarized, all the logs are sorted according to the time sequence of the business flow, stored in one file, and packaged into a target log file, and the above The target link information displayed on the link tracking display page is switched and displayed as the log information in the target log file.
- the log can be analyzed to quickly query and locate the problem. You can clearly know the proportion of each call segment to the entire call segment. You can determine the abnormal link. For example, in the log file displayed on the above link tracking display page, if a certain call segment accounts for too much time in the entire call segment, it can be determined that the link corresponding to the call segment is a problem link or a timeout link. So as to solve the problem quickly and accurately.
- the embodiment of the application collects service-related data (service identification) while collecting link information in the process of link tracking, and generates a mapping relationship table between the service identification and each link information in the global link information .
- the target link information can be obtained from the above link information according to the parameter information in the link query request (for example, query service type parameters, query time range parameters), and then The obtained target link information is displayed on the tracking display page, a link can be added to the target link information on the link tracking display page, and the log switching instruction for the target link information can be obtained based on the link, and then Obtain the target service identifier corresponding to the target link information from the above mapping relationship table, and then obtain the target log file corresponding to the target service identifier from the log system, and display the target chain on the link tracking display page.
- the parameter information in the link query request for example, query service type parameters, query time range parameters
- the path information is switched to display the above target log file.
- the queried target link information can be displayed on the link tracking display page, but it can also be directly linked to the log file corresponding to the above target link information, which can quickly locate the source of the link abnormal error. , Thereby improving the efficiency of link exception handling.
- the link tracking device 1 may include: a link information acquisition module 10, a link information display module 20, and a log file acquisition module 30;
- the link information obtaining module 10 is configured to obtain global link information and service identifiers, and generate a mapping relationship table between the service identifiers and each piece of link information in the global link information;
- the link information display module 20 is configured to obtain a link query request, obtain target link information according to the link query request, and display the target link information on the link tracking display page;
- the log file obtaining module 30 is configured to obtain a log switching instruction for the target link information, obtain the target service identifier corresponding to the target link information from the mapping relationship table according to the log switching instruction, and obtain the target The target log file corresponding to the service identification, and switching and displaying the displayed target link information as the target log file.
- link information acquisition module 10 the link information display module 20, and the log file acquisition module 30 can be found in step S101 to step S103 in the embodiment corresponding to FIG. 1, which will not be repeated here.
- the above-mentioned link information display module 20 may include: a first obtaining unit 201, a second obtaining unit 202, and a determining unit 203;
- the first obtaining unit 201 is configured to obtain the query service type parameter and the query time range parameter in the link query request;
- the second obtaining unit 202 is configured to obtain the link information to be detected that matches the query service type parameter and the query time range parameter from the global link information, and obtain the target mark of the link information to be detected ;
- the determining unit 203 is configured to determine the link information to be detected whose target is marked as an abnormal mark as target link information.
- step S202 For specific functional implementations of the first acquiring unit 201, the second acquiring unit 202, and the determining unit 203, refer to step S202 to step S204 in the embodiment corresponding to FIG. 2 above, and details are not described herein again.
- the aforementioned log file acquisition module 30 may include: a first instruction generating unit 301, a second instruction generating unit 302, a setting unit 303, a third instruction generating unit 304, a third acquiring unit 305, and a fourth acquiring Unit 306, packaging unit 307;
- the first instruction generating unit 301 is configured to generate a click instruction corresponding to the log switch button according to the touch signal when the touch signal of the screen position where the log switch button is located is acquired;
- the second instruction generating unit 302 is configured to generate a log switching instruction for the target link information according to the click instruction
- the setting unit 303 is configured to set a jump interface for the target link information
- the third instruction generating unit 304 is configured to trigger the jump interface to generate the log switch instruction according to the touch signal when the touch signal of the screen position where the target link information is obtained;
- the third obtaining unit 305 is configured to obtain at least one log server to which the target service identifier belongs from the log system as the at least one target log server;
- the fourth obtaining unit 306 is configured to obtain multiple log files corresponding to the target service identifier from the target log server;
- the encapsulation unit 307 is configured to encapsulate the multiple obtained log files into a target log file, and switch and display the displayed target link information as the target log file.
- the specific function implementation of the first instruction generating unit 301, the second instruction generating unit 302, the setting unit 303, the third instruction generating unit 304, the third obtaining unit 305, the fourth obtaining unit 306, and the packaging unit 307 can be found in Steps S205 to S209 in the embodiment corresponding to FIG. 2 are not repeated here.
- the setting unit 303 and the third instruction generating unit 304 both suspend the execution of operations.
- the first instruction generating unit 301 and the second instruction generating unit 302 both suspend the execution of the operations.
- the embodiment of the application collects service-related data (service identification) while collecting link information in the process of link tracking, and generates a mapping relationship table between the service identification and each link information in the global link information .
- the target link information can be obtained from the above link information according to the parameter information in the link query request (for example, query service type parameters, query time range parameters), and then The obtained target link information is displayed on the tracking display page, a link can be added to the target link information on the link tracking display page, and the log switching instruction for the target link information can be obtained based on the link, and then Obtain the target service identifier corresponding to the target link information from the above mapping relationship table, and then obtain the target log file corresponding to the target service identifier from the log system, and display the target chain on the link tracking display page.
- the parameter information in the link query request for example, query service type parameters, query time range parameters
- the path information is switched to display the above target log file.
- the queried target link information can be displayed on the link tracking display page, but it can also be directly linked to the log file corresponding to the above target link information, which can quickly locate the source of the link abnormal error. , Thereby improving the efficiency of link exception handling.
- FIG. 4 is a schematic structural diagram of another link tracking device provided by an embodiment of the present application.
- the link tracking apparatus 500 in the embodiment of the present application may include: one or more processors 501 and a memory 502.
- the aforementioned processor 501 and memory 502 are connected through a bus 503.
- the memory 502 is used to store a computer program, and the computer program includes program instructions.
- the processor 501 is used to execute the program instructions stored in the memory 502, and can be used for:
- processor 501 executes the foregoing acquisition of target link information according to the link query request, it is specifically configured to:
- the link information to be detected whose target is marked as an abnormal mark is determined as target link information.
- the aforementioned processor 501 executes the aforementioned log switching instruction for acquiring the target link information, it is specifically configured to:
- a log switching instruction for the target link information is generated.
- the aforementioned processor 501 is specifically configured to: when executing the aforementioned log switching instruction for acquiring the target link information:
- the jump interface is triggered according to the touch signal to generate the log switching instruction.
- the processor 501 executes the foregoing acquisition of the target log file corresponding to the target service identifier, and switches and displays the displayed target link information as the target log file, it specifically uses in:
- the above-mentioned processor 501 may be a central processing unit (central processing unit, CPU), and the processor may also be other general-purpose processors, digital signal processors (digital signal processors, DSP), and dedicated integration Circuit (application specific integrated circuit, ASIC), ready-made programmable gate array (field-programmable gate array, FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components, etc.
- the general-purpose processor may be a microprocessor or the processor may also be any conventional processor or the like.
- the memory 502 may include a read-only memory and a random access memory, and provides instructions and data to the processor 501.
- a part of the memory 502 may also include a non-volatile random access memory.
- the memory 502 may also store device type information.
- link tracking device 500 can perform the description of the link tracking method in the foregoing embodiment corresponding to FIG. 1 and FIG. 2 and the description of the link tracking device in the embodiment corresponding to FIG. 3, here Do not repeat it.
- the embodiment of the application obtains the service identifier while obtaining the global link information, and generates a mapping relationship table between the service identifier and each link information in the global link information.
- a link query request is received, Obtain the target link information that matches the link query request from the above global link information, and display the above target link information on the link tracking display page, by obtaining the log switching instruction for the above target link information, Obtain the target service identifier corresponding to the target link information from the above mapping relationship table, and then obtain the target log file corresponding to the target service identifier from the log system, and display the target link on the link tracking display page.
- the information is switched to display the above target log file.
- the queried target link information can be displayed on the link tracking display page, but it can also be directly linked to the log file corresponding to the above target link information, which can quickly locate the source of the link abnormal error. , Thereby improving the efficiency of link exception handling.
- the embodiment of the present application also provides a computer non-volatile readable storage medium, and the aforementioned computer non-volatile readable storage medium stores the aforementioned link tracking device 1
- the executed computer program, and the above-mentioned computer program includes program instructions.
- the processor executes the above-mentioned program instructions, it can execute the description of the above-mentioned link tracking method in the embodiment corresponding to FIG. 2 above. Therefore, it will not be repeated here. .
- the description of the beneficial effects of using the same method will not be repeated.
- For technical details not disclosed in the embodiments of the computer non-volatile readable storage medium involved in this application please refer to the description of the method embodiments of this application.
- computer program instructions can implement each process and/or schematic structural diagrams of the method Or a block, and a combination of processes and/or blocks in a flowchart and/or block diagram.
- These computer program instructions can be provided to the processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing equipment to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing equipment are generated for use. It is a device that realizes the functions specified in one or more processes in the flowchart and/or one block or more in the schematic structural diagram.
- These computer program instructions can also be stored in a computer-readable memory that can guide a computer or other programmable data processing equipment to work in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture including the instruction device.
- the device implements the functions specified in one process or multiple processes in the flowchart and/or one block or multiple blocks in the schematic structural diagram.
- These computer program instructions can also be loaded on a computer or other programmable data processing equipment, so that a series of operation steps are executed on the computer or other programmable equipment to produce computer-implemented processing, so as to execute on the computer or other programmable equipment.
- the instructions provide steps for implementing the functions specified in one block or multiple blocks in the flow chart or the flow chart and/or the structure.
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Physics & Mathematics (AREA)
- Databases & Information Systems (AREA)
- Data Mining & Analysis (AREA)
- Computational Linguistics (AREA)
- Health & Medical Sciences (AREA)
- Biomedical Technology (AREA)
- Quality & Reliability (AREA)
- Software Systems (AREA)
- Debugging And Monitoring (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
- User Interface Of Digital Computer (AREA)
Abstract
Description
Claims (20)
- 一种链路跟踪方法,其特征在于,包括:获取全局链路信息与业务标识,生成所述业务标识与所述全局链路信息中的每条链路信息之间的映射关系表;获取链路查询请求,根据所述链路查询请求获取目标链路信息,并在链路跟踪展示页面显示所述目标链路信息;获取针对所述目标链路信息的日志切换指令,根据所述日志切换指令从所述映射关系表获取所述目标链路信息对应的目标业务标识,获取所述目标业务标识对应的目标日志文件,并将所显示的所述目标链路信息切换显示为所述目标日志文件。
- 根据权利要求1所述的方法,其特征在于,所述根据所述链路查询请求获取目标链路信息,包括:获取所述链路查询请求中的查询业务类型参数、查询时间范围参数;从全局链路信息中获取与所述查询业务类型参数、所述查询时间范围参数相匹配的待检测链路信息,并获取所述待检测链路信息的目标标记;将目标标记为异常标记的待检测链路信息确定为目标链路信息。
- 根据权利要求1所述的方法,其特征在于,所述获取针对所述目标链路信息的日志切换指令,包括:当获取到日志切换按键所在屏幕位置的触控信号时,根据所述触控信号生成所述日志切换按键对应的点击指令;根据所述点击指令,生成针对所述目标链路信息的日志切换指令。
- 根据权利要求1所述的方法,其特征在于,所述获取针对所述目标链路信息的日志切换指令,包括:为所述目标链路信息设置跳转接口;当获取到所述目标链路信息所在屏幕位置的触控信号时,根据所述触控信号触发所述跳转接口生成所述日志切换指令。
- 根据权利要求1所述的方法,其特征在于,所述获取所述目标业务标识对应的目标日志文件,并将所显示的所述目标链路信息切换显示为所述目标日志文件,包括:从所述日志系统中获取所述目标业务标识所属的至少一个日志服务器,作为至少一个目标日志服务器;从所述目标日志服务器中获取所述目标业务标识对应的多个日志文件;将获取到的所述多个日志文件封装成目标日志文件,并将所显示的所述目 标链路信息切换显示为所述目标日志文件。
- 根据权利要求5所述的方法,其特征在于,所述从所述日志系统中获取所述目标业务标识所属的至少一个日志服务器,作为至少一个目标日志服务器,包括:基于所述目标业务标识,对所述日志系统中所包含的所有日志文件进行查询;将所述日志系统中携带所述目标业务标识的日志文件所属的日志服务器,作为目标日志服务器。
- 根据权利要求5所述的方法,其特征在于,所述将获取到的所述多个日志文件封装成目标日志文件,并将所显示的所述目标链路信息切换显示为所述目标日志文件,包括:获取所述多个日志文件分别对应的业务时间信息;读取所述多个日志文件中所包含的日志内容,并基于所述业务时间信息,对所述日志内容进行排序,将排序后的日志内容封装成目标日志文件;将所述链路跟踪展示页面中,所显示的所述目标链路信息切换显示为所述目标日志文件。
- 根据权利要求1所述的方法,其特征在于,所述获取全局链路信息与业务标识,生成所述业务标识与所述全局链路信息中的每条链路信息之间的映射关系表,包括:采集原始链路信息,所述原始链路信息包括调用起始时间、调用类型、请求的服务名、调用耗时、调用结果以及异常信息;对所述原始链路信息进行数据有效性验证,将验证成功的原始链路信息确定为全局链路信息;获取与所述全局链路信息相关联的业务标识,生成所述业务标识与所述全局链路信息中的每条链路信息之间的映射关系表。
- 根据权利要求1所述的方法,其特征在于,还包括:统计目标时间范围内的每秒响应请求事务数和耗时信息;所述耗时信息包括平均耗时、最小耗时以及最小耗时;在所述链路跟踪展示页面中显示所述每秒响应请求事务数和所述耗时信息。
- 一种链路跟踪装置,其特征在于,包括:链路信息获取模块,用于获取全局链路信息与业务标识,生成所述业务标识与所述全局链路信息中的每条链路信息之间的映射关系表;链路信息显示模块,用于获取链路查询请求,根据所述链路查询请求获取 目标链路信息,并在链路跟踪展示页面显示所述目标链路信息;日志文件获取模块,用于获取针对所述目标链路信息的日志切换指令,根据所述日志切换指令从所述映射关系表获取所述目标链路信息对应的目标业务标识,获取所述目标业务标识对应的目标日志文件,并将所显示的所述目标链路信息切换显示为所述目标日志文件。
- 根据权利要求10所述的装置,其特征在于,所述链路信息显示模块包括:第一获取单元,用于获取所述链路查询请求中的查询业务类型参数、查询时间范围参数;第二获取单元,用于从全局链路信息中获取与所述查询业务类型参数、所述查询时间范围参数相匹配的待检测链路信息,并获取所述待检测链路信息的目标标记;确定单元,用于将目标标记为异常标记的待检测链路信息确定为目标链路信息。
- 根据权利要求10所述的装置,其特征在于,所述日志文件获取模块包括:第一指令生成单元,用于当获取到日志切换按键所在屏幕位置的触控信号时,根据所述触控信号生成所述日志切换按键对应的点击指令;第二指令生成单元,用于根据所述点击指令,生成针对所述目标链路信息的日志切换指令。
- 根据权利要求10所述的装置,其特征在于,所述日志文件获取模块包括:设置单元,用于为所述目标链路信息设置跳转接口;第三指令生成单元,用于当获取到所述目标链路信息所在屏幕位置的触控信号时,根据所述触控信号触发所述跳转接口生成所述日志切换指令。
- 根据权利要求10所述的装置,其特征在于,所述日志文件获取模块包括:第三获取单元,用于从所述日志系统中获取所述目标业务标识所属的至少一个日志服务器,作为至少一个目标日志服务器;第四获取单元,用于从所述目标日志服务器中获取所述目标业务标识对应的多个日志文件;封装单元,用于将获取到的所述多个日志文件封装成目标日志文件,并将所显示的所述目标链路信息切换显示为所述目标日志文件。
- 根据权利要求14所述的装置,其特征在于,所述第三获取单元包括:查询子单元,用于基于所述目标业务标识,对所述日志系统中所包含的所有日志文件进行查询;日志服务器确定子单元,用于将所述日志系统中携带所述目标业务标识的日志文件所属的日志服务器,作为目标日志服务器。
- 根据权利要求14所述的装置,其特征在于,所述封装单元包括:时间获取子单元,用于获取所述多个日志文件分别对应的业务时间信息;排序子单元,用于读取所述多个日志文件中所包含的日志内容,并基于所述业务时间信息,对所述日志内容进行排序,将排序后的日志内容封装成目标日志文件;切换显示子单元,用于将所述链路跟踪展示页面中,所显示的所述目标链路信息切换显示为所述目标日志文件。
- 根据权利要求10所述的装置,其特征在于,所述链路信息获取模块包括:采集单元,用于采集原始链路信息,所述原始链路信息包括调用起始时间、调用类型、请求的服务名、调用耗时、调用结果以及异常信息;验证单元,用于对所述原始链路信息进行数据有效性验证,将验证成功的原始链路信息确定为全局链路信息;关系表生成单元,用于获取与所述全局链路信息相关联的业务标识,生成所述业务标识与所述全局链路信息中的每条链路信息之间的映射关系表。
- 根据权利要求10所述的装置,其特征在于,还包括:统计模块,用于统计目标时间范围内的每秒响应请求事务数和耗时信息;所述耗时信息包括平均耗时、最小耗时以及最小耗时;所述链路信息显示模块,还用于在所述链路跟踪展示页面中显示所述每秒响应请求事务数和所述耗时信息。
- 一种链路跟踪装置,其特征在于,包括:处理器和存储器;所述处理器和存储器相连,其中,所述存储器用于存储程序代码,所述处理器用于调用所述程序代码,以执行如权利要求1-9任一项所述的方法。
- 一种计算机非易失性可读存储介质,其特征在于,所述计算机非易失性可读存储介质存储有计算机程序,所述计算机程序包括程序指令,所述程序指令当被处理器执行时,执行如权利要求1-9任一项所述的方法。
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201910420483.3A CN110245035A (zh) | 2019-05-20 | 2019-05-20 | 一种链路跟踪方法及装置 |
CN201910420483.3 | 2019-05-20 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2020233015A1 true WO2020233015A1 (zh) | 2020-11-26 |
Family
ID=67884635
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2019/117987 WO2020233015A1 (zh) | 2019-05-20 | 2019-11-13 | 一种链路跟踪方法及装置 |
Country Status (2)
Country | Link |
---|---|
CN (1) | CN110245035A (zh) |
WO (1) | WO2020233015A1 (zh) |
Cited By (25)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN112506799A (zh) * | 2020-12-22 | 2021-03-16 | 北京百度网讯科技有限公司 | 业务异常定位方法及装置、电子设备、介质、产品 |
CN112579457A (zh) * | 2020-12-24 | 2021-03-30 | 北京志翔能源技术有限公司 | 基于人工智能的数据架构管控方法及系统 |
CN112817847A (zh) * | 2021-01-28 | 2021-05-18 | 杭州网易再顾科技有限公司 | 数据处理任务的测试方法、装置、电子设备及存储介质 |
CN113094166A (zh) * | 2021-05-10 | 2021-07-09 | 杭州网易云音乐科技有限公司 | 一种链路追踪方法、装置、介质和计算设备 |
CN113157570A (zh) * | 2021-04-07 | 2021-07-23 | 腾讯音乐娱乐科技(深圳)有限公司 | 确定触发主体信息的方法、设备及存储介质 |
CN113282465A (zh) * | 2021-06-17 | 2021-08-20 | 中国建设银行股份有限公司 | 一种故障定位方法、装置、电子设备及计算机存储介质 |
CN113468159A (zh) * | 2021-07-19 | 2021-10-01 | 广东电网有限责任公司 | 一种数据应用全链路管控方法及系统 |
CN113485891A (zh) * | 2021-06-30 | 2021-10-08 | 中国民航信息网络股份有限公司 | 业务日志监控方法、装置、存储介质及电子设备 |
CN113641554A (zh) * | 2021-08-10 | 2021-11-12 | 南威软件股份有限公司 | 一种跨接口链路监控方法 |
CN113760728A (zh) * | 2021-01-22 | 2021-12-07 | 北京沃东天骏信息技术有限公司 | 应用测试的方法和装置 |
CN113806360A (zh) * | 2021-08-12 | 2021-12-17 | 浙江吉利控股集团有限公司 | 一种派单链路故障确定方法、装置、设备及存储介质 |
CN113867913A (zh) * | 2021-09-27 | 2021-12-31 | 平安国际智慧城市科技股份有限公司 | 面向微服务的业务请求处理方法、装置、设备及存储介质 |
CN114153712A (zh) * | 2021-11-22 | 2022-03-08 | 深圳市晨北科技有限公司 | 异常处理方法、装置、设备及存储介质 |
CN114443337A (zh) * | 2022-01-27 | 2022-05-06 | 苏州浪潮智能科技有限公司 | 一种基于js的日志分析方法、装置、电子设备和介质 |
CN114598622A (zh) * | 2022-03-10 | 2022-06-07 | 平安科技(深圳)有限公司 | 数据监控方法及装置、存储介质、计算机设备 |
CN114866535A (zh) * | 2022-05-30 | 2022-08-05 | 广州简悦信息科技有限公司 | 应用的投放下载方法及装置 |
CN116016646A (zh) * | 2022-11-07 | 2023-04-25 | 中国工商银行股份有限公司 | 业务访问控制方法、装置、设备及介质 |
CN116112397A (zh) * | 2022-11-17 | 2023-05-12 | 中国邮政储蓄银行股份有限公司 | 延时异常的确定方法、确定装置与云平台 |
CN116192621A (zh) * | 2022-12-27 | 2023-05-30 | 上海轻维软件有限公司 | 基于Opentracing链路追踪业务调用链的方法 |
CN116775440A (zh) * | 2023-08-21 | 2023-09-19 | 青岛民航凯亚系统集成有限公司 | 一种基于机场生产运营系统的日志级链路追踪方法及系统 |
CN116882724A (zh) * | 2023-07-13 | 2023-10-13 | 北京优特捷信息技术有限公司 | 一种业务流程优化方案的生成方法、装置、设备及介质 |
CN117176802A (zh) * | 2023-11-02 | 2023-12-05 | 太平金融科技服务(上海)有限公司 | 一种业务请求的全链路监控方法、装置、电子设备及介质 |
CN117215964A (zh) * | 2023-11-09 | 2023-12-12 | 中央军委政治工作部军事人力资源保障中心 | 一种业务系统的程序异常观测方法和装置 |
CN113761406B (zh) * | 2021-09-03 | 2024-06-04 | 丰巢网络技术有限公司 | 一种智能柜二维码短链生成方法、装置、介质及电子设备 |
CN118227200A (zh) * | 2024-05-24 | 2024-06-21 | 华能信息技术有限公司 | 一种多链路追踪方法 |
Families Citing this family (37)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN110245035A (zh) * | 2019-05-20 | 2019-09-17 | 平安普惠企业管理有限公司 | 一种链路跟踪方法及装置 |
CN110751444B (zh) * | 2019-10-25 | 2022-05-27 | 拉扎斯网络科技(上海)有限公司 | 数据处理方法、装置、计算机系统及可读存储介质 |
CN110855477A (zh) * | 2019-10-29 | 2020-02-28 | 浙江大搜车软件技术有限公司 | 链路日志监控方法、装置、计算机设备和存储介质 |
CN111143304B (zh) * | 2019-11-20 | 2023-09-29 | 杭州端点网络科技有限公司 | 一种基于请求链路的微服务系统异常日志分析方法 |
CN111078342A (zh) * | 2019-12-06 | 2020-04-28 | 拉扎斯网络科技(上海)有限公司 | 信息展示方法、装置、电子设备及计算机可读存储介质 |
CN113132143B (zh) * | 2019-12-31 | 2023-04-07 | 深圳云天励飞技术有限公司 | 服务调用追踪方法及相关产品 |
CN111159590A (zh) * | 2019-12-31 | 2020-05-15 | 亚信科技(中国)有限公司 | 一种基于前后端业务调用链路的串联方法及装置 |
CN111241125B (zh) * | 2020-01-08 | 2023-06-02 | 北京数培通网络科技有限公司 | 一种记录操作日志的方法、装置、电子设备和存储介质 |
CN111352902A (zh) * | 2020-02-28 | 2020-06-30 | 中国平安人寿保险股份有限公司 | 日志处理方法、装置、终端设备及存储介质 |
CN113448936A (zh) * | 2020-03-25 | 2021-09-28 | 阿里巴巴集团控股有限公司 | 一种日志跟踪方法、装置、服务器、系统及存储介质 |
CN111724158B (zh) * | 2020-05-25 | 2024-03-26 | 中国建设银行股份有限公司 | 交易路径生成方法、系统及相关计算机设备和存储介质 |
CN113746883B (zh) * | 2020-05-29 | 2023-05-19 | 华为技术有限公司 | 链路跟踪方法及系统 |
CN111752799B (zh) * | 2020-06-24 | 2024-08-06 | 中国建设银行股份有限公司 | 一种业务链路跟踪方法、装置、设备及储存介质 |
CN111899105A (zh) * | 2020-08-04 | 2020-11-06 | 深圳乐信软件技术有限公司 | 系统异常处理方法、装置、计算机设备及存储介质 |
CN112134739B (zh) * | 2020-09-24 | 2022-07-08 | 平安科技(深圳)有限公司 | 链路状态的追踪方法、装置、电子设备及计算机存储介质 |
CN112256658B (zh) * | 2020-10-16 | 2023-08-18 | 海尔优家智能科技(北京)有限公司 | 日志记录的分流方法及装置、存储介质、电子装置 |
CN113761015B (zh) * | 2020-10-22 | 2023-09-05 | 北京京东振世信息技术有限公司 | 一种日志处理方法、装置、系统及存储介质 |
CN112311811B (zh) * | 2020-11-16 | 2022-10-18 | 深圳市欢太科技有限公司 | 全链路跟踪方法、装置、存储介质以及服务器 |
CN113762910B (zh) * | 2020-11-27 | 2024-04-16 | 北京京东振世信息技术有限公司 | 一种单据监控方法和装置 |
CN112910945B (zh) * | 2020-12-08 | 2023-06-30 | 江苏苏宁云计算有限公司 | 请求链路跟踪方法和业务请求处理方法 |
CN112597016A (zh) * | 2020-12-17 | 2021-04-02 | 平安普惠企业管理有限公司 | 自动化测试脚本的录制方法、装置、设备及存储介质 |
CN115997410A (zh) * | 2020-12-18 | 2023-04-21 | Oppo广东移动通信有限公司 | 无线通信方法、终端设备和网络设备 |
CN112861053A (zh) * | 2021-01-18 | 2021-05-28 | 北京致远互联软件股份有限公司 | 一种任务系统调用链路的表单跟踪系统 |
CN112783629A (zh) * | 2021-02-01 | 2021-05-11 | 天津五八到家货运服务有限公司 | 服务调用方法、装置、电子设备及存储介质 |
CN115017148A (zh) * | 2021-03-08 | 2022-09-06 | 杭州云掣科技有限公司 | 一种统一高效的运维数据存储检索分析的方法与系统 |
CN112882994A (zh) * | 2021-03-30 | 2021-06-01 | 中信银行股份有限公司 | 一种日志提取方法和装置 |
CN113342767A (zh) * | 2021-04-28 | 2021-09-03 | 招银云创信息技术有限公司 | 一种日志生成方法、装置、设备及存储介质 |
CN113392893B (zh) * | 2021-06-08 | 2024-08-13 | 北京达佳互联信息技术有限公司 | 业务故障的定位方法、装置、存储介质及计算机程序产品 |
CN113268363B (zh) * | 2021-06-16 | 2024-04-09 | 中移(杭州)信息技术有限公司 | 基于全局能力的调用追踪方法、装置、服务器及存储介质 |
CN113596078B (zh) * | 2021-06-17 | 2024-08-02 | 微梦创科网络科技(中国)有限公司 | 业务问题定位方法及装置 |
CN113760652B (zh) * | 2021-08-13 | 2023-12-26 | 济南浪潮数据技术有限公司 | 基于应用的全链路监控的方法、系统、设备和存储介质 |
CN113778736A (zh) * | 2021-09-14 | 2021-12-10 | 北京房江湖科技有限公司 | 错误信息的定位方法和装置 |
CN113918426A (zh) * | 2021-12-09 | 2022-01-11 | 山东宁泓信息技术有限公司 | 一种实现Redis访问全链路跟踪的方法、系统及设备 |
CN114003472B (zh) * | 2022-01-04 | 2022-04-12 | 连连(杭州)信息技术有限公司 | 一种数据处理方法、装置、电子设备及存储介质 |
CN114584621B (zh) * | 2022-04-18 | 2024-06-07 | 中国农业银行股份有限公司 | 一种数据发送的方法及装置 |
CN114866606A (zh) * | 2022-04-21 | 2022-08-05 | 彩讯科技股份有限公司 | 一种微服务管理系统 |
CN115412592B (zh) * | 2022-08-19 | 2023-08-22 | 恒生电子股份有限公司 | 业务处理系统以及方法 |
Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN106933724A (zh) * | 2017-03-16 | 2017-07-07 | 北京搜狐新媒体信息技术有限公司 | 一种分布式信息追踪系统、信息处理方法及装置 |
CN106980627A (zh) * | 2016-01-18 | 2017-07-25 | 中兴通讯股份有限公司 | 日志内容的显示方法及装置 |
US20180075240A1 (en) * | 2015-03-20 | 2018-03-15 | Alibaba Group Holding Limited | Method and device for detecting a suspicious process by analyzing data flow characteristics of a computing device |
CN108228432A (zh) * | 2016-12-12 | 2018-06-29 | 阿里巴巴集团控股有限公司 | 一种分布式链路跟踪、分析方法及服务器、全局调度器 |
CN110245035A (zh) * | 2019-05-20 | 2019-09-17 | 平安普惠企业管理有限公司 | 一种链路跟踪方法及装置 |
Family Cites Families (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101137160B (zh) * | 2006-09-01 | 2010-04-21 | 华为技术有限公司 | 检测跟踪状态的方法和系统及跟踪代理、跟踪控制服务器 |
CN108228322B (zh) * | 2016-12-12 | 2022-03-25 | 阿里巴巴集团控股有限公司 | 一种分布式链路跟踪、分析方法及服务器、全局调度器 |
CN106790718A (zh) * | 2017-03-16 | 2017-05-31 | 北京搜狐新媒体信息技术有限公司 | 服务调用链路分析方法及系统 |
CN109359094B (zh) * | 2018-08-03 | 2021-04-16 | 挖财网络技术有限公司 | 一种分布式系统日志全链路追踪方法及装置 |
-
2019
- 2019-05-20 CN CN201910420483.3A patent/CN110245035A/zh active Pending
- 2019-11-13 WO PCT/CN2019/117987 patent/WO2020233015A1/zh active Application Filing
Patent Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20180075240A1 (en) * | 2015-03-20 | 2018-03-15 | Alibaba Group Holding Limited | Method and device for detecting a suspicious process by analyzing data flow characteristics of a computing device |
CN106980627A (zh) * | 2016-01-18 | 2017-07-25 | 中兴通讯股份有限公司 | 日志内容的显示方法及装置 |
CN108228432A (zh) * | 2016-12-12 | 2018-06-29 | 阿里巴巴集团控股有限公司 | 一种分布式链路跟踪、分析方法及服务器、全局调度器 |
CN106933724A (zh) * | 2017-03-16 | 2017-07-07 | 北京搜狐新媒体信息技术有限公司 | 一种分布式信息追踪系统、信息处理方法及装置 |
CN110245035A (zh) * | 2019-05-20 | 2019-09-17 | 平安普惠企业管理有限公司 | 一种链路跟踪方法及装置 |
Cited By (35)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN112506799A (zh) * | 2020-12-22 | 2021-03-16 | 北京百度网讯科技有限公司 | 业务异常定位方法及装置、电子设备、介质、产品 |
CN112506799B (zh) * | 2020-12-22 | 2023-11-10 | 北京百度网讯科技有限公司 | 业务异常定位方法及装置、电子设备、介质、产品 |
CN112579457A (zh) * | 2020-12-24 | 2021-03-30 | 北京志翔能源技术有限公司 | 基于人工智能的数据架构管控方法及系统 |
CN112579457B (zh) * | 2020-12-24 | 2024-04-19 | 北京志翔信息技术有限公司 | 基于人工智能的数据架构管控方法及系统 |
CN113760728A (zh) * | 2021-01-22 | 2021-12-07 | 北京沃东天骏信息技术有限公司 | 应用测试的方法和装置 |
CN112817847A (zh) * | 2021-01-28 | 2021-05-18 | 杭州网易再顾科技有限公司 | 数据处理任务的测试方法、装置、电子设备及存储介质 |
CN113157570A (zh) * | 2021-04-07 | 2021-07-23 | 腾讯音乐娱乐科技(深圳)有限公司 | 确定触发主体信息的方法、设备及存储介质 |
CN113094166B (zh) * | 2021-05-10 | 2023-08-04 | 杭州网易云音乐科技有限公司 | 一种链路追踪方法、装置、介质和计算设备 |
CN113094166A (zh) * | 2021-05-10 | 2021-07-09 | 杭州网易云音乐科技有限公司 | 一种链路追踪方法、装置、介质和计算设备 |
CN113282465A (zh) * | 2021-06-17 | 2021-08-20 | 中国建设银行股份有限公司 | 一种故障定位方法、装置、电子设备及计算机存储介质 |
CN113485891A (zh) * | 2021-06-30 | 2021-10-08 | 中国民航信息网络股份有限公司 | 业务日志监控方法、装置、存储介质及电子设备 |
CN113468159A (zh) * | 2021-07-19 | 2021-10-01 | 广东电网有限责任公司 | 一种数据应用全链路管控方法及系统 |
CN113641554A (zh) * | 2021-08-10 | 2021-11-12 | 南威软件股份有限公司 | 一种跨接口链路监控方法 |
CN113641554B (zh) * | 2021-08-10 | 2023-10-27 | 南威软件股份有限公司 | 一种跨接口链路监控方法 |
CN113806360A (zh) * | 2021-08-12 | 2021-12-17 | 浙江吉利控股集团有限公司 | 一种派单链路故障确定方法、装置、设备及存储介质 |
CN113761406B (zh) * | 2021-09-03 | 2024-06-04 | 丰巢网络技术有限公司 | 一种智能柜二维码短链生成方法、装置、介质及电子设备 |
CN113867913A (zh) * | 2021-09-27 | 2021-12-31 | 平安国际智慧城市科技股份有限公司 | 面向微服务的业务请求处理方法、装置、设备及存储介质 |
CN114153712A (zh) * | 2021-11-22 | 2022-03-08 | 深圳市晨北科技有限公司 | 异常处理方法、装置、设备及存储介质 |
CN114443337A (zh) * | 2022-01-27 | 2022-05-06 | 苏州浪潮智能科技有限公司 | 一种基于js的日志分析方法、装置、电子设备和介质 |
CN114598622A (zh) * | 2022-03-10 | 2022-06-07 | 平安科技(深圳)有限公司 | 数据监控方法及装置、存储介质、计算机设备 |
CN114598622B (zh) * | 2022-03-10 | 2023-04-25 | 平安科技(深圳)有限公司 | 数据监控方法及装置、存储介质、计算机设备 |
CN114866535A (zh) * | 2022-05-30 | 2022-08-05 | 广州简悦信息科技有限公司 | 应用的投放下载方法及装置 |
CN116016646A (zh) * | 2022-11-07 | 2023-04-25 | 中国工商银行股份有限公司 | 业务访问控制方法、装置、设备及介质 |
CN116016646B (zh) * | 2022-11-07 | 2024-05-28 | 中国工商银行股份有限公司 | 业务访问控制方法、装置、设备及介质 |
CN116112397A (zh) * | 2022-11-17 | 2023-05-12 | 中国邮政储蓄银行股份有限公司 | 延时异常的确定方法、确定装置与云平台 |
CN116192621A (zh) * | 2022-12-27 | 2023-05-30 | 上海轻维软件有限公司 | 基于Opentracing链路追踪业务调用链的方法 |
CN116882724A (zh) * | 2023-07-13 | 2023-10-13 | 北京优特捷信息技术有限公司 | 一种业务流程优化方案的生成方法、装置、设备及介质 |
CN116882724B (zh) * | 2023-07-13 | 2024-06-11 | 北京优特捷信息技术有限公司 | 一种业务流程优化方案的生成方法、装置、设备及介质 |
CN116775440B (zh) * | 2023-08-21 | 2023-12-01 | 青岛民航凯亚系统集成有限公司 | 一种基于机场生产运营系统的日志级链路追踪方法及系统 |
CN116775440A (zh) * | 2023-08-21 | 2023-09-19 | 青岛民航凯亚系统集成有限公司 | 一种基于机场生产运营系统的日志级链路追踪方法及系统 |
CN117176802A (zh) * | 2023-11-02 | 2023-12-05 | 太平金融科技服务(上海)有限公司 | 一种业务请求的全链路监控方法、装置、电子设备及介质 |
CN117176802B (zh) * | 2023-11-02 | 2024-01-16 | 太平金融科技服务(上海)有限公司 | 一种业务请求的全链路监控方法、装置、电子设备及介质 |
CN117215964A (zh) * | 2023-11-09 | 2023-12-12 | 中央军委政治工作部军事人力资源保障中心 | 一种业务系统的程序异常观测方法和装置 |
CN117215964B (zh) * | 2023-11-09 | 2024-02-09 | 中央军委政治工作部军事人力资源保障中心 | 一种业务系统的程序异常观测方法和装置 |
CN118227200A (zh) * | 2024-05-24 | 2024-06-21 | 华能信息技术有限公司 | 一种多链路追踪方法 |
Also Published As
Publication number | Publication date |
---|---|
CN110245035A (zh) | 2019-09-17 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2020233015A1 (zh) | 一种链路跟踪方法及装置 | |
US11379475B2 (en) | Analyzing tags associated with high-latency and error spans for instrumented software | |
US11269859B1 (en) | Correlating different types of data of a distributed ledger system | |
CN110457190B (zh) | 一种基于区块链的全链路监控方法、装置及系统 | |
US11775501B2 (en) | Trace and span sampling and analysis for instrumented software | |
US9454450B2 (en) | Modeling and testing of interactions between components of a software system | |
WO2020220638A1 (zh) | 链路系统与日志系统的关联方法、装置及存储介质 | |
US8521871B2 (en) | System and method for merging monitoring data streams from a server and a client of the server | |
US11500709B1 (en) | Mobile application crash monitoring user interface | |
CN110489315B (zh) | 一种操作请求的跟踪方法、跟踪装置及服务器 | |
US20150286470A1 (en) | Modeling and testing of interactions between components of a software system | |
WO2020238130A1 (zh) | 一种大数据日志监控方法及装置、存储介质和计算机设备 | |
US10592327B2 (en) | Apparatus, system, and method for analyzing logs | |
CN111881011A (zh) | 日志管理方法、平台、服务器及存储介质 | |
WO2019085307A1 (zh) | 数据抽样方法、终端、设备以及计算机可读存储介质 | |
WO2020232871A1 (zh) | 一种微服务依赖分析方法及装置 | |
CN106293891B (zh) | 多维投资指标监督方法 | |
CN114817968B (zh) | 无特征数据的路径追溯方法、装置、设备及存储介质 | |
US10241957B2 (en) | Workload patterns for realistic load recreation in performance testing | |
CN110851324A (zh) | 基于日志的巡检处理方法、装置以及电子设备、存储介质 | |
WO2017107679A1 (zh) | 一种历史信息展示方法及装置 | |
WO2015196885A1 (zh) | 云计算系统的性能数据的采集与存储方法及装置 | |
CN111045983B (zh) | 核电站电子文件管理方法、装置、终端设备及介质 | |
JP4973738B2 (ja) | 業務フロー処理プログラム、方法及び装置 | |
CN107330031A (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: 19929609 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: 19929609 Country of ref document: EP Kind code of ref document: A1 |
|
32PN | Ep: public notification in the ep bulletin as address of the adressee cannot be established |
Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205 DATED 18/03/2022) |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 19929609 Country of ref document: EP Kind code of ref document: A1 |