Build a reporting dashboard

Problem: After a load test, every team member opens the run and configures their own set of charts to check. Some look at p95, some at throughput, some forget to check error rate. Dashboards solve this: one saved layout that everyone applies to every run, ensuring consistent analysis.

Test type: Any — dashboards apply to any run in the test.

Prerequisites

• A MaxoPerf account and a test with at least one completed run.
• A list of the 3–5 metrics your team cares about most (recommended: p95 latency, RPS, error rate, VU count, and one per-label chart for your most critical endpoint).

See Build reporting dashboards for the how-to reference.

Step by step in MaxoPerf

1. Open a run and navigate to the Reporting tab

1. Open any completed run of the test.
2. Switch to the Reporting tab.
3. If no dashboard exists yet, the tab shows an empty canvas with an Add chart button.

2. Add your first chart — p95 latency over time

1. Click Add chart.
2. Chart type: Line.
3. Metric: p95 latency (ms).
4. Filter by label: All labels (or pick your most critical endpoint for a focused view).
5. Title: p95 Latency — all labels.
6. Click Add to dashboard.

3. Add a throughput chart

1. Click Add chart.
2. Metric: Throughput (RPS).
3. Title: Requests per second.
4. Click Add to dashboard.

4. Add an error-rate chart

1. Click Add chart.
2. Metric: Error rate (%).
3. Title: Error rate.
4. Click Add to dashboard.

Start with three, add later

Three charts are enough for a quick health check. Add more only when you find yourself clicking somewhere else on every run — that is the signal that a fourth chart belongs in the dashboard.

5. Add a per-endpoint deep-dive chart

1. Click Add chart.
2. Metric: p95 latency (ms).
3. Filter by label: select the most critical endpoint (e.g. POST /checkout).
4. Title: POST /checkout — p95.
5. Click Add to dashboard.

6. Arrange and save

1. Drag charts into the order that tells the story: throughput first, latency second, error rate third, per-endpoint last.
2. Resize charts to balance the layout.
3. Click Save dashboard and name it — for example Checkout — release review or Nightly regression.
4. Optionally, click Set as default to apply this dashboard automatically to every new run of the test.

7. Apply the dashboard to other runs

1. Open any other run of the same test.
2. Switch to the Reporting tab.
3. Use the Dashboard selector to pick the saved dashboard.
4. The same chart layout appears, populated with that run’s data.

Verify

• The dashboard name appears in the selector on all runs of the test.
• All three (or more) charts populate with data when applied to a completed run.
• If you set the dashboard as default, new runs open to the Reporting tab with the dashboard pre-selected.
• Teammates opening the same run see the same dashboard (dashboards are workspace-level, no separate sharing step needed).

Variations

• Location-filtered charts: create a second dashboard variant with per-region filters to support multi-region run analysis — apply it alongside the global dashboard.
• VarioTest dashboard: apply the dashboard to a VarioTest child run; charts show the scenario-level metrics for that child.
• Pinned comparison view: after a dashboard, use Comparing runs and baselines to put the dashboard-equipped run next to a baseline for delta analysis.
• Scheduled run review: combine a nightly schedule (see Overnight soak test) with a default dashboard so every morning’s review is one click.

Where to go next

• Build reporting dashboards — the how-to reference with full chart type and metric options.
• Comparing runs and baselines — layer the comparison view on top of a dashboard for delta analysis.
• Anatomy of a load test result — what each metric means and how to read it.
• Scheduled regression test — combine scheduling with a default dashboard for automated morning reviews.