Method and system for generating performance portrait of full-link pressure test scene

By using traceId identification and Agent probe technology in the financial system, combining the grafana framework to display indicators and build call relationship diagrams, the complex business link performance evaluation problem is solved, system performance optimization and exception identification are achieved, and system stability is improved sex.

CN119030898AInactive Publication Date: 2024-11-26RURAL CREDIT BANKS FUNDS CLEARING CENT CO LTD
View PDF 3 Cites 0 Cited by

Patent Information

Application Number
CN202410992087.9
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-07-23
Publication Date
2024-11-26
Estimated Expiration
Not applicable · inactive patent

AI Technical Summary

Technical Problem

The prior art is difficult to effectively evaluate the performance bottlenecks and carrying capacity of business links in complex financial systems, and there is a lack of a platform for viewing full-link execution and indicators.

Method used

By adding a unique identifier traceId to the HTTP header request header, traffic staining is realized, and service-related information is collected in combination with Agent probe technology, grafana framework is used to visualize indicator data, build a service call relationship diagram, analyze link execution status and log alarms information.

Benefits of technology

Clearly display service call situations, quickly locate performance bottlenecks, optimize system architecture, realize unified monitoring and exception identification, and improve system reliability and stability.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119030898A_ABST
    Figure CN119030898A_ABST
Patent Text Reader

Abstract

The invention is suitable for the technical field of testing, and provides a full-link pressure test scene performance portrait generation method and system, and the method comprises the steps: traffic dyeing; collecting data; collecting data; displaying the index data; performing link tracking analysis; service calling analysis; and log analysis. According to the method, by constructing the service calling relation graph, the calling situation between services can be clearly displayed, system optimizable items are analyzed from the architecture and micro-service division level, services or service interaction modes causing performance bottlenecks are rapidly positioned, and targeted optimization adjustment is carried out. According to the invention, the distributed logs of each micro-service are collected, so that unified monitoring and analysis are realized, the system condition is convenient to know, abnormal conditions can be quickly identified and processed through centralized monitoring, an alarm mechanism is enhanced, and the reliability and stability of the system are improved.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention belongs to the field of testing technology, and in particular relates to a method and system for generating a performance profile of a full-link stress testing scenario. Background Art

[0002] Before the banking business system goes online, performance testing is an essential step. This test can evaluate the performance of the system and the performance capacity under different hardware resources or configurations. With the continuous increase in business traffic, the scale of the entire business chain is also increasing, and the complexity of the business architecture is also increasing. Therefore, in order to ensure the continuity of the system and improve performance, full-link stress testing has become a common method. This test can simulate the actual business scenario, system environment, user requests and data, and stress test the entire business process, so as to discover and solve various problems, such as locating system performance bottlenecks and checking whether the use of system resources is reasonable.

[0003] However, there are some problems with the current performance testing methods for such businesses: (1) Most financial systems have complex technical architectures and long business transaction links, and the number of application nodes involved in business flows is large, making it difficult to evaluate system performance bottlenecks and carrying capacity; (2) There is currently no platform that can support viewing the full-link execution status and statistics of full-link execution indicators in performance testing. To this end, a method and system for generating performance profiles for full-link stress testing scenarios are proposed. Summary of the invention

[0004] The purpose of the present invention is to provide a method and system for generating a performance profile of a full-link stress testing scenario, aiming to solve the problems raised in the above-mentioned background technology.

[0005] To achieve the above object, the present invention provides the following technical solutions:

[0006] A method for generating a performance profile of a full-link stress test scenario includes the following steps:

[0007] Step 1, flow dyeing;

[0008] Step 2: Data collection;

[0009] Step 3: Data collection;

[0010] Step 4: Display indicator data;

[0011] Step 5: Link tracking analysis;

[0012] Step 6: Service call analysis;

[0013] Step 7: Log analysis.

[0014] Furthermore, the specific process of step 1 is: adding a unique identifier traceId in the HTTP header request header as a unique identifier for each request to implement traffic coloring, and carrying the identifier in the entire business link, collecting indicator data related to the traceId link, which is used to track the execution link of the system and perform traffic analysis.

[0015] Furthermore, the specific process of step 2 is: performing instrumentation based on Agent probe technology to collect service-related information, and reporting the collected data.

[0016] Furthermore, the specific process of step 3 is: receiving reported data; the collected data includes:

[0017] a. Globally unique identifier traceId: used to associate the request with the subsequent call service;

[0018] b. Service name / interface path: all service names and interface request paths accessed by the same request;

[0019] c. Call sequence span_id: identifies a specific service in the call link;

[0020] d. Parent span number parent_span_id: identifies the parent span identifier of the current call relationship;

[0021] e. Service call timestamp: records the start time of accessing a service and the end time of service processing completion, to assist in time-consuming troubleshooting of interface services during performance testing;

[0022] f. Number of calls: record the number of times a single service calls other services and the number of times it is called;

[0023] g. Host resources and log data: The collected log data is stored and queried through ELK.

[0024] Furthermore, the specific process of step 4 is: visually displaying the collected and stored indicator data based on the grafana framework.

[0025] Furthermore, the specific process of step 5 is: by querying the unique identifier traceId of the stored data, the service time consumption and link execution model are displayed in the visual interface.

[0026] Furthermore, the specific process of step 6 is: by tracking the request link multiple times, recording the calls between services and the upstream and downstream situations, building a service call relationship diagram, displaying the number of service calls and call relationships, analyzing whether there are repeated calls, the degree of coupling between services, and the unreasonable upstream and downstream thread settings and timeout settings; and evaluating the degree of connection between modules through the number of service calls and the number of calls; if there are too many times or repeated calls, re-splitting the microservices.

[0027] Furthermore, the specific process of step 7 is: checking the collected logs, counting the log alarm information, and identifying system and business anomalies.

[0028] A system for generating performance profiles of full-link stress testing scenarios, including:

[0029] Traffic coloring module, used to add a unique identifier traceId in the HTTP header request header as the unique identifier of each request, implement traffic coloring, carry the identifier in the entire business link, collect indicator data related to the traceId link, and use it to track the execution link of the system and perform traffic analysis;

[0030] The data collection module is used to collect service-related information through plugging based on the Agent probe technology, and report the collected data to the data collection module;

[0031] A data collection module, used for receiving reported data;

[0032] The indicator data display module is used to visualize the collected and stored indicator data based on the grafana framework;

[0033] The link tracking analysis module is used to query the unique identifier traceId of the stored data and display the service time consumption and link execution model in the visual interface;

[0034] The service call analysis module is used to track request links multiple times, record the calls between services and upstream and downstream situations, build a service call relationship diagram, display the number of service calls and call relationships, analyze whether there are repeated calls, the degree of coupling between services, and unreasonable upstream and downstream thread settings and timeout settings; and evaluate the closeness of the connection between modules through the number of service calls and the number of times they are called;

[0035] The log analysis module is used to view collected logs, collect log alarm information, and identify system and business anomalies.

[0036] Compared with the prior art, the present invention has the following beneficial effects:

[0037] 1. By constructing a service call relationship diagram, the present invention can clearly display the call status between services, analyze the system optimisation items from the architecture and microservice division levels, quickly locate the services or service interaction modes that cause performance bottlenecks, and perform targeted optimization adjustments.

[0038] 2. The present invention realizes unified monitoring and analysis by collecting the scattered logs of each microservice, which makes it easier to understand the system situation. Through centralized monitoring, abnormal situations can be quickly identified and handled. At the same time, the alarm mechanism is strengthened, and the reliability and stability of the system are improved. BRIEF DESCRIPTION OF THE DRAWINGS

[0039] Figure 1 This is a schematic diagram of the present invention.

[0040] Figure 2 It is a flow chart of the present invention.

[0041] Figure 3 This is the data collection process of the microservice call link in the present invention. DETAILED DESCRIPTION

[0042] In order to make the purpose, technical solution and advantages of the present invention more clearly understood, the present invention is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present invention and are not used to limit the present invention.

[0043] The specific implementation of the present invention is described in detail below in conjunction with specific embodiments.

[0044] like Figure 1 As shown, an embodiment of the present invention provides a system for generating a performance profile of a full-link stress test scenario, including:

[0045] Traffic coloring module, used to add a unique identifier traceId in the HTTP header request header as the unique identifier of each request, implement traffic coloring, carry the identifier in the entire business link, collect indicator data related to the traceId link, and use it to track the execution link of the system and perform traffic analysis;

[0046] The data collection module is used to collect service-related information through plugging based on the Agent probe technology, and report the collected data to the data collection module;

[0047] A data collection module, used for receiving reported data;

[0048] The indicator data display module is used to visualize the collected and stored indicator data based on the grafana framework;

[0049] The link tracking analysis module is used to query the unique identifier traceId of the stored data and display the service time consumption and link execution model in the visual interface;

[0050] The service call analysis module is used to track request links multiple times, record the calls between services and upstream and downstream situations, build a service call relationship diagram, display the number of service calls and call relationships, analyze whether there are repeated calls, the degree of coupling between services, and unreasonable upstream and downstream thread settings and timeout settings; and evaluate the closeness of the connection between modules through the number of service calls and the number of times they are called;

[0051] The log analysis module is used to view collected logs, collect log alarm information, and identify system and business anomalies.

[0052] like Figure 2 As shown, an embodiment of the present invention provides a method for generating a performance profile of a full-link stress test scenario, including the following steps:

[0053] Step 1: Traffic coloring: Add a unique identifier traceId to the HTTP header request header as the unique identifier of each request to achieve traffic coloring, and carry the identifier in the entire business link, collect indicator data related to the traceId link, and use it to track the execution link of the system and perform traffic analysis;

[0054] Step 2: Data collection: Use Agent probe technology to collect service-related information, such as logs, tracking data, and statistics, and report the collected data to the data collection module.

[0055] Step 3: Data collection: Receive reported data; the main collected data include:

[0056] a. Globally unique identifier traceId: used to associate the request with the subsequent call service to ensure that the entire request-response link can be fully traced;

[0057] b. Service name / interface path: all service names and interface request paths accessed by the same request, for easy display;

[0058] c. Call sequence span_id: identifies a specific service in the call chain; for example, service a calls service b and is named 1.1;

[0059] d. Parent_span_id: identifies the parent identifier of the current call relationship. For example, if the current call number is 1.1, the parent_span_id of the call relationship is 1.

[0060] e. Service call timestamp: records the start time of accessing a service and the end time of service processing completion, to assist in time-consuming troubleshooting of interface services during performance testing;

[0061] f. Number of calls: record the number of times a single service calls other services and the number of times it is called;

[0062] g. Host resources and log data: host operation data such as CPU usage, memory usage, disk IO time consumption, etc. The collected log data is stored and queried through ELK.

[0063] After analyzing, integrating, calculating and storing the above collected data, the service call link relationship of the request can be depicted, and data can be queried through the provided query API interface. Figure 3 shown.

[0064] Step 4: Indicator data display: Visualize the collected and stored indicator data based on the grafana framework;

[0065] Step 5: Link tracking analysis: By querying the unique identifier traceId of the stored data, the service time consumption, link execution model, etc. are displayed in the visual interface. The specific display information is shown in Table 1.

[0066] Table 1 shows information

[0067]

[0068] Step 6, service call analysis: By tracking the request link multiple times, recording the calls between services and the upstream and downstream situations, building a service call relationship diagram, showing the number of service calls and call relationships, analyzing whether there are repeated calls, the degree of coupling between services, and the unreasonable upstream and downstream thread settings and timeout settings. Figure 2 As shown in the figure, from the perspective of horizontal splitting, service a and service c are at the same level of business relationship and should focus on their own business functions. If there is a calling or called relationship between a and c, the microservice division should be re-performed to ensure the independence of services and improve cohesion. The closeness of the connection between modules can be evaluated by the number of service calls and calls. If there are too many or repeated calls, the microservice splitting should be considered to enhance the independence of microservices and reduce the coupling between microservices.

[0069] Step 7: Log analysis: View the collected logs, collect log alarm information, and identify system and business anomalies.

[0070] The above are only preferred embodiments of the present invention. It should be pointed out that, for those skilled in the art, several modifications and improvements can be made without departing from the concept of the present invention. These should also be regarded as the protection scope of the present invention. These will not affect the effect of the implementation of the present invention and the practicality of the patent.

Claims

1. A method for generating a performance profile of a full-link stress test scenario, characterized in that: The following steps are involved: Step 1, flow dyeing; Step 2: Data collection; Step 3: Data collection; Step 4: Display indicator data; Step 5: Link tracking analysis; Step 6: Service call analysis; Step 7: Log analysis.

2. The method for generating a performance profile of a full-link stress test scenario according to claim 1, characterized in that: The specific process of step 1 is: add a unique identifier traceId in the HTTP header request header as a unique identifier for each request to implement traffic coloring, carry the identifier in the entire business link, collect indicator data related to the traceId link, and use it to track the execution link of the system and perform traffic analysis.

3. The method for generating a performance profile of a full-link stress test scenario according to claim 1, characterized in that: The specific process of step 2 is: performing plugging based on Agent probe technology to collect service-related information, and reporting the collected data.

4. The method for generating a performance profile of a full-link stress test scenario according to claim 1, characterized in that: The specific process of step 3 is: receiving reported data; the collected data includes: a. Globally unique identifier traceId: used to associate the request with the subsequent call service; b. Service name / interface path: all service names and interface request paths accessed by the same request; c. Call sequence span_id: identifies a specific service in the call link; d. Parent span number parent_span_id: identifies the parent span identifier of the current call relationship; e. Service call timestamp: records the start time of accessing a service and the end time of service processing completion, to assist in time-consuming troubleshooting of interface services during performance testing; f. Number of calls: record the number of times a single service calls other services and the number of times it is called; g. Host resources and log data: The collected log data is stored and queried through ELK.

5. The method for generating a performance profile of a full-link stress test scenario according to claim 1, characterized in that: The specific process of step 4 is: visually display the collected and stored indicator data based on the grafana framework.

6. The method for generating a performance profile of a full-link stress test scenario according to claim 1, characterized in that: The specific process of step 5 is: by querying the unique identifier traceId of the stored data, the service time consumption and link execution model are displayed in the visual interface.

7. The method for generating a performance profile of a full-link stress test scenario according to claim 1, characterized in that: The specific process of step 6 is: by tracking the request link multiple times, recording the calls between services and the upstream and downstream situations, building a service call relationship diagram, showing the number of service calls and call relationships, analyzing whether there are repeated calls, the degree of coupling between services, and unreasonable upstream and downstream thread settings and timeout settings; and evaluating the closeness of the connection between modules through the number of service calls and the number of calls; if there are too many times or repeated calls, re-splitting the microservices.

8. The method for generating a performance profile of a full-link stress test scenario according to claim 1, characterized in that: The specific process of step 7 is: checking the collected logs, counting the log alarm information, and identifying system and business anomalies.

9. A system for generating performance portraits of full-link stress test scenarios, characterized in that: include: Traffic coloring module, used to add a unique identifier traceId in the HTTP header request header as the unique identifier of each request, implement traffic coloring, carry the identifier in the entire business link, collect indicator data related to the traceId link, and use it to track the execution link of the system and perform traffic analysis; The data collection module is used to collect service-related information through plugging based on the Agent probe technology, and report the collected data to the data collection module; A data collection module, used for receiving reported data; The indicator data display module is used to visualize the collected and stored indicator data based on the grafana framework; The link tracking analysis module is used to query the unique identifier traceId of the stored data and display the service time consumption and link execution model in the visual interface; The service call analysis module is used to track request links multiple times, record the calls between services and upstream and downstream situations, build a service call relationship diagram, display the number of service calls and call relationships, analyze whether there are repeated calls, the degree of coupling between services, and unreasonable upstream and downstream thread settings and timeout settings; and evaluate the closeness of the connection between modules through the number of service calls and the number of times they are called; The log analysis module is used to view collected logs, collect log alarm information, and identify system and business anomalies.

Citation Information

Patent Citations

  • Micro-service link tracking and performance analysis method, system, equipment and application

    CN113946499A

  • Full-link monitoring method and device, equipment, storage medium and program product

    CN114490268A

  • Integrated application performance diagnosis system and method based on link tracking

    CN117194142A