xMatters Integration
Route TigerOps alerts through xMatters with AI-enriched notifications, escalation chain metrics, and full on-call response tracking. Deliver context-rich pages that reduce investigation time.
How It Works
Create an xMatters Inbound Integration
In xMatters, navigate to your target workflow and add a new HTTP trigger integration. Copy the trigger URL and authentication token for use in TigerOps.
Configure xMatters in TigerOps
Paste the xMatters trigger URL and authentication credentials into the TigerOps xMatters integration panel. Send a test alert to verify the end-to-end connection.
Map Groups and Escalation Policies
Map TigerOps service tags and severity levels to xMatters groups and escalation policies. Critical alerts page the primary group; warnings notify the secondary group by email.
Notifications Deliver with Full Context
On-call engineers receive AI-enriched xMatters notifications with incident summary, metric data, and a deep link. Responses sync back to TigerOps automatically.
What You Get Out of the Box
AI-Enriched xMatters Notifications
Every xMatters notification triggered by TigerOps carries an AI-generated incident summary, affected service details, and a direct link to the TigerOps investigation.
Escalation Chain Metrics
TigerOps tracks the full escalation chain for every xMatters alert — who was paged, when, who acknowledged, and how many escalations occurred before resolution.
Group and Device Targeting
Route TigerOps alerts to specific xMatters groups, devices (SMS, voice, push), and notification priority levels based on incident severity and service ownership.
Acknowledgment Sync
When an on-call engineer acknowledges or resolves a notification in xMatters, TigerOps receives the event via xMatters outbound webhook and updates the incident state.
Noise Reduction via Deduplication
TigerOps groups related alerts into a single incident before triggering xMatters. One xMatters notification per incident prevents notification storms during correlated outages.
On-Call Health Reporting
TigerOps aggregates xMatters response data to generate on-call health reports: pages per rotation, MTTA per group, missed pages, and escalation frequency trends.
xMatters Trigger Config
Configure xMatters trigger URL, payload mapping, and group routing rules.
# TigerOps — xMatters Integration Config
integrations:
xmatters:
trigger_url: "${XMATTERS_TRIGGER_URL}"
auth:
type: basic
username: "${XMATTERS_USER}"
password: "${XMATTERS_PASSWORD}"
min_severity: warning
auto_resolve: true
group_mappings:
- severity: critical
tags:
team: platform
xmatters_group: "Platform On-Call"
priority: HIGH
- severity: warning
xmatters_group: "Engineering Alerts"
priority: MEDIUM
payload_template:
properties:
summary: "{{ai_summary}}"
service: "{{service_name}}"
severity: "{{severity}}"
metric: "{{metric_name}}"
value: "{{metric_value}}"
trace_url: "{{trace_url}}"
dashboard_url: "{{tigerops_url}}"
slo_burn_rate: "{{slo_burn_rate}}"
inbound_webhook:
url: "https://ingest.tigerops.io/webhooks/xmatters"
events: [acknowledge, resolve, escalate]Common Questions
Does TigerOps integrate with xMatters workflows or just inbound triggers?
TigerOps integrates with xMatters via inbound HTTP triggers, which can invoke any xMatters workflow or flow designer automation. This means TigerOps can trigger complex multi-step xMatters workflows — not just simple notifications.
Can I customize the xMatters notification payload from TigerOps?
Yes. TigerOps supports a configurable JSON payload template for the xMatters trigger. You can map any TigerOps incident field — severity, service name, AI summary, trace URL, metric value — to the properties expected by your xMatters workflow.
How does TigerOps receive response events back from xMatters?
Configure an xMatters outbound integration (webhook) to POST response events (acknowledged, resolved, escalated) to the TigerOps inbound webhook URL. TigerOps processes these events and updates the corresponding incident state.
Can TigerOps target specific xMatters devices (SMS vs. push vs. voice)?
Device targeting in xMatters is controlled by xMatters notification policies and group device preferences. TigerOps can pass a notification priority level in the trigger payload, which xMatters maps to device delivery order according to the recipient's configured preference.
Does TigerOps support xMatters on-call schedule display?
TigerOps can query the xMatters on-call API to display who is currently on-call for a given group directly in the TigerOps incident panel. Schedule data is cached and refreshed every few minutes.
Deliver Smarter Alerts Through xMatters
No credit card required. Connect xMatters in minutes. AI-enriched notifications immediately.