Features & Implementation¶
This section describes what SLAtus does and how each feature is implemented. Each page names the relevant tables, modules and decisions, so developers can follow the code, and gives enough context for operators to understand the behavior.
| Feature | Summary | Page |
|---|---|---|
| Status model | Active status windows per service; the basis of uptime and SLA figures | Status model |
| Incidents & maintenance | Incident lifecycle with timeline, internal notes, planned maintenance windows | Incidents & maintenance |
| SLA & availability | Service-level plans, holiday lists, availability metrics, SLA reports and exports | SLA & availability |
| Uptime checks | Automatic HTTP checks that set statuses and measure response times | Uptime checks |
| Notifications & subscriptions | E-mail, webhook, SMS and web push with double opt-in, rate limiting and per-channel control | Notifications & subscriptions |
| Public page & integrations | Public UI, visitor time zone, themes, languages, badge, RSS, legal pages | Public page & integrations |
Feature overview¶
- Public status page with an overall banner, key figures, component groups, 90-day uptime bars, active incidents and outages, maintenance, and a paginated history of the last six months
- Service detail page with an availability table over eight periods, plus monthly and quarterly SLA bars
- A time zone toggle for visitors and an adapted layout on phones
- Incidents with timeline, affected services, exact outage times and post-incident review
- Planned maintenance windows that automatically show as "under maintenance" and are completed at their scheduled end
- Automatic uptime checks per service, with a configurable interval, failure thresholds and a pause
- SLA plans with weekday time windows, holiday lists, per-service targets and SLA reports with a confirmation workflow
- SLA report exports as PDF and Excel, per report or per service, as draft or final, plus ad-hoc exports without a stored report
- Notifications over four channels, with per-component mute switches and a rate limit on the public forms
- Admin interface with role-based access, audit log, API tokens, and English and German public UI