SYSTEM Cited by 1 source

OpsGenie¶

OpsGenie is Atlassian's on-call scheduling + paging SaaS (formerly an independent company; acquired by Atlassian in 2018). Canonical wiki mention is its role as the on-call-team directory of truth whose team list Zalando uses to auto-generate the directory structure for its incident- playbook repository.

Role¶

OpsGenie provides:

On-call rotation schedules per team.
Paging routes — alert → on-call person, with escalation policies.
Team + service metadata — who owns what, who gets paged when.

Zalando's use case on the wiki is the team-metadata interface: Zalando's incident-playbook repository's directory layout is generated from OpsGenie's on-call-team list, so every team has a pre-seeded skeleton directory to contribute playbooks into.

The "directory structure auto-generated from on-call teams"¶

pattern¶

Verbatim framing:

"We use documentation site built using mkdocs to host the documentation containing a description of the incident process and all playbooks. We generate the playbook directory structure based on our OpsGenie on-call teams. This way there is always a skeleton available for every team to contribute their playbooks to." — sources/2023-01-30-zalando-how-we-manage-our-1200-incident-playbooks

The load-bearing property is OpsGenie-as-source-of-truth for team identity. Any on-call team at Zalando exists in OpsGenie (because that's where paging is configured); every such team therefore also exists in the playbook repo (because the directory is generated from the same list). New team → both appear; retired team → both disappear. No per-repo curation.

OpsGenie as example, not deep-dive¶

The source post names OpsGenie to explain where the directory list comes from, not to deep-dive OpsGenie's internals. The generalisation in patterns/playbooks-as-markdown-with-codeowners is: "any on-call-management system that exposes a team directory" can play OpsGenie's role — PagerDuty, VictorOps (Splunk On-Call), internal paging platforms, etc.

Seen in¶

Zalando incident playbooks (2019-present) — sources/2023-01-30-zalando-how-we-manage-our-1200-incident-playbooks — source of the on-call-team list used to generate the playbook-repo directory structure. Canonical wiki instance.

concepts/incident-playbook — the artefact whose directory OpsGenie grounds.
concepts/alert-fatigue — the operator-side risk on-call paging tools accumulate.
patterns/playbooks-as-markdown-with-codeowners — the pattern that uses OpsGenie's directory.
companies/zalando — axis 28.
companies/atlassian — current owner.