Skip to main content

results-k6

Last updated on

Run overview​

The left panel, titled About This Test, shows the test metadata and the live status of the execution.

FieldDescription
Test NameName of the load test.
Load Test InfrastructureThe infrastructure that ran the test, with its connection status.
TypeReads k6.
UsersPeak concurrent virtual users configured.
DurationTotal configured test duration.
ReplicasNumber of runner pods the load was split across for distributed execution.
Peak VUsHighest number of virtual users reached during the run.
Run StartedTimestamp when the execution began.
Time ElapsedHow long the test has run, or the total runtime once complete.
StatusExecution status: Running, Finished, or Failed.
The top of the Run detail page for a finished k6 run, showing the About This Test panel with Replicas and Peak VUs, the six summary cards including Failed Rate and P50, P95, and P99, the Checks table, and the Active Users chart

The Run detail page for a finished k6 run. The k6 cards report Failed Rate and the P50, P95, and P99 percentiles, and the Checks table shows a 100% pass rate. This run defined no thresholds, so no Thresholds table appears.

Summary cards​

The cards across the top of the results panel report the headline metrics for a k6 run:

MetricWhat it measures
Total RequestsTotal number of requests sent during the test.
Request Per SecondAverage throughput across the whole run, in requests per second.
Failed RatePercentage of requests that failed.
P50Median response time, in milliseconds.
P9595th-percentile response time. Five percent of requests were slower than this.
P9999th-percentile response time, useful for spotting tail latency.

Thresholds and checks​

Below the summary cards, k6 runs show up to two extra tables.

  • Thresholds: This table appears only when the test defines thresholds. Each row shows a Metric, its pass/fail Condition (for example, p(95)<5000), the Actual measured value, and a Status. A breached threshold marks the whole run as Failed, which is how a k6 test becomes a release gate. The status reads PENDING while the run is in progress. A test with no thresholds shows no Thresholds table.
  • Checks: Validations declared in the script or built in the UI. The table lists each Check with its Passed and Total counts and an overall pass rate (for example, 100.0% pass rate (171 / 171)). Failed checks are recorded but do not fail the run on their own.

Go to k6 to configure thresholds and checks.

Charts​

The charts visualize how the test behaved over time.

Active users​

A time-series line chart of concurrent virtual users. Use it to confirm the load followed the shape you configured:

  • The ramp-up phase, where users rise linearly from zero to the configured peak.
  • The steady-state phase, where the count plateaus at the peak.
  • The ramp-down at the end, or an early drop if the run stopped or failed.

Total requests per second​

A time-series chart with two lines:

  • Request Per Second (green): throughput over time.
  • Errors/sec (red): errors over time.

Read the two lines together to see whether throughput holds under sustained load and whether errors climb as users increase. A rising red line while the green line flattens is a strong sign the system is at capacity.

Response time distribution​

A scatter plot of individual request response times over the run. Each point is color-coded by request name and outcome:

  • Success: requests that returned a successful response and passed all assertions.
  • Failure: requests that failed or violated an assertion.

Use it to spot latency that drifts upward as load increases, outlier requests, and whether response times stay within your target.

Response time histogram​

A histogram that bins the per-request response times and plots how many requests fell into each latency band. The subtitle notes that the top one percent of samples is clipped so a few slow outliers do not distort the scale. Use it to see the typical latency band and how tightly response times cluster.

A k6 run showing the Total Requests Per Second chart, the Response Time Distribution scatter plot, and the Response Time Histogram that bins response times into latency bands

A k6 run. Alongside the Total Requests Per Second and Response Time Distribution charts, k6 adds a Response Time Histogram that groups requests into latency bands.

Console logs and endpoint statistics​

Below the charts, two sections give you the raw detail behind the summary.

  • Load Test Logs: An expandable Console Logs panel with the streamed k6 output. You can search, download, or open it full screen. It lists the built-in k6 metrics, such as http_req_duration with its avg, min, med, max, p(95), and p(99) values, http_req_failed, http_reqs, iteration_duration, and vus.
  • Endpoint Statistics: A per-endpoint breakdown. Each row shows the Endpoint, Requests, Fails, a Latency (ms) bar marking the median (M), 95th (95), and 99th (99) percentiles, the Avg (ms), and the Current RPS. An Aggregated row totals every endpoint.
A k6 run showing the Response Time Histogram, the expanded Console Logs panel with built-in k6 metrics such as http_req_duration and http_req_failed, and the start of the Endpoint Statistics table

The k6 Response Time Histogram above the Console Logs panel, which lists the built-in k6 metrics, and the Endpoint Statistics table below.