Skip to main content
Reports show how reliable a project was over a time window. Each report compares the window with the previous window of the same length, so you can see if response and uptime get better or worse.

​
Open a report

  1. Open your project and select Reporting in the sidebar.
  2. Select a report. Reports are grouped in sections (see Reports).
  3. Select a range: 7d, 30d, 90d, or Month to date.
  4. On a monitor-based report, select a monitor to show only that monitor.
Each report has three parts:
  • KPI cards. Each card shows the value for the window and the value for the previous window of the same length.
  • One chart. Select the bucket size: hour, day, week, or month, when the report supports it. Buckets use your time zone.
  • One table. Each row links to its incident, monitor, or issue. You can export the table as a CSV file.
A preset range starts at midnight in your time zone. For example, 7d is today and the six days before it. Through the API, you can also give an explicit window of up to 400 days.

​
Reports

The monitor filter is on every report except Manual incidents and Issues.

​
How Squasher measures incidents

A report counts the incidents that opened in the window. An incident that opened before the window is not in the report, even when it was still open. MTTA, MTTI, and MTTR use only the incidents that reached that point. For example, an incident that is not resolved is not in MTTR. The MTTR, MTTA, and MTTI reports also show the median and the P90.

​
How Squasher measures uptime

SLA and Heartbeats calculate uptime as healthy checks out of all checks that ran. Checks do not run while a monitor is paused, so a paused time does not lower uptime. SLA covers every monitor except heartbeat monitors. Heartbeats covers only heartbeat monitors. These two reports read daily check counts for each monitor. The days are in UTC, so these reports use UTC and support only day, week, and month buckets. Response time shows the average and the P95 latency of checks. Squasher samples about one check every 5 minutes for each monitor.

​
How Squasher measures escalations and issues

Escalations counts the on-call pages that started in the window. It shows the number of pages, the mean time to acknowledge a page, the pages that nobody acknowledged (exhausted pages), and the texts and calls sent. The table has one row for each escalation policy, with its pages, acknowledged pages, time to acknowledge, unanswered pages, highest level reached, and notifications. Issues counts new issues by first seen time and resolved issues by resolution time. The mean time to resolve goes from first seen to resolved.

​
Limits

When a report reads only the first 5,000 records, the API response sets truncated to true. Use a shorter window to get exact numbers.

​
Permissions

You see a report only if you can read its data:

​
Use reports from the API and the CLI

See the Reports API for all parameters and the response shape.

​
Next steps

Reports API

Read reports from a script or an agent.

On-call escalation

Page responders until someone acknowledges.

Uptime monitors

Check endpoints and open incidents when they fail.

Notifications

Send incidents to the channels your team watches.