Reports
Understand the output formats generated by Overload.
By default, Overload generates reports in the reports/ directory relative to your current working path. Each report is stamped with a unique run ID (e.g., overload_report_20260530_153021_abc123.html).
HTML Report (Default)
The HTML report is a standalone, single-file document. It embeds all CSS and JS (Chart.js via CDN) so you can easily share it via email or Slack without worrying about missing assets.
Contents of the HTML report:
- KPI Summary: Total requests, Success/Error rates, Avg/P95 Latency.
- Verdict Banner: Shows PASS/FAIL status based on configured assertions, along with a detailed table of which assertions passed or failed.
- Status Codes Doughnut: Visual breakdown of HTTP response codes.
- RPS Stacked Bar Chart: Shows traffic over time, stacked by response outcome (2xx, 4xx, 5xx, Network Errors).
- Latency Timeline: A scatter plot showing the latency of every request over the duration of the test.
- Latency Histogram: Distribution of response times across buckets (e.g., <50ms, <100ms, etc.).
- Request Log: A detailed table of requests, including methods, URLs, status codes, and error messages.
Generate it explicitly using:
overload run --collection api.json --format htmlJSON Export
If you want to feed the results into a custom dashboard, database, or analytics tool, use the JSON format. It outputs the fully computed Stats dictionary.
overload run --collection api.json --format jsonCSV Export
The CSV format writes the raw, unaggregated timeline data. It generates one row per HTTP request dispatched during the test.
Columns: timestamp, request_name, method, url, status_code, latency_ms, error, body_size_bytes
overload run --collection api.json --format csvJUnit XML
This format is specifically for CI/CD integrations. It translates your assertion results into a standard format recognized by GitHub Actions, GitLab CI, Jenkins, and Azure DevOps.
overload run --collection api.json --assert "p95_latency_ms<500" --junit results.xml