Turn it on
On the Triage page, open Slack settings and turn on Auto-join incident channels. Add one name pattern per line, using* as a wildcard. The default is inc-*. Add others such as sev* if your tool names channels differently.
Ordyn joins any new public channel whose name matches, and any channel that is renamed to a matching name. Shared channels from other workspaces are skipped.
What Ordyn does in the channel
- Reads what is already there. Ordyn catches up on the messages posted so far and opens any links to alerts, dashboards, logs, or traces.
- States the problem. Once it can say in one sentence what is broken, it posts a short summary so your team can correct it early if it misread.
- Investigates in a thread. Under that post, Ordyn works to measure the impact, find a way to mitigate, such as rolling back a deploy or turning off a feature flag, and find the root cause.
After it starts
Ordyn stays quiet unless someone mentions it. Mention Ordyn in the investigation thread to follow up, or anywhere in the channel to ask a new question or start another investigation. Messages from your incident tool’s own bot are read as context. They do not stop Ordyn from starting its own investigation. If the incident turns out not to be real, say so in the channel and Ordyn stands down.Private investigations
Some incidents, such as security issues, need to stay out of shared tools. Turn on Private investigations in the same settings and add name patterns, such assec-*. When you invite Ordyn to a matching private channel, it investigates the same way, but the investigation and any issues it opens stay in Slack and never appear in the web app.
Private investigations match nothing until you add a pattern. Use different patterns than auto-join.