Reports
A report sends a digest of some monitors’ latest results on a schedule: a daily operations summary in Slack, a weekly reliability review by email.
Creating a report
Section titled “Creating a report”On Reports, create a report with:
| Field | What it does |
|---|---|
| Name, Description | How it shows in the list and in the message. |
| Schedule, Time zone, Cron expression | When it is sent. Five cron fields: minute, hour, day of month, month, day of week. |
| Monitors | The monitors the report covers. |
| Send to | Channels that can carry a message (below). |
| Format | Summary: one line per monitor, its latest status and how many runs failed. Detailed: also its latest rows, series and flow steps. |
| Runs counted | Latest only, or Every run since the previous report, so failures between two digests show up. |
| Enabled | A paused report keeps its settings; Send now still works. |
Channels that carry reports
Section titled “Channels that carry reports”Email, Slack, Microsoft Teams, Discord, Google Chat, Telegram, AWS SNS and webhooks. PagerDuty and Jira are for alerts only, and a report can’t be sent to them.
Sending
Section titled “Sending”- Reports are sent by SREInsights’ background worker at their scheduled time.
- Send now on the report queues one at once.
- Every run of a report records what went to which channel. Open the report to see its runs.