Context

Context gives triage something from your own stack to stand on. It does not create Pulses.

When a repository, runbook, observability tool, open issue, or status-page incident is connected, triage can cite it instead of guessing. You see that citation under What informed this on the Pulse. See How triage helps.

Configure connectors in the app under Connections → Context. At triage time, verified connectors run in parallel under a shared time budget. Excerpts are scrubbed with your workspace rules, stored on the Pulse, and sent to the model unless you opt that connector out. A connector that fails is skipped; triage still completes. Send-test-alert Pulses skip live collectors.

Jira and Linear still support postmortem follow-ups. They also contribute up to three open issues that match the service or title. Statuspage is coming soon and is not offered to connect.

If you want a vendor’s alerts to become Pulses, connect that vendor under Sources instead.

See Prompt → Context use for prompt size and per-connector opt-out.

---

Repositories

Recent commits and a short deploy-correlation window from connected repos.

• GitHub
• GitLab
• Bitbucket
• Azure DevOps

Observability context

API credentials Exhale uses at triage time — distinct from Sources webhooks.

• Datadog
• New Relic
• Splunk
• Dynatrace
• Grafana
• Elastic
• Honeycomb
• Sentry
• AWS CloudWatch

Runbooks & docs

Playbooks matched to the Pulse service name or alert key.

• Confluence
• Notion (coming soon)
• Markdown upload
• SharePoint / OneDrive
• Guru
• GitBook
• Docs URL

Ticketing

Jira and Linear contribute up to three matching open issues at triage, and they support postmortem follow-through.

• Jira
• Linear
• Statuspage (coming soon)

---

Caps

Connector slots are shared across Context categories. Markdown uploads use a separate document cap.

Plan	Context connectors	Runbook documents
Trial	3	5
Starter	3	10
Growth	10	25
Business	20	75
Enterprise	30	100