Skip to main content
Investigations get better the more context they can draw on. Connecting your sources takes a few minutes each, and you can start with whichever you have to hand — every source you add makes investigations more grounded. Everything below is configured from the Investigations settings in your dashboard.

​
1. Connect your sources

1

Past incidents

Let investigations find similar incidents from your history and the fixes that worked before. See Past incidents.
2

Slack channels

Add the channels where your team shares deploys, config changes, and incident context. See Slack channels.
3

Documentation

Sync your runbooks and reference docs from Confluence, Notion, GitHub, or GitLab. See Documentation.
4

Code repositories

Connect GitHub or GitLab so investigations can link relevant pull requests and read your code. See Code repositories.
5

Telemetry

Connect the observability tools your team uses during incidents. See Telemetry.
Connect the dashboards and data sources your team actually reaches for during an incident. The closer they reflect your real workflow, the more useful investigations will be.

​
2. Choose when investigations run

Decide whether investigations run for every incident, only when conditions are met, when a workflow triggers them, or only on demand. See Triggering investigations for the options.

​
3. Run your first investigation

Create a test incident and trigger an investigation to see it in action. You can start one manually from the incident, or by using /inc investigate in Slack.

​
What’s next

  • Try the chatbot — tag @incident in an incident channel to ask about logs, code changes, past incidents, or recent deploys. See the chatbot docs.
  • Share feedback — use the thumbs up/down buttons on investigation messages, and tell us what’s working and what isn’t.