How investigations use this
Connected documentation is synced and indexed for both keyword and semantic search. From there it’s available in two places:- In investigations — relevant runbooks and reference docs surface as evidence, helping ground a finding in how your systems are actually meant to work and what to do about a known failure.
- In the chatbot — ask a question in an incident channel and the answer can cite the specific docs it drew on, with links back to the source.
Documentation is most valuable when it captures operational knowledge — runbooks, architecture overviews, and
references. The more your docs describe how to operate and debug your systems, the more investigations can lean on
them.
Providers you can connect
| Provider | What gets synced |
|---|---|
| Confluence | Pages from the spaces you choose |
| Notion | Pages and databases you choose |
| GitHub | Markdown and docs in repositories, by file path |
| GitLab | Markdown and docs in repositories, by file path |
Setup
Configure document sources from the Investigations settings in your dashboard.Connect the provider
Connect the relevant integration (Confluence, Notion, GitHub, or GitLab) if you haven’t already.
Choose what to sync
Scope each source to the docs that matter:
- Confluence — select the spaces to sync.
- Notion — select the pages or databases to sync.
- GitHub and GitLab — choose repositories and the file paths to include (for example
docs/**or*.md).
When a document is removed at the source, it’s dropped from search on the next sync. Only the documents you scope are
synced — investigations never read beyond the spaces, pages, or paths you choose.
Related
How investigations work
How a runbook becomes evidence in a finding.
Chatbot
Ask questions in the incident channel and get cited answers.