How to Integrate Pingzo Alerts with PagerDuty Incident Management

PagerDuty is the industry standard platform for real-time incident response, on-call scheduling, and automated escalation. By routing your application alerts to PagerDuty, you ensure that critical infrastructure failures are instantly escalated to the correct engineers, minimizing your Mean Time to Resolution (MTTR).

Because Pingzo is built to deliver clean, actionable incident alerts, you can integrate it directly with PagerDuty using two natively supported approaches: Email-based incident routing (simple and robust) or custom webhook translation (advanced and structured). This guide explains how to configure both methods.

📬 Method 1: Route Alerts via PagerDuty Email Integrations (Recommended)

The simplest and most reliable way to connect Pingzo to PagerDuty is by configuring an email integration. In this model, PagerDuty generates a dedicated email inbox for your service. When Pingzo detects a downtime event, it emails that inbox, which automatically triggers a PagerDuty incident. When the service recovers, Pingzo sends a recovery email that resolves the incident.

1. Create a Service in PagerDuty

1. Log into your PagerDuty Dashboard and navigate to Services -> Service Directory.
2. Click New Service.
3. Name your service (e.g. Pingzo Uptime Monitor) and click Next.
4. Select your preferred escalation policy and click Next.
5. Under Integrations, search for and select Email (or Integrate via Email).
6. Click Create Service.

2. Copy the Integration Email Address

Once created, PagerDuty will display your service settings. Look for the integration section and copy the generated email address: alerts@your-account-subdomain.pagerduty.com

3. Add the Email Alert Channel in Pingzo

1. Navigate to your Pingzo Dashboard and click on Alert Channels.
2. Click Add Channel.
3. Select Email as the channel type.
4. In the Destination Email field, paste the PagerDuty integration email address.
5. Save the channel.

4. Link the Channel to Your Monitors

Ensure the new alert channel is linked to your active monitors. The next time a check fails, Pingzo will email PagerDuty, triggering your on-call phone alerts immediately.

⚡ Method 2: Route Alerts via PagerDuty Webhook Transformers

If you want to parse metadata programmatically (like mapping custom server latency values or monitor IDs directly into PagerDuty incident fields), you can configure a custom webhook integration.

Because PagerDuty's Events API V2 expects a specific JSON schema, you must use PagerDuty's Custom Event Transformer (CET) to translate Pingzo's payload format.

1. Add a Custom Event Transformer in PagerDuty

1. Go to your PagerDuty Service settings.
2. Under the Integrations tab, click Add an Integration.
3. Select Custom Event Transformer from the integration type catalog.
4. Give it a name (e.g. Pingzo Webhook Parser) and click Add.

2. Configure the Transformer Script

Click Edit on your new integration to open the JavaScript editor. Paste the following translation script to map Pingzo's payload to PagerDuty:

// Map Pingzo's incoming webhook payload to PagerDuty Events API V2 format
var input = PD.inputRequest.body;
var eventType = input.status === 'down' ? PD.Trigger : PD.Resolve;

var event = {
  event_action: eventType,
  dedup_key: input.monitor_id,
  payload: {
    summary: input.text || "Pingzo Uptime Incident",
    source: input.monitor_name || "Pingzo Monitor",
    severity: PD.Critical,
    custom_details: {
      url: input.url,
      check_time: input.time,
      incident_id: input.incident_id
    }
  }
};

PD.emitGenericEvents([event]);

Save the integration and copy the unique webhook endpoint URL generated by PagerDuty.

3. Add the Webhook Channel in Pingzo

1. In your Pingzo Dashboard, go to Alert Channels.
2. Click Add Channel and select Webhook.
3. Paste the PagerDuty Custom Event Transformer URL into the Webhook URL destination field.
4. Save the channel.

🔒 Step 3: Test Your Integration Flow

To ensure alerts propagate correctly, we recommend manually verifying the integration:

1. Find a test monitor (or configure a temporary check targeting a localhost dummy path that you know will return a 404).
2. Save the monitor and force the check to execute.
3. Verify that your PagerDuty service creates a new incident.
4. Once verified, point the monitor back to its healthy target and confirm that PagerDuty automatically resolves the incident.