Opsgenie Integration

Integrate BlackTide with Opsgenie for automated incident creation, intelligent alert routing, and on-call management. Alternative to PagerDuty with similar features.

Prerequisites

• Opsgenie account (Free or paid plan)
• API integration access
• BlackTide account with alert configuration access

Step 1: Create Opsgenie Integration

1. Log in to Opsgenie
2. Go to Settings → Integrations
3. Click Add Integration
4. Search for API and select it
5. Name it "BlackTide Monitoring"
6. Configure integration settings:
   • Assigned Team: Select your on-call team
   • Responders: Choose who gets alerted
   • Priority: Default priority level
7. Click Save Integration
8. Copy the API Key

Step 2: Configure BlackTide Channel

1. Log in to BlackTide
2. Navigate to Alerts → Alert Channels
3. Click New Channel
4. Select Opsgenie
5. Fill in configuration:
   • Name: Production Incidents
   • API Key: Paste from Step 1
   • Region: US or EU
   • Priority: P1, P2, P3, P4, P5
   • Responders: team_xyz (optional)
6. Click Test Channel
7. Verify alert created in Opsgenie
8. Save the channel

Configuration Example

{
  "type": "opsgenie",
  "name": "Production On-Call",
  "apiKey": "YOUR_API_KEY",
  "region": "us",
  "priority": "P2",
  "responders": [
    {"type": "team", "id": "team_abc123"}
  ],
  "tags": ["blacktide", "production"],
  "autoClose": true
}

Step 3: Create Alert Rule

1. Go to Alerts → Alert Rules
2. Click New Rule
3. Configure:
   • Name: Critical API Failures
   • Monitors: Select production monitors
   • Conditions: 3 consecutive failures
   • Channels: Select Opsgenie channel
4. Save the rule

Features

Alert Creation

BlackTide automatically creates Opsgenie alerts when monitors fail:

Alert Message: [BlackTide] Production API Down

Description:
Monitor: Production API Health Check
Status: Down
Failures: 3 consecutive
Last Error: Connection timeout after 10s
Time: 2026-02-13 10:30 UTC

Priority: P2
Tags: blacktide, production, api

[View Monitor] [View Dashboard]

Auto-Close on Recovery

When monitors recover, Opsgenie alerts are automatically closed:

Alert Closed

Monitor: Production API Health Check
Status: Up (recovered)
Downtime: 8 minutes 42 seconds
Recovery Time: 2026-02-13 10:38:42 UTC

Note: Service recovered automatically

Priority Levels

Team Routing

Route different monitor types to different teams:

{
  "backend-api": {
    "responders": [{"type": "team", "name": "Backend Team"}],
    "priority": "P1"
  },
  "frontend": {
    "responders": [{"type": "team", "name": "Frontend Team"}],
    "priority": "P2"
  },
  "web3": {
    "responders": [{"type": "team", "name": "Web3 Team"}],
    "priority": "P1"
  }
}

Advanced Configuration

Custom Fields

{
  "details": {
    "monitor_id": "mon_abc123",
    "environment": "production",
    "region": "us-east-1",
    "runbook": "https://wiki.example.com/runbooks/api-down",
    "dashboard": "https://blacktide.xyz/monitors/mon_abc123"
  }
}

Alert Actions

Configure automatic actions in Opsgenie:

• Auto-acknowledge: After first responder views
• Escalate: To manager after 15 minutes
• Add note: Link to BlackTide dashboard
• Create incident: For P1 alerts

Best Practices

1. Use Priority Wisely

Reserve P1 for true emergencies:

• P1: Production outages only
• P2: Important but not urgent
• P3-P5: Informational alerts

2. Configure On-Call Schedules

Set up rotations in Opsgenie:

• Weekly rotations with backup
• Follow-the-sun coverage
• Holiday schedules
• Escalation policies

3. Test Integration Monthly

1. Send test alert from BlackTide
2. Verify it reaches Opsgenie
3. Acknowledge and close
4. Confirm auto-close works on recovery

4. Add Context to Alerts

Include actionable information:

• What failed: Service name
• Impact: Users affected
• Runbook: Link to troubleshooting steps
• Dashboard: Link to BlackTide monitor

Troubleshooting

Test Alert Not Creating Alert

Possible Causes:

• API key is incorrect or expired
• Wrong region selected (US vs EU)
• Team has insufficient permissions

Solution:

1. Verify API key in Opsgenie settings
2. Check region matches (US: api.opsgenie.com, EU: api.eu.opsgenie.com)
3. Ensure integration is enabled
4. Test API key manually:

   curl -X POST https://api.opsgenie.com/v2/alerts \
     -H 'Authorization: GenieKey YOUR_API_KEY' \
     -H 'Content-Type: application/json' \
     -d '{
       "message": "Test from BlackTide",
       "priority": "P3",
       "source": "BlackTide"
     }'

Alerts Not Auto-Closing

Solution:

• Ensure autoClose: true in channel config
• Verify notifyOnRecovery enabled in alert rule
• Check alert alias matches (used for deduplication)

Opsgenie vs PagerDuty

Next Steps

• PagerDuty Integration: Alternative incident management
• Slack Integration: Team notifications
• Alert Rules: Configure when to page
• Best Practices: Avoid alert fatigue