Stress testing sampling logs contain three main parts: request details, response details, and timing information for the core request lifecycle. You can view these logs during a stress test or in a test report to quickly locate issues.
Prerequisites
A stress test has been initiated. For more information, see Initiate a stress test in one minute.Background information
Sampling logs are collected at a 1% frequency and stored for 30 days.Procedure
- On the Stress Testing page or the Report Details page, click View Sampling Logs in the upper-right corner.
- In the View Logs pane, specify the filter criteria and click Query.
- Stress Testing Sampler: Select a single stress testing API.
- Response Status: You can select multiple statuses from the list, including abnormal request statuses and business statuses (success or failure). The Business Status is applicable only to stress testing scenarios where assertions are set.
- Keyword Search 0:1:2: Perform a fuzzy search by DPI engine sampling ID. In this example, 0 indicates the first trace, 1 indicates the first concurrent request in the trace, and 2 is the identity of a stress testing agent. Logs with the same DPI engine sampling ID belong to a sequence of requests from the same concurrent user in the same trace, running on a single stress testing engine.
- Time Range: Specify the time range for the logs. The minimum unit is seconds.
- RT Range: Enter a minimum and maximum response time (RT) to filter the logs.
- Response Status Code: Filter logs by status code, such as 200 or 302.
Note Historical logs created before August 14, 2020 do not support queries by status code.
- Sampling Type: Select a sampling type.
- In the search results, find the target log. In the Operation column, click View Details to view the detailed sampling log. You can view sampling logs and trace information during a stress test or in a test report to quickly locate issues.
The log details include the following information:
- General tab displays the log fields and their values for the sampling log.
The Timing waterfall flow tab shows the time that the request consumes during its core lifecycle.
- DNS Lookup: The time taken to perform a DNS query.
- Get Connected: The time taken to establish a connection.
- Request Sent: The time taken to send the network request.
- Waiting (TTFB): The time taken to wait for the initial response. This time captures the round-trip latency to the server and the time spent waiting for the server to process the request and deliver the response.
- Content Download: The time taken to receive the response data.
- Reuse: The time taken to reuse a connection.
Note The timing information in the sampling log covers only the core lifecycle of a request to help you locate issues. It does not cover all request stages.- Trace View page displays the details of the upstream and downstream traces for the API being tested.
该文章对您有帮助吗？