Main Concepts#
IncidentRelay resources are organized around groups, teams, services, rotations, routes and channels.
| Concept | Description |
|---|---|
| Group | Access boundary and group-level administration scope |
| User | Person who can log in, be on-call, receive notifications or use personal API tokens |
| Team | Operational unit inside a group |
| Rotation | On-call schedule for a team |
| Route | Incoming alert routing rule with its own intake token |
| Service | Logical affected system such as API, database, queue, website or infrastructure component |
| Business service | Business Services describe customer-facing or business-facing capabilities that depend on one or more technical services. |
| Escalation policy | Escalation policy |
| Channel | Outgoing notification destination |
| Alert | Alert created or updated by an incoming integration |
| Silence | Temporary rule that suppresses notifications for matching new alerts |
| Override | Temporary replacement in a rotation |
Recommended reading order:
- Groups and RBAC
- Route Intake Tokens
- Channels
- Reminders and Escalations
- Escalation Policies
- Business services
For domain-specific workflows, continue with: