Status
Monitoring and incident management. Configure monitors, route alerts to on-call responders, manage incidents, and publish service status.
Getting started
Topics
- Monitor servicesMonitor types, check execution, and failure criteria.
- Respond to incidentsDeclare, assign, update, resolve, and review.
- Alerting channels and routingNotification channels and routing rules.
- Publish a status pagePublic service health and incident updates.
- Schedule maintenanceMaintenance windows and check suppression.
- Automation APIAPI authentication, endpoints, and requests.
Status documentation covers monitoring, incident response, administration, and deployment. Start with Getting started for setup or Common tasks for console procedures.
Connector support begins at Status general availability. Pre-release Status installations do not provide Connector enrollment.
Choose by role
The table lists tasks, documentation, and required access.
| Task | Start with | Typical access |
|---|---|---|
| Check health or read history | Common tasks | Viewer or above |
| Create and troubleshoot checks | Monitoring | Member or above |
| Coordinate an outage | Incidents | Member or above |
| Tell customers what is happening | Status pages | Member or above |
| Plan expected service work | Maintenance | Member or above |
| Manage people and workspace policy | Roles, members, and teams | Admin or owner |
| Automate or integrate Status | Automation API | Admin creates keys; access also depends on key scopes |
| Install or operate the platform | Self-hosting | Deployment administrator |
If a button described in a guide is missing or disabled, first confirm that you are in the intended organization and environment, then check your role. Viewers can inspect information but cannot change organization records.
Monitor and investigate
- Monitoring
- Monitor workbench
- API sequence monitoring
- Monitor configuration history
- Monitor schedules
- Monitor taxonomy and ownership
- Monitor templates and recipes
- Bulk monitor actions
- Import, export, and clone monitors
- Transfer a monitor to another organization
- Monitoring agents
- Run monitor workers
- Monitor credentials and secrets
- Analytics
- Custom dashboards
- Custom DNS resolvers
- IPv4 and IPv6 availability
- Per-monitor outbound proxies
- Custom certificate authorities
Respond and coordinate
- Incidents
- Incident work and deployment correlation
- Comments and mentions
- Message templates
- Automatic severity rules
- Automatic grouping and reopening
- Postmortems
- External alerts
- Alerting channels and routing
- On-call schedules
- Escalation policies
- Service level objectives
- Deployment events
Communicate
- Status pages
- Status-page subscriptions
- Maintenance
- Maintenance calendar
- Maintenance templates
- Notification center
- Scheduled reports
Manage the workspace
- Operations toolkit
- Roles, members, and teams
- User profiles, account, and preferences
- Searchable audit log
- Recycle bin
- Monitor-result retention
- Scoped API keys
- Automation API
Install and operate Status
- Self-hosting
- Configuration
- Setup health and observability
- Backup and restore
- API rate limits
- Prometheus metrics
- Cloud platform policy
Reader conventions
Console paths use Section → Action. API paths use code formatting. Unless an article says otherwise, console and management API operations apply only to the active organization. Viewer, member, admin, and owner permissions are described in Roles, members, and teams.
Legal and policies
Review the Status legal and policy section for terms, acceptable use, privacy, data processing, billing, security, and service commitments.