Scheduled reports
Schedule recurring analytics summaries and deliver them to email recipients.
A scheduled report emails an analytics summary at a configured interval.
Manage them from Analytics → Export → Scheduled reports…, or from the Operations toolkit.
Report contents
The same measurements the Analytics page computes, over the period the schedule covers:
- checks recorded, and uptime;
- average, P95, and P99 response time;
- incident count, mean time to detect, and mean time to recover;
- a per-region breakdown of uptime and average response time.
Reports cover one organization or monitor over the last 24 hours, 7 days, 30 days, or 90 days. Plain-text and HTML parts use the same calculated figures.
Scheduling
Create a report with a name, period, scope, recipients (up to 20 addresses), and frequency:
- Daily, Weekly on a chosen weekday, or Monthly on a chosen day of the month (1–28, so every month has it);
- at a chosen local hour in the organization's timezone.
The local hour is what is fixed, not the interval: a 09:00 report stays at 09:00 across daylight-saving changes, which means the gap between two sends is 23 or 25 hours across a boundary. If a schedule's hour is skipped by a spring-forward transition, that occurrence is skipped rather than the whole schedule failing.
Delivery
A due schedule is claimed before the report is built, so a slow render or a relay timeout cannot send the same report twice. A failed send is not retried—a report is a snapshot of a period, and delivering a stale one hours later is worse than skipping it. The failure is recorded on the schedule and shown in the manager instead.
Send now makes one schedule due immediately without shifting its future runs.
Reports need the instance mail relay; see Configuration. Without one, schedules can be created but record a clear failure instead of sending.
Recipients are arbitrary addresses, so treat the ability to create a schedule as the ability to mail a report to anyone. Creation and deletion are written to the audit log.