OpsKnightChange coverage without rebuilding the rotation.
Use an override for planned leave or a last-minute swap. Review its time window and validate that the intended responder owns the affected interval.
Read the operational guideON-CALL & ESCALATION
Know who’s responsible before something breaks.
Build rotations, schedule overrides and escalation policies around the people responsible for each service.
WHAT IT SOLVES
A schedule is a promise of ownership.
Build rotations around real team availability, time zones and coverage. Verify the effective on-call responder instead of relying on how a calendar looks.
Understand the capability01Timezone-aware rotations
02Temporary overrides and handoffs
03User, team and schedule escalation targets
OPSKNIGHT / PRODUCT VIEW Northstar Systems · v2.0.0
HOW IT WORKS
A concrete operational path, not a feature list.
EFFECTIVE RESPONDERResolve ownership at execution time, not from how a calendar happens to look.
01Service
02Policy
03Schedule
04Rotation
05Responder
EXPLORE A WORKFLOW
- 01Service
- 02Escalation step
- 03Effective rotation
- 04Responder
Schedules resolve the responder at execution time. Inspect coverage in the intended time zone.
OPERATIONAL DEPTH
On-call & escalation, beyond the happy path.
The details below are the parts teams need when evaluating how the capability behaves during real response, failure, and handoff.
Primary, backup, and a viable final target.
An escalation step can target a user, team or effective schedule. Set explicit delays and channels, then test unavailable users and empty schedules before relying on the policy.
Read the operational guideMake the handoff deliberate.
Review active incidents, current ownership and incoming coverage together. A schedule transition is an operational handoff, not a guarantee that every open incident was understood.
Read the operational guideTest the page before you need it.
Validate the selected responder, healthy endpoints and delivery evidence with a synthetic incident. A saved schedule alone does not prove an end-to-end page.
Read the operational guideKNOW BEFORE PRODUCTION
Validate the boundary, not just the happy path.
Use a test service and representative provider configuration before treating on-call & escalation as production incident infrastructure.
Capability-enabled Microsoft Teams cards; no manual escalation control in Web or standard Slack incident actions.
- 01Verify the effective responder across the intended timezone and a DST boundary.
- 02Test an override plus an empty-schedule condition before relying on the rotation.
- 03Run a synthetic incident through escalation and inspect delivery evidence.
DOCUMENTATIONSetup, authorization, limits, and troubleshooting.
Explore on-call & escalation documentationYour incidents should belong to you.
Run OpsKnight on infrastructure you control.
v2.0.0 · AGPL-3.0-only · Self-hosted · 28 inbound integrations