Alerts and reports · 4 of 4
Reports and the weekly digest
Uptime per service, host and check, incidents with time to acknowledge and fix, disks with a forecast of when each fills, certificates, mail and backups, over a week, a month or any month. CSV, PDF and a weekly digest.
The Reports page covers the last 7 or 30 days, or any month:
- Uptime per service, host and check. Down is time spent critical; degraded is time spent at warning or serious.
- Incidents people were told about, with the time to acknowledge and to fix, and the cause, which operators and admins write.
- Certificates by when they end.
- Disks, with a straight-line forecast of when each one fills.
- CPU and memory per host, per day.
- Mail: the monitor's rounds and any time on a block list.
- Backups.
Every section downloads as CSV, and printing the page gives a clean PDF.
What's kept
Once a minute obs-beacond writes each service's, host's and check's status when it changes (so a year stays small), and an hourly sample per host: CPU and memory, average and peak, and every disk's use. History older than 400 days is dropped.
While obs-beacond is down nothing is known, so uptime counts only the time Cairn OBS was watching.
The weekly digest
Once a week Cairn OBS sends a summary of the last seven days: what's wrong now, uptime (services below 100% by name), incidents, backups, certificates ending within 30 days, disks filling within 90, and mail. Email gets the whole text; chat channels get a line and a link.
reports:
timezone: Europe/Berlin # where days and months start; default the server's
digest:
weekday: monday
at: "08:00"
channels: [mail] # alert channel ids; default every email channel
It's sent once a week even across restarts. Admins can preview it, and send it by hand, on the Reports page.
reports.timezone is also what the Reports page shows times in, and the
"Since" time in alert notices.