OpsGenie, now part of Atlassian, is an alerting and incident management platform that natively integrates with Jira, Confluence, and other Atlassian tools. If your team already uses the Atlassian suite, OpsGenie is the natural choice for on-call management.
The MoniTao-OpsGenie integration automatically routes your alerts to OpsGenie, triggering configured escalation policies and optionally creating Jira tickets for tracking.
This integration is particularly powerful for teams wanting a continuous workflow from monitoring to resolution, with complete traceability in Jira and automatic documentation in Confluence.
What is OpsGenie?
OpsGenie offers a complete incident management suite:
- Intelligent alerting: Automatic enrichment, deduplication, and noise suppression. Similar alerts are grouped to reduce fatigue.
- On-call schedules: Flexible rotations, overrides, and vacation management. Calendar integration to visualize on-call.
- Jira integration: Automatic Jira ticket creation from alerts. Bidirectional status synchronization.
- Mobile application: Dedicated app to acknowledge, escalate, and manage incidents from phone. Works offline.
Integration Benefits
The MoniTao-OpsGenie integration brings:
- Atlassian ecosystem: If you use Jira and Confluence, OpsGenie integrates seamlessly. Incidents become tickets, post-mortems become Confluence pages.
- Automated actions: Configure actions to execute automatically on alert: restart service, scale infrastructure, create ticket.
- Alert policies: Filter and route alerts based on content. Staging alerts go to dev team, prod alerts to ops team.
- Heartbeat monitoring: OpsGenie can monitor that MoniTao is sending heartbeats, alerting if the monitoring tool itself goes down.
- Detailed reports: MTTA/MTTR metrics, load per team, on-call performance. Data for continuous improvement.
Integration Configuration
Connect MoniTao to OpsGenie in a few steps:
- Create an API integration: In OpsGenie > Settings > Integrations, create a new API type integration. Copy the API Key.
- Configure the team: Assign the integration to an OpsGenie team. Alerts will be routed according to that team's escalation policy.
- Add in MoniTao: In MoniTao > Alerts > Webhooks, add an OpsGenie destination and paste the API Key.
- Configure priorities: Map MoniTao alert levels to OpsGenie priorities (P1 to P5).
- Test: Send a test alert from MoniTao and verify it appears in OpsGenie with correct information.
Payload Format
MoniTao sends alerts in OpsGenie Alert API format:
{
"message": "[DOWN] example.com - HTTP 503",
"alias": "monitao-monitor-123-incident-456",
"priority": "P1",
"source": "MoniTao",
"tags": ["production", "website", "critical"],
"details": {
"monitor_name": "Production Website",
"url": "https://example.com",
"status_code": "503",
"response_time_ms": "12500",
"check_location": "Paris, France"
},
"entity": "example.com",
"actions": ["Restart", "Scale Up", "Check Logs"]
}
The alias serves as deduplication key. Tags allow filtering in OpsGenie. Actions appear as buttons in the mobile app.
Automatic Jira Integration
OpsGenie can automatically create Jira tickets:
- Creation on alert: Configure an action to create a Jira ticket when a P1 or P2 alert is triggered. The ticket contains all alert information.
- Bidirectional sync: Jira ticket status and OpsGenie alert stay synchronized. Close ticket = resolve alert.
- Enrichment: Add custom fields to ticket: business impact, affected components, associated runbook.
- Post-mortem: OpsGenie can create a Confluence page with the incident timeline to facilitate post-mortem.
Best Practices
Optimize your MoniTao-OpsGenie integration:
- Use tags: Tag your MoniTao monitors (production, staging, service-name). These tags are transmitted to OpsGenie for filtering.
- Configure Alert Policies: Use OpsGenie rules to route alerts by tag, source, or content to the right teams.
- Define actions: OpsGenie actions (restart, scale, check logs) accelerate resolution. Configure them by monitor type.
- Enable heartbeat: Configure MoniTao to send heartbeats to OpsGenie. You'll be alerted if MoniTao itself has a problem.
OpsGenie Integration Checklist
- API integration created in OpsGenie
- API Key configured in MoniTao
- Team and escalation policy assigned
- Priorities mapped (P1-P5)
- Test alert successful
- Jira integration configured (if applicable)
Frequently Asked Questions
What's the difference between OpsGenie and PagerDuty?
Functionally similar, OpsGenie stands out with its native integration to the Atlassian ecosystem (Jira, Confluence). PagerDuty has a larger integration ecosystem.
Do I need an Atlassian subscription for OpsGenie?
No, OpsGenie can be used standalone. But Jira integration requires a Jira Cloud or Data Center subscription.
Can alerts automatically create Jira tickets?
Yes, it's a native OpsGenie feature. Configure a "Create Jira Issue" action on high priority alerts.
How to manage multiple teams?
Create one integration per team in OpsGenie, with distinct API Keys. In MoniTao, assign each monitor to the right webhook destination.
Does OpsGenie support maintenance windows?
Yes, configure "Maintenance Windows" in OpsGenie. Alerts during these periods are suppressed or reduced in priority.
How to enrich alerts with more context?
MoniTao sends all monitor information in the "details" field. OpsGenie can display them and use them in Jira templates.
Conclusion
The MoniTao-OpsGenie integration is ideal for teams using the Atlassian ecosystem. From monitoring to resolution documented in Jira, the workflow is smooth and traceable.
Configure the integration now and benefit from professional incident management, perfectly integrated with your existing tools.
Ready to Sleep Soundly?
Start free, no credit card required.