Opsgenie Integration
Create and auto-resolve Opsgenie alerts from TigerOps detections with full context attached. Team routing, priority mapping, and bidirectional sync — configured in minutes.
How It Works
Create an Opsgenie API Integration
In Opsgenie, create a new API integration and copy the API key. In TigerOps, add the Opsgenie integration under Settings > Alerting > Opsgenie and paste the key.
Configure Alert Routing Rules
Map TigerOps alert severity levels to Opsgenie priorities and teams. Critical alerts go to P1 with on-call escalation; warnings become P3 with business-hours routing.
Add Runbook Links and Context
TigerOps attaches the AI-generated incident summary, correlated metric charts, and runbook URL to every Opsgenie alert as details fields and a description.
Enable Auto-Resolution
When TigerOps detects that an alert condition has cleared, it automatically resolves the corresponding Opsgenie alert — eliminating manual close steps during an incident.
What You Get Out of the Box
Bidirectional Sync
TigerOps creates Opsgenie alerts on detection and resolves them on recovery. Alert acknowledgements in Opsgenie are synced back to TigerOps for audit trail completeness.
Team & Schedule Routing
Route alerts to specific Opsgenie teams, schedules, or escalation policies based on TigerOps alert tags — service name, environment, severity, and custom labels.
Rich Alert Context
Every Opsgenie alert includes the TigerOps AI summary, affected service, metric values at detection time, correlated events, and a direct deep link to the TigerOps incident page.
Priority Mapping
Configure TigerOps-to-Opsgenie priority mapping: Critical → P1, High → P2, Medium → P3, Low → P4. Custom mapping rules support per-team priority overrides.
Alert Deduplication
TigerOps uses Opsgenie's alias field for deduplication. Repeated detections for the same condition update the existing Opsgenie alert rather than creating duplicates.
Incident Timeline Export
TigerOps exports the full incident timeline — detection, acknowledgement, investigation steps, and resolution — to Opsgenie as a post-incident report.
Alert Policy YAML with Opsgenie Routing
Define alert routing rules that map TigerOps alerts to Opsgenie teams and priorities.
# tigerops-alert-policy.yaml — Opsgenie routing rules
integrations:
opsgenie:
- name: production-oncall
apiKey: "${OPSGENIE_API_KEY}"
region: us # or eu
defaultTeam: platform-oncall
routing_rules:
# Critical infrastructure alerts → P1, immediate escalation
- match:
severity: critical
labels:
env: production
opsgenie:
priority: P1
teams: [platform-oncall]
escalationPolicy: production-critical
message: "[CRITICAL] {{ .AlertName }} — {{ .Service }}"
runbookUrl: "https://wiki.example.com/runbooks/{{ .AlertName }}"
details:
affected_service: "{{ .Labels.service }}"
metric_value: "{{ .Value }}"
threshold: "{{ .Threshold }}"
# High severity application alerts → P2, app team
- match:
severity: high
labels:
category: application
opsgenie:
priority: P2
teams: [app-team]
message: "[HIGH] {{ .AlertName }}"
# Warning alerts → P4, no wake-up
- match:
severity: warning
opsgenie:
priority: P4
teams: [platform-oncall]
message: "[WARN] {{ .AlertName }}"
auto_resolve:
enabled: true
resolveMessage: "Auto-resolved by TigerOps — condition cleared"Common Questions
Which Opsgenie regions does TigerOps support?
TigerOps supports both Opsgenie US (api.opsgenie.com) and EU (api.eu.opsgenie.com) regions. Select your region when configuring the integration in TigerOps.
Can TigerOps route different alert types to different Opsgenie teams?
Yes. Create multiple TigerOps Opsgenie integration configurations, each pointing to a different Opsgenie API key. Then use TigerOps alert routing rules to send infrastructure alerts to the infra team and application alerts to the app team.
How does TigerOps handle Opsgenie maintenance windows?
TigerOps respects Opsgenie's maintenance window schedule by polling the Opsgenie API. During an active maintenance window for a team, TigerOps suppresses alert creation for alerts routed to that team.
Can I add custom details fields to Opsgenie alerts from TigerOps?
Yes. In the TigerOps Opsgenie integration settings, configure a details mapping that extracts fields from the TigerOps alert payload — such as deployment version, affected endpoint, or SLO budget remaining — and adds them as Opsgenie details.
Does TigerOps support Opsgenie actions (custom actions on alerts)?
Yes. Configure Opsgenie actions in the integration settings. Actions like "Silence for 1 hour" or "Trigger remediation runbook" can be added as Opsgenie alert actions and triggered from the Opsgenie mobile app or web UI.
AI-Powered Detections. Opsgenie On-Call. Zero Manual Steps.
Automatic alert creation, rich context, and auto-resolution for Opsgenie. Configure in 5 minutes.