Call chain monitoring method and call chain monitoring system for browser request

Abstract

The invention relates to the technical field of communication, and provides a call chain monitoring method and a call chain monitoring system for browser requests. The method comprises the steps that a chain recording plug-in is called to obtain recording function starting operation and triggering time triggered by a user when a browser breaks down, and a monitoring identifier is generated; sending the monitoring identifier to a front-end request interceptor, and calling and starting a recording interface to execute recording; the front-end request interceptor adds the monitoring identifier into the received service request message and sends the service request message to a back-end service framework; the back-end service framework monitors the call chain of the message based on the monitoring identifier in the message to obtain call chain log data; the front-end request interceptor notifies a call chain recording plug-in to check recording data of the service request message; and the call chain recording plug-in queries the call chain log data. According to the method, the complete request calling link can be captured and displayed so as to identify the performance problem and the error source, and the troubleshooting time is shortened.

Description

Technical Field

[0001] The present application relates to the field of communication technology, and in particular to a call chain monitoring method and a call chain monitoring system for browser requests. Background Art

[0002] Currently, there are some network monitoring tools and performance analysis tools for monitoring and analyzing HTTP requests. These tools can usually capture basic information about HTTP requests, such as request method, URL, status code, and response time. Some of these tools also provide performance statistics, such as request response time and throughput.

[0003] When users encounter performance issues, slowdowns, or errors, debugging and optimization become very difficult. It is impossible to clearly track the entire life cycle of a request, that is, usually only focusing on the surface information of the HTTP request, unable to provide the complete call link of the request, resulting in a lot of time-consuming troubleshooting. Summary of the invention

[0004] The purpose of the embodiments of the present application is to provide a call chain monitoring method and a call chain monitoring system for browser requests, which can capture and display the complete request call chain, including the multi-level call relationship between the front-end HTTP request and the back-end microservice, and can clearly track the entire path of the request from the starting point to the final target, and deeply understand the details of each step, so as to more easily identify performance problems and error sources, and greatly shorten the time spent on troubleshooting.

[0005] In a first aspect, a call chain monitoring method for a browser request is provided, which is applied to a monitoring system including a call chain recording plug-in, a front-end request interceptor, and a back-end service framework. The method may include:

[0006] The call chain recording plug-in obtains the start recording function operation and trigger time triggered by the user when the browser fails, and generates a monitoring identifier corresponding to the trigger time; and after sending the monitoring identifier to the front-end request interceptor, calls the start recording interface to perform recording; the front-end request interceptor stores the monitoring identifier in a cookie;

[0007] During the recording process, if the front-end request interceptor receives a service request message sent by the user through the browser, it adds the monitoring identifier to the message header of the service request message to obtain a new service request message, and sends the new service request message to the back-end service framework;

[0008] If the backend service framework detects that the message header of the new service request message contains the monitoring identifier, it monitors the call chain of the new service request message, obtains the call chain log data related to the new service request message, and sends a service request response message to the frontend request interceptor to indicate that the monitoring is completed;

[0009] The front-end request interceptor notifies the call chain recording plug-in to view the recording data of the service request message based on the service request response message;

[0010] The call chain recording plug-in calls the backend query log interface to query the call chain log data of the service request message, and displays the corresponding request address so that the user can view the call chain log data according to the request address.

[0011] In a possible implementation, the monitoring identifier includes a current recording event identifier and a to-be-recorded event identifier;

[0012] The current recording event identifier is an identifier of a recording event that is uniquely identified; the to-be-recorded identifier is an identifier that indicates that the request message needs to be recorded.

[0013] In a possible implementation, after the call chain recording plug-in obtains the start recording function operation and the triggering time triggered by the user when the browser fails, the method further includes:

[0014] The call chain recording plug-in generates a monitoring refresh identifier corresponding to the trigger time; and sends the monitoring identifier and the monitoring refresh identifier to the front-end request interceptor; the monitoring refresh identifier is used to instruct the front-end request interceptor to refresh the current cookie and obtain a cookie that stores the monitoring identifier.

[0015] In a possible implementation, the current recording event identifier and the to-be-recorded identifier are both 1-bit identifiers;

[0016] The front-end request interceptor adds the monitoring identifier to the message header of the service request message to obtain a new service request message, including:

[0017] Detecting the number of free fields in the message header;

[0018] If it is detected that the number of free fields in the message header is not less than 2 bits, the current recording event identifier and the to-be-recorded identifier are added to different free fields respectively;

[0019] If it is detected that the number of free fields in the message header is less than 2 bits, determine the first preset bit value corresponding to the current recording event identifier and the second preset bit value corresponding to the to-be-recorded identifier based on the mapping relationship between the configured identifier and the preset bit value; and add the bit sum of the first preset bit value and the second preset bit value to the free field;

[0020] If it is detected that there is no free field in the message header, the message header is expanded to obtain a free field of 1 bit, or two free fields of 1 bit, and the execution step is returned to: detecting the number of free fields in the message header.

[0021] In one possible implementation, the method further includes:

[0022] After receiving the closing recording function operation triggered by the user when the browser fails, the call chain recording plug-in sends a closing call chain monitoring instruction to the backend service framework through the front-end request interceptor, and calls the closing recording interface to close the recording;

[0023] At the same time, the front-end request interceptor clears the monitoring identifier in the cookie;

[0024] The backend service framework closes the call chain monitoring of the new service request message.

[0025] In a possible implementation, the request address includes the current recording event identifier; and the method further includes:

[0026] After establishing a communication connection between the monitoring system and the development platform, the development platform retrieves and analyzes the call chain log data according to the current recording event identifier sent by the user to determine the fault information of the browser fault.

[0027] In a possible implementation, the front-end request interceptor includes an RPC interceptor, an Elastic interceptor, a Feign interceptor, a Redis interceptor, a Repository interceptor, and a Service interceptor.

[0028] In a second aspect, a monitoring system is provided, which may include: a call chain recording plug-in, a front-end request interceptor, and a back-end service framework;

[0029] Among them, the call chain recording plug-in, the front-end request interceptor and the back-end service framework are used to execute the call chain monitoring method steps described in any one of the first aspects above.

[0030] In a third aspect, a computer-readable storage medium is provided, wherein a computer program is stored in the computer-readable storage medium, and when the computer program is executed by a processor, the steps of the call chain monitoring method described in any one of the first aspects are implemented.

[0031] The call chain monitoring method for browser requests provided in the present application includes a call chain recording plug-in obtaining the start recording function operation and trigger time triggered by the user when the browser fails, and generating a monitoring identifier corresponding to the trigger time; after sending the monitoring identifier to the front-end request interceptor, calling the start recording interface to perform recording; the front-end request interceptor stores the monitoring identifier in a cookie; if the front-end request interceptor receives a service request message sent by the user through the browser, the monitoring identifier is added to the message header of the service request message, a new service request message is obtained, and the message is sent to the back-end service framework; if the back-end service framework detects that the message header of the new service request message contains the monitoring identifier, the call chain of the new service request message is monitored, the call chain log data related to the new service request message is obtained, and a service request response message is sent to the front-end request interceptor to indicate that the monitoring is completed; the front-end request interceptor notifies the call chain recording plug-in to view the recording data of the service request message based on the service request response message; the call chain recording plug-in calls the back-end query log interface to query the call chain log data of the service request message, and displays the corresponding request address so that the user can view the call chain log data according to the request address. This method can capture and display the complete request call chain, making it easier to identify performance problems and error sources, greatly shortening the time spent on troubleshooting. BRIEF DESCRIPTION OF THE DRAWINGS

[0032] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required for use in the embodiments of the present application will be briefly introduced below. It should be understood that the following drawings only show certain embodiments of the present application and therefore should not be regarded as limiting the scope. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without paying creative work.

[0033] Figure 1 An architecture diagram of a monitoring system provided in an embodiment of the present application;

[0034] Figure 2 A flowchart of a call chain monitoring method for browser requests provided in an embodiment of the present application. DETAILED DESCRIPTION

[0035] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments of the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0036] Traditional browser console tools usually only provide limited HTTP request information, such as request method, URL, and status code. This limits our comprehensive understanding of the complete call chain of the request. In real applications, multiple microservices and backend services may be called in series to form a complex call chain. When users are solving performance problems, slowness, or troubleshooting call errors, detailed call chain information is urgently needed.

[0037] Specifically, traditional browser console tools have the following disadvantages:

[0038] (1) Insufficient call chain tracing: Traditional tools usually only provide limited HTTP request information and cannot capture and display the complete call chain of the request. This makes it impossible for users to gain in-depth understanding of the path and call relationship of the request from the front-end to the back-end microservices.

[0039] (2) Lack of backend microservice tracing: In a complex microservice architecture, requests may pass through multiple microservice layers. Traditional tools usually lack in-depth tracing and visualization of the call relationships between backend microservices, making it difficult to help users analyze and optimize the interactions between microservices.

[0040] (3) Difficulty in troubleshooting performance issues: When users encounter slow performance or performance degradation, traditional tools provide limited information and fail to provide sufficient context and details, making it difficult to accurately troubleshoot the root cause of the performance issue.

[0041] (4) Call recording and playback requirements: When troubleshooting, users often need to record the complete call chain of a request in order to further analyze and reproduce the problem. However, traditional tools usually lack call recording and playback functions, making troubleshooting more difficult.

[0042] In order to solve the above technical problems, the present application embodiment provides a call chain monitoring method for browser requests, which can be applied to Figure 1 In the monitoring system shown in Figure 1 As shown, the monitoring system may include: a call chain recording plug-in, a front-end request interceptor and a back-end service framework.

[0043] The call chain recording plug-in has a communication connection with the browser to receive the user's trigger operation;

[0044] The front-end request interceptor has a communication connection with the browser. The front-end request interceptor receives the user's trigger operation on the browser through the browser. The front-end request interceptor may include but is not limited to: RPC interceptor, Elastic interceptor, Feign interceptor, Redis interceptor, Repository interceptor and Service interceptor.

[0045] The backend service framework can be set in the backend terminal device or the backend server, and is the service architecture that the business service relies on. Among them, the server can be a physical server, or a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, content delivery networks (Content Delivery Network, CDN), as well as basic cloud computing services such as big data and artificial intelligence platforms. The terminal device can be a user equipment (User Equipment, UE) such as a laptop, tablet computer (PAD), a handheld device, a vehicle-mounted device, a wearable device, a computing device or other processing device connected to a wireless modem, a mobile station (Mobile Station, MS), a mobile terminal (Mobile Terminal), etc.

[0046] Compared with traditional browser console tools, the call chain monitoring method for browser requests provided by this application may have the following advantages and corresponding effects:

[0047] (1) Compared with traditional tools that only provide limited HTTP request information, it can capture and display the complete request call chain, including the multi-level call relationship between the front-end HTTP request and the back-end microservices.

[0048] Effect: Users can clearly trace the entire path of a request from its starting point to its final destination, gaining insight into the details of each step, making it easier to identify performance issues and error sources.

[0049] (2) Compared with traditional tools that are usually unable to deeply trace and visualize the calling relationships between backend microservices, it can provide deep backend microservice tracing capabilities.

[0050] Effect: Users can clearly understand the dependencies between microservices and analyze the call chains within each microservice, which helps optimize microservice architecture and interactions.

[0051] (3) Compared with traditional tools that usually do not support call recording and playback, it allows users to record the complete call chain of a request and play it back at any time.

[0052] Benefit: Users can reproduce problem scenarios, speed up the troubleshooting process, and share recordings with team members to collaboratively solve problems.

[0053] (4) Detailed information and time statistics for each call step can be provided, compared to traditional tools which usually provide basic information about response time.

[0054] Effect: Users can locate performance bottlenecks more accurately, quickly identify potential problems, and perform targeted optimizations.

[0055] Among them, detailed information and performance statistics: Compared with traditional tools, it can provide detailed information for each call step, including parameters, response data, and time statistics, etc. It helps users to deeply analyze performance bottlenecks and find key points for optimization.

[0056] Through the above analysis, it can be clearly seen that this application brings many advantages and effects compared with the existing technology, including comprehensive call chain tracking, in-depth tracking of backend microservices, improved troubleshooting efficiency, call recording and playback functions, and detailed performance statistics. These advantages will provide users with more powerful and comprehensive performance analysis and troubleshooting tools, greatly shortening the time spent on troubleshooting.

[0057] The preferred embodiments of the present application are described below in conjunction with the drawings in the specification. It should be understood that the preferred embodiments described herein are only used to illustrate and explain the present application, and are not used to limit the present application. In addition, the embodiments and features in the embodiments of the present application may be combined with each other if there is no conflict.

[0058] Figure 2 A flowchart of a method for processing business data provided by an embodiment of the present application. Figure 2 As shown, the method may include:

[0059] Step 20: The call chain recording plug-in obtains the start recording function operation and trigger time triggered by the user when the browser fails, and generates a monitoring identifier corresponding to the trigger time.

[0060] The monitoring identifier may include a current recording event identifier and a pending recording identifier;

[0061] The current recording event identifier is an identifier of a recording event that represents a unique identifier; the pending recording identifier is an identifier that indicates that the request message needs to be recorded.

[0062] Step 21: The call chain recording plug-in sends a monitoring identifier to the front-end request interceptor, and calls the start recording interface to perform recording.

[0063] Step 22: The front-end request interceptor stores the monitoring identifier in a cookie.

[0064] Furthermore, in order to allow the backend service framework to monitor only the recording events at the current time, the call chain recording plug-in may generate a monitoring refresh flag corresponding to the trigger time after obtaining the trigger time in step 20; the monitoring refresh flag is used to instruct the front-end request interceptor to refresh the current cookie;

[0065] At this time, step 21 is changed to: the call chain recording plug-in sends the monitoring identifier and the monitoring refresh identifier to the front-end request interceptor;

[0066] Correspondingly, step 22 is changed to: the front-end request interceptor refreshes the current cookie based on the monitoring refresh identifier to obtain a cookie that only stores the monitoring refresh identifier corresponding to the trigger time.

[0067] Step 23: The front-end request interceptor adds the monitoring identifier to the message header of the received service request message to obtain a new service request message.

[0068] In a specific implementation, during the recording process of the call chain recording plug-in, after the front-end request interceptor receives the service request message sent by the user through the browser, it adds the monitoring identifier to the message header of the service request message to obtain a new service request message.

[0069] If the front-end request interceptor does not receive the service request message sent by the user through the browser within the first preset time, a prompt message is displayed to the user asking whether to continue waiting;

[0070] After the user triggers the operation of determining to continue waiting, the front-end request interceptor continues to monitor whether the browser receives the service request message within the first preset time period.

[0071] After the user triggers the operation of refusing to continue waiting, the front-end request interceptor clears the monitoring identifier corresponding to the trigger time in the cookie, and sends a timeout waiting indication message to the call chain recording plug-in, so that the call chain recording plug-in calls the recording shutdown interface to close the recording.

[0072] Furthermore, the number of bits of the field occupied by the current recording event identifier and the to-be-recorded identifier may be configured in advance, such as the current recording event identifier and the to-be-recorded identifier are both 1-bit identifiers, that is, the current recording event identifier and the to-be-recorded identifier each occupy a 1-bit field.

[0073] Specifically, the front-end request interceptor may include:

[0074] Detect the number of free fields in the message header of the service request message;

[0075] If it is detected that the number of free fields in the message header is not less than 2 bits, the current recording event identifier and the to-be-recorded identifier are added to different free fields respectively;

[0076] If it is detected that the number of free fields in the message header is less than 2 bits, a first preset bit value corresponding to the current recording event identifier and a second preset bit value corresponding to the to-be-recorded identifier are determined based on a mapping relationship between the configured identifier and the preset bit value; and a bit sum of the first preset bit value and the second preset bit value is added to the free field;

[0077] If it is detected that there is no free field in the message header, the message header is expanded to obtain a free field of 1 bit, or two free fields of 1 bit, and the execution step is returned to: detect the number of free fields in the message header of the service request message.

[0078] Step 24: The front-end request interceptor sends a new service request message to the back-end service framework.

[0079] In a specific implementation, since the message header of the new service request message contains the current recording event identifier and the to-be-recorded identifier, it can be ensured that related events can be correctly tracked and associated after being sent to the backend service framework.

[0080] Step 25: After the backend service framework detects that the new service request message contains a monitoring identifier, it monitors the call chain of the new service request message to obtain the call chain log data.

[0081] After the backend service framework detects that the message header of the new service request message contains a monitoring identifier, it monitors the call chain of the new service request message, specifically including: writing the log information involved in the new service request message into the log information queue. The lightweight processing log thread obtains data from the log information queue and writes it to the ES index generated when the log is opened.

[0082] It should be noted that if the front-end request interceptor in step 23 adds the bits and values ​​of the current recording event identifier and the identifier to be recorded to the free field of the message header, then in step 25, in order for the back-end service framework to detect whether the current recording event identifier and the identifier to be recorded exist in the message header, the back-end service framework needs to pre-store the configured bits and thresholds so that when the back-end service framework detects that the bits and values ​​in the message header are consistent with the stored bits and thresholds, it can determine that the message header contains the current recording event identifier and the identifier to be recorded.

[0083] Step 26: The backend service framework sends a service request response message to the frontend request interceptor to indicate that the monitoring is complete.

[0084] Step 27: The front-end request interceptor notifies the call chain recording plug-in to view the call chain log data of the service request message.

[0085] Since a service request message includes multiple call nodes, the log data of each call node may include the request address of the corresponding call node, service name, recording event id, child node, method name, sorting, opening search column display configuration identifier, logical deletion, recording start time, recording end time, method name, node information, parent id, request parameters, panoramic log tracking id, type (RCP, Radis, ES, SQL), etc.

[0086] In an example, the data structure of log data of a single calling node may be as shown in Table 1.

[0087] Table 1

[0088]

[0089]

[0090] Based on the integration of the log data of the above-mentioned single call node, the call chain log data of the service request message can be obtained.

[0091] Step 28: The call chain recording plug-in calls the backend query log interface to query the call chain log data and displays the corresponding request address.

[0092] The user views the call chain log data according to the request address, wherein the request address may include the current recording event identifier.

[0093] In some embodiments, after the call chain recording plug-in calls the backend query log interface to query the call chain log data, if a user triggers a recording shutdown function operation when the browser fails, a call chain monitoring shutdown instruction is sent to the backend service framework through the frontend request interceptor, and the recording shutdown interface is called to shut down the recording;

[0094] At the same time, the front-end request interceptor clears the monitoring flag in the cookie; the back-end service framework closes the call chain monitoring of the new service request message, and automatically clears the call chain thread, traverses the call chain that has not expired and timed out, and closes the call chain.

[0095] In some embodiments, the monitoring system can establish a communication connection with the development platform. After obtaining the request address of the call chain log data, the user can send the request address to the development platform. The development platform retrieves and analyzes the call chain log data based on the current recording event identifier in the request address to determine the fault information of the browser failure and perform operation and maintenance.

[0096] In another embodiment provided in the present application, a computer-readable storage medium is also provided, in which instructions are stored. When the computer-readable storage medium is executed on a computer, the computer executes the call chain monitoring method for browser requests described in any of the above embodiments.

[0097] In another embodiment provided by the present application, a computer program product including instructions is also provided, which, when executed on a computer, enables the computer to execute the call chain monitoring method for browser requests described in any of the above embodiments.

[0098] Those skilled in the art will appreciate that the embodiments in the present application may be provided as methods, systems, or computer program products. Therefore, the present application may adopt a complete hardware embodiment, a complete software embodiment, or a form of an embodiment combining software and hardware. Moreover, the present application may adopt a form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0099] The embodiments of the present application are described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0100] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0101] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0102] Although the preferred embodiments of the present application have been described, those skilled in the art may make additional changes and modifications to these embodiments once they have learned the basic creative concept. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments and all changes and modifications falling within the scope of the embodiments of the present application.

[0103] Obviously, those skilled in the art can make various changes and modifications to the embodiments in the present application without departing from the spirit and scope of the embodiments in the present application. Thus, if these modifications and variations of the embodiments in the present application fall within the scope of the claims and their equivalents in the embodiments of the present application, the embodiments of the present application are also intended to include these modifications and variations.

Claims

1. A call chain monitoring method for browser requests, It is characterized in that Applied to a monitoring system including a call chain recording plug-in, a front-end request interceptor and a back-end service framework, the method includes: The call chain recording plug-in obtains the start recording function operation and trigger time triggered by the user when the browser fails, and generates a monitoring identifier corresponding to the trigger time; and after sending the monitoring identifier to the front-end request interceptor, calls the start recording interface to perform recording; the front-end request interceptor stores the monitoring identifier in a cookie; During the recording process, if the front-end request interceptor receives a service request message sent by the user through the browser, it adds the monitoring identifier to the message header of the service request message to obtain a new service request message, and sends the new service request message to the back-end service framework; If the backend service framework detects that the message header of the new service request message contains the monitoring identifier, it monitors the call chain of the new service request message, obtains the call chain log data related to the new service request message, and sends a service request response message to the frontend request interceptor to indicate that the monitoring is completed; The front-end request interceptor notifies the call chain recording plug-in to view the recording data of the service request message based on the service request response message; The call chain recording plug-in calls the backend query log interface to query the call chain log data of the service request message, and displays the corresponding request address so that the user can view the call chain log data according to the request address.

2. The method according to claim 1, It is characterized in that The monitoring identifier includes a current recording event identifier and a pending recording identifier; The current recording event identifier is an identifier of a recording event that is uniquely identified; the to-be-recorded identifier is an identifier that indicates that the request message needs to be recorded.

3. The method according to claim 2, It is characterized in that After the call chain recording plug-in obtains the start recording function operation and the triggering time triggered by the user when the browser fails, the method further includes: The call chain recording plug-in generates a monitoring refresh identifier corresponding to the trigger time; and sends the monitoring identifier and the monitoring refresh identifier to the front-end request interceptor; the monitoring refresh identifier is used to instruct the front-end request interceptor to refresh the current cookie and obtain a cookie that stores the monitoring identifier.

4. The method according to claim 2, It is characterized in that The current recording event identifier and the to-be-recorded identifier are both 1-bit identifiers; The front-end request interceptor adds the monitoring identifier to the message header of the service request message to obtain a new service request message, including: Detecting the number of free fields in the message header; If it is detected that the number of free fields in the message header is not less than 2 bits, the current recording event identifier and the to-be-recorded identifier are added to different free fields respectively; If it is detected that the number of free fields in the message header is less than 2 bits, determine the first preset bit value corresponding to the current recording event identifier and the second preset bit value corresponding to the to-be-recorded identifier based on the mapping relationship between the configured identifier and the preset bit value; and add the bit sum of the first preset bit value and the second preset bit value to the free field; If it is detected that there is no free field in the message header, the message header is expanded to obtain a free field of 1 bit, or two free fields of 1 bit, and the execution step is returned to: detecting the number of free fields in the message header.

5. The method according to claim 1, It is characterized in that The method further comprises: After receiving the closing recording function operation triggered by the user when the browser fails, the call chain recording plug-in sends a closing call chain monitoring instruction to the backend service framework through the front-end request interceptor, and calls the closing recording interface to close the recording; At the same time, the front-end request interceptor clears the monitoring identifier in the cookie; The backend service framework closes the call chain monitoring of the new service request message.

6. The method according to claim 2, It is characterized in that The request address includes the current recording event identifier; the method further includes: After establishing a communication connection between the monitoring system and the development platform, the development platform retrieves and analyzes the call chain log data according to the current recording event identifier sent by the user to determine the fault information of the browser fault.

7. The method according to claim 1, It is characterized in that The front-end request interceptor includes RPC interceptor, Elastic interceptor, Feign interceptor, Redis interceptor, Repository interceptor and Service interceptor.

8. A monitoring system, It is characterized in that The monitoring system includes: a call chain recording plug-in, a front-end request interceptor and a back-end service framework; Among them, the call chain recording plug-in, the front-end request interceptor and the back-end service framework are used to execute the call chain monitoring method described in any one of claims 1-7.

9. A computer-readable storage medium, It is characterized in that The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the call chain monitoring method according to any one of claims 1 to 7 is implemented.

Images