PagerDuty Integration

Connect Pulsar to PagerDuty for on-call alerting and incident management.

Setup

Step 1: Create a PagerDuty Service

1. Log in to PagerDuty
2. Go to Services → Service Directory
3. Click New Service
4. Configure the service:
   • Name: "Pulsar Monitoring"
   • Integration: Select Events API v2
5. Copy the Integration Key

Step 2: Create the channel in Pulsar

1. Go to Settings → Notification Channels → Create Channel
2. Enter a Channel Name (for example "On-Call PagerDuty")
3. Set Channel Type to PagerDuty
4. Paste the key into Integration Key
5. Click Create

Step 3: Link the channel to your sites

A channel sends nothing until it is attached to a site. Open the site in Pulsar, click Link Channel in the Notification Channels card and pick the channel. Repeat for every site that should alert there. Use the Test action on the channel row in Settings to send a test message.

How It Works

Pulsar integrates with PagerDuty Events API v2:

Pulsar Event	PagerDuty Action
Site goes down	Creates incident (trigger)
Site recovers	Resolves incident

Incident Details

When Pulsar creates a PagerDuty incident, it includes:

• Summary - Site name and error type
• Severity - Based on alert type (critical for down, warning for degraded)
• Source - Pulsar monitoring
• Custom details - Response time, status code, error message

Escalation Policies

PagerDuty handles escalation based on your configured policies:

1. Initial notification to on-call responder
2. Escalation if not acknowledged
3. Additional escalations as configured

Best Practices

Service Configuration

1. Dedicated service - Create a separate service for Pulsar alerts
2. Appropriate urgency - Set urgency based on site criticality
3. Escalation policy - Configure escalation for unacknowledged alerts

Alert Routing

Consider creating multiple services for different severity levels:

Service	Alert Types
Pulsar Critical	Site down, checkout failures
Pulsar Warning	Degraded performance, JS errors

Troubleshooting

Incidents Not Creating

1. Verify the Integration Key is correct
2. Check PagerDuty service is active
3. Ensure the service isn't in maintenance mode
4. Send a Test from the channel row in Settings

Incidents Not Resolving

1. Check that the same Integration Key is used
2. Verify PagerDuty's Events API is receiving resolve events
3. Check for deduplication key mismatches

Rate Limits

PagerDuty has rate limits on the Events API:

• 120 events per minute per integration key
• Pulsar batches events to stay within limits