OpsKnightKeep actions attached to the incident.
Provider cards project incident context and supported actions. Identity links, product permissions, provider capabilities and lifecycle phase determine which actions can run.
Read the operational guideCHATOPS
Response belongs in the room.
Coordinate incidents in Slack and Microsoft Teams with incident actions, linked identities and war rooms.
WHAT IT SOLVES
Choose the conversation that owns the response.
Create an incident-scoped Slack or Microsoft Teams war room manually, or use the effective global/service policy for automatic creation. One destination should own automatic room creation for a service.
Understand the capability01Acknowledge, assign and resolve
02War rooms and participant synchronization
03Service destinations for Slack and Teams
PRODUCT WORKFLOWChatOps
Coordinate incidents in Slack and Microsoft Teams with incident actions, linked identities and war rooms.
HOW IT WORKS
A concrete operational path, not a feature list.
ONE INCIDENT / TWO COLLABORATION PROVIDERS
Slack. Connected to the incident.
Provision a room, project incident context, coordinate the response and reconcile provider drift.
Standard Slack incident actions do not expose manual Escalate. Supported lifecycle actions remain permission- and phase-bound.
- Confirm destination and identity links
- Create or reconcile the recorded room
- Verify projected state and authorized actions
- Resolve and complete provider cleanup
SlackINCIDENT COLLABORATION
P1
Checkout API latencyNorthstar Systems · Commerce Reliability
ACKNOWLEDGEASSIGNRESOLVE
Identity + permissions checked before actionOpsKnight remains system of record
OPERATIONAL DEPTH
ChatOps, beyond the happy path.
The details below are the parts teams need when evaluating how the capability behaves during real response, failure, and handoff.
Policy before provisioning.
Service policy overrides the global default. Validate the effective destination and permissions with a new incident; changing policy does not migrate an already provisioned room.
Read the operational guideReconcile drift instead of creating duplicates.
Inspect the durable room and operation identity when provisioning times out, membership changes or a card is stale. Retry or reconcile the existing operation before attempting another room.
Read the operational guideClose the response with the conversation.
Resolve the incident, verify terminal context and close or archive the room through supported controls. Provider retention and cleanup capabilities determine the final room behavior.
Read the operational guideKNOW BEFORE PRODUCTION
Validate the boundary, not just the happy path.
Use a test service and representative provider configuration before treating chatops as production incident infrastructure.
Capability-enabled Microsoft Teams cards; no manual escalation control in Web or standard Slack incident actions.
- 01Verify linked identities and OpsKnight permissions for each collaboration provider.
- 02Test room provisioning, reconciliation, and stale-card behavior on a non-production incident.
- 03Confirm supported actions by lifecycle phase instead of assuming Slack and Teams parity.
DOCUMENTATIONSetup, authorization, limits, and troubleshooting.
Explore chatops documentationYour incidents should belong to you.
Run OpsKnight on infrastructure you control.
v2.0.0 · AGPL-3.0-only · Self-hosted · 28 inbound integrations