Fill Four On-Call Lists Before You Accept the Rotation

说明与用途

轮班现在以完整的目录、只读的首次命令脚本、定义好的升级时钟和数据包以及冻结规则开始，防止即兴操作并提高安全性。

问题

On‑call rotations often start without fully defined runbooks, leading to improvisation, unclear escalation paths, and unsafe write permissions.

结果

Rotations now have auditable, immutable runbooks that prevent accidental writes, clarify escalation paths, and reduce on‑call uncertainty.

工作流

• 1. Verify every alert ID in the past month has a catalog entry, including a "not this" note.
• 2. Ensure each catalog row points to a read‑only first‑command script on disk.
• 3. Define escalation roles, minute bounds, and packet fields in escalation.yaml.
• 4. Set freeze_on_unknown_alert to true so unknown IDs trigger a freeze until a human edits the catalog.

证据

I keep the on‑call file as four lists because each list answers a different failure.

来源

Unknown IDs freeze writes immediately; unfreeze is a filled sentence, not a vibe.

来源