PagerDuty Integration

Send monitor alerts to PagerDuty using Events API v2. Automatically create and resolve incidents in your PagerDuty service.

How It Works

Uptime Monitor integrates with PagerDuty through the Events API v2 to create incidents when monitors go down:

  • •Creates incidents when monitors go down
  • •Automatically resolves incidents when monitors recover (configurable)
  • •Includes monitor details and error information
  • •Deduplicates alerts to prevent duplicate incidents
  • •Links directly to monitor dashboard

Prerequisites

PagerDuty Requirements

  • •Active PagerDuty account (any plan)
  • •Admin or Manager role for creating integrations
  • •At least one PagerDuty service configured

Uptime Monitor Requirements

  • •Active Uptime Monitor account
  • •At least one monitor configured
  • •Admin access to manage integrations

Step-by-Step Setup

Step 1: Create PagerDuty Integration

  1. 1

    Log in to your PagerDuty account and navigate to Services → Service Directory

  2. 2

    Select an existing service or click + New Service to create one

  3. 3

    In the service, go to the Integrations tab

  4. 4

    Click + Add Integration

  5. 5

    Search for and select Events API v2

  6. 6

    Name it "Uptime Monitor" and click Add

  7. 7

    Copy the Integration Key (32-character string)

Important: Keep this integration key secure. It allows sending incidents to your PagerDuty service.

Step 2: Configure in Uptime Monitor

  1. 1

    In Uptime Monitor, go to Settings → Contacts

  2. 2

    Click Add Contact and select PagerDuty

  3. 3

    Enter a name (e.g., "Production Alerts") and paste your Integration Key

  4. 4

    Configure auto-resolve setting (enable to automatically resolve incidents when monitors recover)

  5. 5

    Save the contact

Step 3: Assign to Monitors

Now assign the PagerDuty integration to your monitors:

  1. 1

    Navigate to a monitor you want to alert through PagerDuty

  2. 2

    Edit the monitor and find the Contacts section

  3. 3

    Add your PagerDuty contact to the monitor

  4. 4

    Save the monitor configuration

Success! Your monitor will now create PagerDuty incidents when issues are detected.

Incident Information

Each PagerDuty incident includes comprehensive details:

{
  "summary": "Production API is DOWN",
  "source": "uptime-monitor.io",
  "severity": "error",
  "component": "Production API",
  "group": "monitors",
  "class": "HEAD https://api.example.com/",
  "custom_details": {
    "monitor_id": "507f1f77bcf86cd799439011",
    "monitor_name": "Production API",
    "monitor_url": "HEAD https://api.example.com/",
    "monitor_type": "HTTPS",
    "incident_id": "507f1f77bcf86cd799439012",
    "reason": "Connection timeout after 30000ms",
    "check_interval": 60,
    "timeout": 30
  },
  "links": [{
    "href": "https://uptime-monitor.io/monitors/507f1f77bcf86cd799439011",
    "text": "View Monitor Dashboard"
  }]
}

Best Practices

  • ✓
    Create separate PagerDuty contacts for different services

    Use different integration keys for production vs staging environments

  • ✓
    Enable auto-resolve for cleaner incident tracking

    Automatically resolve PagerDuty incidents when monitors recover

  • ✓
    Use meaningful monitor names

    Monitor names appear in PagerDuty incidents - make them descriptive

  • ✓
    Test integration before production use

    Use the Test button in contact settings to verify incidents are created correctly in PagerDuty

Troubleshooting

Common Issues

Incidents not appearing

  • • Verify the integration key is correct (32-character string)
  • • Ensure monitor has PagerDuty contact assigned
  • • Check monitor is not paused

Integration errors

  • • Verify you're using Events API v2 integration
  • • Check integration key hasn't been regenerated in PagerDuty
  • • Test with a different monitor to isolate issues
← Discordincident.io →