PagerDuty Integration

Send AlertifyPro alerts to PagerDuty to take advantage of PagerDuty's advanced on-call management, mobile notifications, and escalation policies.

Prerequisites

• A PagerDuty account (sign up)
• PagerDuty service with Events API v2 integration

---

Setup

Step 1: Create a PagerDuty service

1. In PagerDuty, go to Services → Service Directory → New Service
2. Name it (e.g. AlertifyPro Alerts)
3. Choose an Escalation Policy
4. Under Integrations, select Events API v2
5. Copy the Integration Key (also called Routing Key)

Step 2: Add the integration in AlertifyPro

1. Go to Settings → Integrations → PagerDuty
2. Paste the Integration Key
3. Click "Test connection" — you should see a test incident in PagerDuty
4. Click Save

---

Configuration

integrations:
  pagerduty:
    integration_key: "your-pagerduty-integration-key"
    
    # Map AlertifyPro severity to PagerDuty severity
    severity_map:
      critical: critical
      warning: warning
      info: info
    
    # Auto-resolve PagerDuty incident when monitor recovers
    auto_resolve: true
    
    # Include monitor details in PagerDuty incident body
    include_details: true

---

Alert payload

AlertifyPro sends PagerDuty Events API v2 payloads:

{
  "routing_key": "your-integration-key",
  "event_action": "trigger",
  "dedup_key": "mon_abc123",
  "payload": {
    "summary": "Production API is DOWN — HTTP 503 from us-east-1, eu-west-1",
    "source": "alertifypro",
    "severity": "critical",
    "timestamp": "2026-03-02T14:23:00Z",
    "component": "Production API",
    "group": "infrastructure",
    "custom_details": {
      "monitor_id": "mon_abc123",
      "url": "https://api.yourapp.com/health",
      "failing_regions": ["us-east-1", "eu-west-1"],
      "response_code": 503,
      "duration": "3m 24s"
    }
  }
}

When the monitor recovers, AlertifyPro automatically sends a resolve action to close the PagerDuty incident.

---

Per-monitor routing

Route different monitors to different PagerDuty services:

monitors:
  - name: Production Database
    alerts:
      pagerduty:
        integration_key: "prod-db-pagerduty-key"  # High-priority service

  - name: Staging API
    alerts:
      pagerduty:
        integration_key: "staging-pagerduty-key"  # Lower-priority service

---

Troubleshooting

Issue	Solution
No incidents appearing in PagerDuty	Verify the Integration Key is correct
Incidents not auto-resolving	Check auto_resolve: true is set
Wrong severity levels	Update severity_map to match your PagerDuty setup
Duplicate incidents	AlertifyPro uses dedup_key — ensure only one integration key per service