Build reporting dashboards

A dashboard is a saved arrangement of charts that you apply to any run. You open the run and the same six charts your team cares about appear in the same layout. You no longer click through tabs every time.

When to build a dashboard

• You have a recurring test and want a health check you can read at a glance.
• You compare runs and want the same axes every time.
• You report performance numbers to a wider audience and want a stable view.

Build a dashboard

1. Open any run in the test you want to track. Switch to the Reporting tab.

   

   The dashboard builder. Add, filter, and arrange charts, then save the layout as a dashboard.

2. Click Add chart. Pick a chart type (line, bar, donut, or radial) and the metric to plot (latency p95, throughput, error rate, virtual users, runner health).

3. Filter the chart by request label, scenario, or location if you need to.

4. Give the chart a clear title and a short description so teammates see what it shows.

5. Repeat for each chart you want to pin. Drag to reorder and resize to fit your screen.

6. Save the dashboard with a name like Checkout — release review or Hourly smoke.

Templates

After you save a dashboard, you can apply it to other runs of the same test. Use the Apply dashboard menu on a run page to switch between dashboards.

You can also pin a default dashboard. Every new run of the test then opens with the same view.

Share a dashboard

Dashboards live at the workspace level. Any teammate who can see the run can see the dashboard. There is no separate sharing step.

Start with three charts

Twenty charts are harder to read than three well-chosen ones. Start with p95 latency by label, throughput, and error rate. Add more only when you keep looking somewhere else for the same number.

Where to go next

• Read run results and logs: what to put on a dashboard and why.
• Schedule recurring tests: combine a schedule with a default dashboard.
• Scenarios and VarioTest: dashboards work across scenarios and child runs.