Reading Results
Every run has a dashboard. Open it from a project's Results tab, or from the test list at /<project>.
The dashboard refreshes itself while a test is running, so you can leave it open from start to finish.
Headline numbers
| Status | Whether the test is still running |
| Test Started | When it began |
| Duration | How long it has been running, or ran for |
| Max Users | The peak number of concurrent users, added up across every machine |
| Req/sec | Throughput |
| Avg Response Time | Average across the whole test |
| Error Rate | Failed requests as a percentage of all requests, across the whole test |
Max Users counts every machine
Each load generator reports its own thread count, and Atlas adds them up. If you ran a 100-thread plan on 5 machines, expect roughly 500 — if it shows 100, something stopped four of your generators from producing load.
Average response time and error rate are whole-test figures, not the last few seconds, so they won't jump around as the test finishes.
The chart
Three series on one timeline:
- Active Users (green, right axis) — concurrency over time
- Avg. Response Time (blue, left axis) — how the system responded as load grew
- Error Rate % (red) — when things started failing
Read together, these tell you where your system's limit is: the point where response time climbs and errors begin while users are still increasing.
The aggregation report
One row per request, grouped by thread group, with count, response times (average, median, percentiles, min/max), throughput and error percentage.
Every column sorts. Rows are colour-coded:
| TOTAL | The whole test |
| Thread group | One per thread group in your plan |
| Transaction | A named step, if your plan uses Transaction Controllers |
| Request | An individual HTTP request |
TIP
The same sampler name in two different thread groups stays two separate rows, attributed to the right group — so a shared "login" step used by several groups doesn't get merged into one misleading number.
Drilling in
- Click an Error % — opens a panel listing the actual errors for that request: response codes and messages, with the full request and response for each distinct failure.
- Click a Label — opens the same chart filtered to that one request, so you can see whether a single endpoint degraded while the rest stayed healthy. There's an error-type dropdown to isolate one specific failure.
Exporting
↓ Export Excel downloads the run as a spreadsheet with the chart and the full table, colour-coded to match. Useful for attaching to a report.
Dark mode
Add ?theme=dark to any dashboard URL.
Comparing runs
There is no side-by-side comparison view yet. Name your runs (in the Results tab) so you can tell variations apart, and export to Excel to compare them outside Atlas.