Escalation context
Capture severity, title, resource, URL, body, tags, source id, and affected service clues.
Incident management integrations help alerts and escalations enter OpsRabbit with enough source context to start triage immediately. The goal is to enrich the incident path, not replace your escalation system.

What this page covers
Use PagerDuty, Opsgenie, xMatters, alert webhooks, email, or chat channels to start or update investigation threads.
Verify signatures or tokens where providers support them, and preserve source-event history for audit.
Use alert noise reduction so repeated incident events do not create repeated RCA turns.
Operational detail
Incident management integrations help alerts and escalations enter OpsRabbit with enough source context to start triage immediately. The goal is to enrich the incident path, not replace your escalation system.
Capture severity, title, resource, URL, body, tags, source id, and affected service clues.
Summaries should include impact, likely owner, next checks, customer-language drafts, and evidence links.
Where configured, OpsRabbit can post RCA notes or outbound summaries back to the incident source.
Related pages