Analytics and cost/Analytics/Scheduled reports
Scheduled reports
Regular digests of operational data, by email or Slack.
Analytics → Scheduled Reports sends recurring digests.
Configuring
| Field | Notes |
|---|---|
| Content | Which dashboards, metrics or analytics |
| Schedule | Daily, weekly, monthly |
| Recipients | Email addresses or a channel |
| Format | Inline summary, PDF, CSV |
| Range | The period covered |
What works
| Report | Cadence | Audience |
|---|---|---|
| Alert volume and response times | Weekly | The team |
| SLO status and budget burn | Weekly | Engineering leadership |
| Deploy frequency and failure rate | Monthly | Leadership |
| Top error groups | Weekly | The owning team |
Making one people read
- Lead with what changed, not with a table.
- Include the comparison. A number without one is not information.
- Keep it short. A weekly report that takes ten minutes to read gets skimmed after three weeks and ignored after six.
- Send it when it will be read. Monday morning, not Sunday night.
Tip
If a report is never discussed, stop sending it. An unread report costs attention every week and provides nothing — and its existence lets everyone believe the topic is covered.
Related
- KPI reports — the same idea for warehouse business data
- Release digest — weekly release notes
Where this behaviour lives: backend/internal/worker/report_worker.go, frontend/src/app/reports/. If the code and this page disagree, the code is right — please fix the page.
Part of Analytics and cost — Dashboards, SLOs, reports and what the infrastructure costs.