Skip to main content
Analytics in Rootly answers three kinds of questions: how is our incident response performing, where is the on-call load falling, and what’s changing over time. Every workspace starts with three default dashboards. From there, you build custom panels around the questions your team actually asks in reliability reviews.
Analytics uses seat-based access. On-Call seats see alert-response metrics; Incident Response seats see incident, retrospective, action item, and user metrics on top of that.

​
In This Section

Default Metrics

The three built-in dashboards — Incident Response, Workload, and On-Call Metrics — and every panel that ships with them.

Managing Dashboards

Create, share, duplicate, and set default dashboards. Ownership, permissions, and public link behavior.

Customizing Dashboards

Panel types, filters, groupings, multiple datasets, operations, and export formats.

Dashboard API

Programmatic access to dashboards and panels via the Rootly API.

​
The Three Default Dashboards

Every workspace ships with three curated dashboards. Each is a starting point — clone and specialize whenever a team needs its own view.

Incident Response

Incident volume, MTTx response times, and breakdowns by severity, environment, service, functionality, and type.

Workload

Hours worked across incidents and responders. Useful for spotting responder burnout and load imbalance.

On-Call Metrics

Alert volume, MTTA, MTTR, MTBF, acknowledge rate, and alerts broken down by source, responder, and urgency.
Full panel-by-panel reference is on the Default Metrics page.

​
How It Works, Briefly

Every panel combines seven pieces: a display type, a collection (Incidents, Alerts, Retrospectives, Action Items, Users), filters, an aggregation operation (Count, Average, Sum), a metric key, an optional Group By, and one or more datasets. Dashboards apply dashboard-level filters (date range, period, team, service — saved per user) on top of any panel-level filters built into each panel. Results cache for about 15 minutes to keep dashboards responsive on large datasets. For the full model, see Customizing Dashboards → How Panels Work.

​
Sharing Dashboards

Rootly supports four ownership types (private, team, organization, public) and four permission roles (viewer, editor, manager, admin). Public dashboards render at /public/dashboards/… — read-only, no login required — gated by a boolean visibility flag on the dashboard rather than per-viewer tokens. See Managing Dashboards → Dashboard Ownership and Visibility for the ownership matrix and Sharing and Permissions for the permission roles.

Retrospectives

Retrospective processes, templates, and Rootly AI drafting. Retrospective completion feeds several default metrics.

Custom Fields

Custom fields become filterable and groupable panel dimensions once enabled for their collection.

Alert Statuses

Alert lifecycle drives the On-Call Metrics dashboard — MTTA, MTTR, acknowledge rate, and MTBF.

Rootly API

Programmatic access to dashboards, panels, incidents, alerts, and every other Rootly object.

​
Frequently Asked Questions

Three: Incident Response, Workload, and On-Call Metrics. Every workspace gets them on creation. Clone and specialize whenever a team needs its own version.
Yes. Chart panels support multiple datasets, each with its own collection, filters, operation, and key. Overlay incident and alert trends on one time axis to compare volume patterns.
Panel results are cached for ~15 minutes. Very recent changes may take that long to reflect — especially with auto-refresh enabled.
Dashboards export as PDF. Individual panels export as PDF, CSV, or JSON; chart panels also export as PNG and JPG. See Customizing Dashboards → Exporting.
Yes. The Rootly API exposes dashboards and panels — list, create, read, update, duplicate, and default-set. See the API Reference.