The Investigator in Discord

The Investigator works in your Discord much like it does in Slack — a slash command instead of a mention, the same case at the other end. Run /investigate with a question, and it opens a thread, digs through the connected accounts, and reports back in that thread with what it found. Every case it opens also lives in the console, one click away.

Start an investigation

Run /investigate with your question:

/investigate why is checkout latency up since this morning?

The Investigator acknowledges right away and opens a thread on that message — this investigation’s own scope, separate from anything else running in the channel. When it finishes, the result posts into the thread: a headline, the evidence, and a plain-language confidence phrase, the same shape it uses in Slack.

Continue the conversation

Run /continue with your follow-up. Run it inside an investigation’s thread to continue that one unambiguously:

/continue what changed in the last deploy?

Run it at the channel level, outside any thread, and it follows up on whichever investigation was started most recently in that channel.

Alerts and watches

Once a default channel is set in Discord settings, an alert- or watch-triggered case posts there too — the Investigator opens its own thread on that post, so following up in it works exactly like following up on a case you started yourself with /investigate. Critical, warning, and info severities can each route to a different channel; anything without an override falls back to the default. If quiet hours are on, a non-critical post waits until the window ends — critical posts always go through right away.

If your project has several AWS or Kubernetes connections and the channel isn’t bound to one, the Investigator declines and asks you to bind the channel in Discord settings first — it never guesses which account you mean.

If Slack is also connected

Channel routing works independently on each provider — an alert- or watch-triggered case can post to both Slack and Discord if both have a channel configured, since neither is “the” surface for an unattended firing. A case you start yourself always stays where you started it, though: running /investigate here never also posts the result to Slack, and a case you summon in Slack never spills into Discord.

Answer a question

When the Investigator needs a decision partway through, it posts the question in the thread under Needs your input. If the question comes down to a single set of options, a dropdown is attached to the message — pick one and the investigation resumes immediately. Anything else — free text, or a question with more than one part — needs a /continue with your answer.

Next: The inbox