ChatOps and war rooms
Provider-backed collaboration spaces linked to incidents.
War rooms and service channels project incident state into supported collaboration providers. The incident remains authoritative; provider messages, action cards, and membership are managed projections with reconciliation and cleanup behavior.
Interactive actions in Slack and Microsoft Teams are governed by the central ChatOps action contract. Actions are capability-gated and phase-bound: for example, manual escalation is exposed only on active open incidents in Microsoft Teams and is omitted once an incident is acknowledged or resolved. Slack performs direct lifecycle transitions without web modal forms.
Provisioning creates or links a provider room, stores its durable identity, and publishes incident updates with idempotent delivery keys. Provider rate limits, permission changes, and deleted rooms can make the projection temporarily unavailable without changing the incident itself.
Treat room membership and message history according to the provider's retention and access controls. Archive or reconcile rooms through OpsKnight so internal links and provider state do not diverge.
Last updated for v2.1.0
Edit this page on GitHub