An on-call rotation or escalation contact is named

The design says who is reached, and how, when the service breaks outside office hours.

HighChecked automatically

Applies to:
Every service
Rule id:
ownership.oncall-set

Why it matters

An alert that reaches nobody is not an alert. Callers of your service need to know where to escalate when it misbehaves, and they need to know before the incident, not during it.

How to apply it

  • Name the rotation or the escalation path, not an individual: a paging service key, a rotation name or a shared channel that is watched.
  • Make sure the rotation has at least two people, so that being on call is survivable.
  • State the expected response time if it differs from your organization's default.

Example

owner.oncall: payments-primary rotation, 15 minutes to acknowledge, escalates to payments-secondary.

References

Checklists with this rule

Related agent skill: team-topologies-ownership

  • An owning team is named

    One team owns the service end to end, and the design says which.

    CriticalChecked automatically

  • A runbook exists

    The service has written steps for its most likely failures, so the person on call does not start from zero.

    HighChecked automatically