Runs — read results

What this is

The Runs surface is where you find and interpret every load-test execution in the workspace. A run is a single execution of a test definition. It captures real-time metrics while active and immutable results when complete. Each run has eight tabs that together give you a complete picture: live charts, per-request metrics, SLA criteria verdicts, runner-level health, an immutable configuration snapshot, error aggregations, raw logs, and downloadable artifacts.

Where to find it

Select Runs in the left navigation sidebar. The page lists all runs in the active workspace. Click Open on any row to go to that run’s detail page.

---

Runs list

The Runs list shows execution history for the active workspace as a paginated table. Columns are Run (name), Test (test name + id), Location (cloud provider and region), Engine, Status (badge with optional failure reason), Started (timestamp in your local timezone), and an Open action link.

Runs list: paginated execution history for the active workspace. Use filters to find runs by status, time range, test, location, or engine.

Filters

Six filter controls appear above the table:

Filter	What it narrows
Search	Run name, id, or test name (substring)
Status	All statuses · Queued · Running · Passed · Failed · Cancelled
Location	All locations · BYOC
Test	All tests or a specific test definition in the workspace
Engine	All engines or a specific Taurus executor
Date range	From / To datetime picker — narrows by run start time

How to use the Runs list

1. Select a workspace using the scope switcher in the top bar — the list is blank without one.
2. Use Status to find all failed runs in the workspace.
3. Use the date range picker to scope to a specific time window (e.g. yesterday’s load-test window).
4. Use Test to see all runs of a specific test definition.
5. Click Open on any row to go to that run’s full detail page.

Failure reason in the list

When a run has failed or been cancelled with a known reason, a short truncated failure reason appears below the status badge. Hover the row to see the full message, or open the run and visit the Overview tab for a full failure explanation callout.

---

Run detail: Overview

The Overview tab is the first tab when you open a run. It shows a live or completed summary of the run’s key performance indicators, health trends, and status.

Run detail — Overview tab: real-time KPI cards, throughput and virtual-user charts, latency distribution, and runner health trend. Refreshes automatically while the run is active.

The Overview tab contains:

Run header — Status badge (Queued, Running, Passed, Failed, Cancelled), linked test name, and the load engine. While a run is active, a Cancel button appears; once complete, a Re-run button appears.

Failure callout — If the run failed, a prominent callout explains the failure reason. It may include a link to the Criteria tab if a criterion was breached.

Runtime secret injection panel — If secrets were bound to the test, the env-var names injected at run start are listed (values are never shown).

Charts — Three charts in a row: Latency overview (p-percentile distribution bars), Throughput (requests/second over time), and Virtual users (active VU count over time). The throughput and VU charts update live while the run is active, following the live tail.

Metric cards — Seven KPI cards across the bottom:

Card	What it shows
Alive runners	Runners alive in the last 60 seconds (fraction of total)
Error rate	Percentage of requests that errored in the selected timeframe
Bandwidth	Network receive (↓) and transmit (↑) in MiB/s
Average response	Mean response time across aggregate samples
Ingestion delay	Average event_time → ingested_at delay across last samples
Max CPU trend	Peak runner CPU percentage in the selected window
Samples	Total Taurus aggregate samples (plus error count if non-zero)

Runner health trend — A chart showing CPU, memory, and network across all matching runners for the selected timeframe, with both max and average lines per metric.

How to use the Overview tab

1. Open a run from the Runs list.
2. Read the status badge and failure callout for a quick pass/fail summary.
3. Watch the Throughput and Virtual users charts to see if the load ramp-up reached the target and held steady.
4. Check Error rate — a non-zero value turns the card red.
5. If the run is live, the charts follow the live tail automatically. Use the timeframe range slider (on the Metrics tab) to zoom in on a specific window.
6. Click Re-run (after completion) to launch a new run from the same test definition.

Live tail overlap

During active runs, the Overview charts apply a small live-tail overlap based on the observed ingestion delay to prevent gaps at the chart’s right edge. The ingestion-delay metric card shows this delay.

---

Run detail: Metrics

The Metrics tab provides a full-featured interactive metrics explorer for this run.

Run detail — Metrics tab: the metrics dashboard builder. Select a dashboard, add chart panels, and filter by location, label, or runner.

Key controls on the Metrics tab:

• Dashboard selector — switch between saved dashboards or create a new one.
• Timeframe range slider — drag the handles to narrow the chart time window. A Reset button returns to the full run span. An Undo button steps back one zoom level.
• Scope filters — filter every chart simultaneously by Location, Label (request label / transaction group), Runner, and Scenario (for VarioTests).
• Chart panels — each panel can display a different metric series. Use the panel controls to pick the metric, change chart type, and set the aggregation.

Metric series names follow the naming conventions of the run’s load engine (k6, JMeter, Taurus). See Engines — Taurus, JMeter, k6 for metric name mappings.

How to use the Metrics tab

1. Open the Metrics tab on any completed or live run.
2. Use the timeframe range slider to zoom into the period of interest (e.g. when error rate spiked).
3. Select a scope filter to isolate data for one location or request label.
4. Click Add panel to add a new chart — pick the metric from the selector.
5. Save the arrangement as a dashboard to reuse across future runs.

For a full step-by-step guide, see Build reporting dashboards.

---

Run detail: Criteria

The Criteria tab shows the per-criterion evaluation status when failure criteria were defined on the test at run time.

Run detail — Criteria tab: traffic-light verdict for each SLA gate defined on the test. Breached criteria show the observed value, threshold, and breach timestamp.

Each criterion row shows:

Field	What it shows
Status badge	ok (green), breached (red), pending (grey), or skipped (muted)
Summary	Human-readable description of the criterion
Observed value	The actual measured value at evaluation time
Threshold	The configured SLA limit
Window	The evaluation window (e.g. “last 30 seconds”)
Stop source	The runner that triggered an early stop, if applicable
Breached at	The timestamp when the criterion was first breached

Criteria tab visibility

The Criteria tab is only visible when the test had at least one failure criterion defined at the time the run was created. If the tab is not visible, no criteria were configured — go to the test’s Configuration tab to add them.

How to read criteria results

1. Open the Criteria tab after a run completes.
2. A breached row means the run failed the SLA gate for that criterion — check the observed value vs. threshold.
3. A pending row means the criterion was not evaluated (typically because the run did not reach the evaluation window).
4. A skipped row means evaluation was skipped (e.g. not enough data for the configured window).

---

Run detail: Runner status

The Runner status tab provides a detailed roster of every runner allocated for this run.

Run detail — Runner status tab: per-runner lifecycle view. Filter by status, engine, or location. Pin runners to scope charts on the Overview and Metrics tabs.

Each runner row shows:

• Status badge (Booting, Starting, Running, Stopped, Failed)
• Location — cloud provider and region, or private datacenter name
• Engine — the load engine that ran on this runner
• Exit code — the process exit code on termination
• Lifecycle timestamps — when the runner started and stopped
• Health drawer — expand to see CPU, memory, and network trends for just this runner

Filter controls let you narrow by runner status, engine, or location. You can also pin specific runners — pinned runners are used as the scope filter on the Overview and Metrics tabs, letting you isolate charts for a single runner.

How to use the Runner status tab

1. Open the Runner status tab.
2. Use the status filter to find any runners that failed during the run.
3. Check the exit code of failed runners — a non-zero code indicates the runner process crashed or the engine reported an error.
4. Click a runner row to expand the health drawer and inspect CPU and memory for that runner.
5. Pin a runner to scope the Overview charts to just that runner’s traffic.

---

Run detail: Configuration

The Configuration tab shows the immutable test configuration snapshot captured when this run was created.

Run detail — Configuration tab: the exact test definition this run used, frozen at creation time. Use this to audit exactly what ran.

The snapshot is read-only and is divided into sections:

Configuration snapshot — Test name and id, project, workspace, detected engine, private datacenter (or “Managed cloud”), and the capture timestamp.

Validation — The engine validator result (pass / fail / pending) at snapshot capture time, including the reason text if validation failed.

Load profile — The exact virtual-user target, runner count, ramp-up, stop mode (duration or iterations), max VUs per runner, and target RPS that were used for this run.

Location plan — The managed regions and private datacenter ids used, plus a per-row table of runner counts and weights.

Files — The list of test files (filename, role, content type, size, SHA-256 checksum) captured at run time. Each row has a Download button to retrieve the original file.

Legacy runs without a snapshot

Runs created before immutable snapshot capture was introduced show an “Snapshot unavailable” empty state. An Open current test configuration link takes you to the live (editable) configuration on the test page.

How to use the Configuration tab

1. Open the Configuration tab to audit exactly which files, load settings, and locations were used.
2. Compare Load profile values across multiple runs of the same test to confirm consistency.
3. Click Download on a file row to retrieve a copy of the exact script that ran.

---

Run detail: Errors

The Errors tab aggregates HTTP or engine-reported errors into a searchable, groupable table.

Run detail — Errors tab: aggregated error rows from the run. Group by label or error key to surface the most impactful failure classes.

The tab shows:

• Summary bar — total error sample count and distinct row count for the active filters.
• Search — filter rows by label, error key, source, or sample message text.
• Group by — collapse rows by label or by error key to see which error class contributed the most samples.
• Table — columns: Label (request label), Error (error key / HTTP status), Source (JMeter error sample or Taurus LDJSON), Count (sample count), First seen, Last seen, Sample (a representative message).

Error rows are scoped by the global timeframe, location, label, runner, and scenario filters set on other tabs.

How to use the Errors tab

1. Open the Errors tab after a run completes or while it is running.
2. Read the summary bar to understand the error volume.
3. Use Group by label to find which request endpoint generated the most errors.
4. Use Group by error to find the most common error type (e.g. “Connection timeout”).
5. Search for a specific error message or label to focus on a known issue.
6. Switch to the Metrics tab to see a charted error-rate trend over time.

Scoped by global filters

The error table respects the location, label, runner, and scenario scope filters set on the Metrics tab. Clear or adjust those filters if you see fewer error rows than expected.

For a deep dive into debugging error responses, see Inspect error response bodies.

---

Run detail: Logs

The Logs tab streams real-time log output from all runners and the platform during the run.

Run detail — Logs tab: real-time (or historical) log output from engine and system streams. Filter by severity and stream, and search by message text.

Filter controls at the top:

Control	Options
Stream	All streams · System (platform-api log lines) · Engine (runner log lines)
Severity	All · Info · Warn · Error
Find	Text search across all visible log lines

Log lines show timestamp (UTC), severity level, message text, stream label, and source identifier (runner id or platform-api). While a run is active, new lines are loaded as you scroll down (infinite scroll with a live-tail sentinel).

How to use the Logs tab

1. Open the Logs tab during or after a run.
2. Select Engine stream to see only the load-engine output (Taurus / JMeter / k6 stdout).
3. Select System stream to see platform-level events (runner provisioning, secret injection, finalize).
4. Filter by Severity → Error to jump straight to error-level lines.
5. Use Find to search for a specific URL, label, or error message.
6. Scroll to the bottom to load more historical lines.

Log retention

Logs are retained for a limited period. For long-term audit trails, download the log artifact from the Artifacts tab before retention expires.

---

Run detail: Artifacts

The Artifacts tab lists all output files generated by runners during the run — JMeter JTL files, k6 JSON summaries, custom engine output, and platform-level archives.

Run detail — Artifacts tab: downloadable output files from all runners, grouped by runner. Status badges indicate ready, uploading (live), failed, or discarded.

Artifacts are grouped by runner. Each group header shows the runner id and a per-runner file table. A Run-level group at the end contains platform-generated files (e.g. compressed log archives). Table columns:

Column	What it shows
File	Filename (truncated with tooltip)
Kind	Artifact category (e.g. result, log, custom)
Source	The runner or engine instance that produced the file
Status	Ready (downloadable), Live (uploading with committed bytes), Finalizing, Failed, or Discarded
Size	File size in bytes / KiB / MiB / GiB
Updated	Last updated timestamp
Download	Download button (enabled when status is Ready or Live)

Filters above the table let you narrow by search (filename), kind, and source.

How to download artifacts

1. Open the Artifacts tab after a run.
2. Find the file you want — use filters to narrow by kind or source.
3. Click Download on any row with status Ready or Live.
4. To download multiple files at once, check the rows you want and click Download selected — a ZIP archive is generated in the browser.

Live artifacts

While a run is active, artifacts in “uploading” status with committed bytes show as Live and are already downloadable. You do not need to wait for the run to finish to retrieve a partial JTL or log file.

Batch download limit

Only artifacts with Ready or Live status can be batch-downloaded. Non-ready items in a batch selection will block the download — deselect them first.

---

Tips & gotchas

• Live vs. completed runs. While a run is active, the Overview and Metrics charts follow the live tail. Filters and timeframe controls still work during live runs. Once the run completes, all data is frozen and the timeframe defaults to the full run span.
• Criteria tab only appears when criteria exist. If the test had no failure criteria at run time, the Criteria tab is hidden. Add criteria on the test’s Configuration tab for future runs.
• Runner status tab is blank for older runs. The Runner status tab requires runner telemetry to have been emitted. Very short or very early-stage runs may show no runner rows.
• Error counts vs. error rate. The Errors tab shows raw error samples (individual request failures). The error rate (percentage) is on the Overview metric card and Metrics tab charts. High error sample counts can still mean a low error rate if overall volume is high.
• Configuration snapshot vs. current configuration. The Configuration tab shows what ran — the immutable snapshot. The live editable configuration is on the test’s Configuration tab. These diverge if the test was modified after this run was created.
• Artifact status “Discarded”. Discarded artifacts were intentionally not retained (e.g. the runner shut down before the file was fully committed). Check the failure reason in the status tooltip.
• Cancelling a run. Two cancel modes are available from the run header: Graceful (runners drain final data and release capacity) and Kill (capacity is removed immediately; final samples may be incomplete). Graceful is preferred unless you need to stop immediately.

---

Related docs

• Tests and runs — what a test and run are, and how they relate.
• Engines — Taurus, JMeter, k6 — engine-specific metric names and artifact formats.
• Read run results — a task-oriented walkthrough of interpreting a completed run.
• Run your first test — end-to-end walkthrough from test creation to reading results.
• Build reporting dashboards — saving and sharing Metrics dashboard layouts.
• Inspect error response bodies — debugging specific HTTP errors from run data.
• Tests — create and configure — creating the test definition that generates runs.
• Navigating the console — shell, Dashboard, and navigation reference.