Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.warrn.io/llms.txt

Use this file to discover all available pages before exploring further.

Most integrations are configured at the team or org level. Add them at the service level when this service needs to behave differently from the rest of the team.

​
Alert sources

Each service can have one or more alert sources attached. Alerts created through these integrations are automatically associated with the service, which means they inherit the service’s owning team and on-call. See Integrations for the full catalog and setup details per source.

​
Chat and ticketing

Slack, Jira, and Confluence can be configured per service to override what the team or org has set. Common reasons to override:
  • This service alerts into a quieter or noisier Slack channel than the rest of the team.
  • Tasks created from this service’s incidents should land in a different Jira project.
  • Runbooks for this service live in a different Confluence space.
If you don’t set anything at the service level, it falls back to the team’s setting, then the org’s. When you add Confluence to a service (or team), there’s a toggle: “Use this space for AI runbook search.” With it on, Warrn searches that Confluence space at alert time alongside its native runbooks. Pages the AI judges relevant get copied into Warrn as native runbooks so they’re found instantly the next time. Pages that aren’t relevant stay where they are. This is the cleanest way to bring existing runbook knowledge from Confluence into Warrn without a manual migration.