Skip to content

How to Fix PagerDuty Service Integration

DodaTech Updated 2026-06-26 3 min read

In this tutorial, you'll learn about How to Fix PagerDuty Service Integration. We cover key concepts, practical examples, and best practices.

The Problem

Your PagerDuty service integration configuration is not working. Notifications do not fire, incidents are not created, or the feature behaves incorrectly.

PagerDuty is critical for incident response, but service integration misconfiguration leads to missed alerts and delayed responses. At DodaTech, we use PagerDuty for on-call management across all production services. Here is how we fix service integration issues.

Error Symptoms

You see in the PagerDuty console:

Integration test failed
0aab61fa35db service-integration configuration error
No incidents created

Wrong Configuration

This is the problematic service integration setup:

{
  "service": {
    "name": "My Service",
    "description": "Production service"
  }
  // Missing: service integration configuration
}

Without proper service integration fields, PagerDuty creates the service but does not apply the required routing, escalation, or notification rules.

API response:

HTTP 201 Created
  Warning: service-integration not configured - using defaults
  Service created without service-integration rules

Right Configuration

Here is the correct service integration setup:

{
  "service": {
    "name": "My Service - pagerduty-servic",
    "description": "Production service managed by DodaTech SRE team",
    "escalation_policy": {
      "id": "ES12345"
    },
    "incident_urgency_rule": {
      "type": "use_support_hours",
      "during_support_hours": {
        "type": "constant",
        "urgency": "high"
      },
      "outside_support_hours": {
        "type": "constant",
        "urgency": "low"
      }
    },
    "alert_creation": "create_alerts_and_incidents"
  }
}

Expected output:

HTTP 201 Created
Service created successfully
Integration key: PD-0aab61fa35db

Prevention

  • Test service integrations with the PagerDuty API sandbox environment before production
  • Configure escalation policies with proper timeout values and multiple notification levels
  • Schedule maintenance windows for planned changes to prevent false alerts
  • Use event orchestration for complex alert routing, deduplication, and suppression
  • Set up runbook actions for automated incident response and resolution
  • Review SLO targets to align alert severity with business impact
  • Regularly audit on-call schedules for coverage gaps, especially during holidays

Common Mistakes with service integration

  1. Mixing let bindings with <- bindings in do notation, producing type errors
  2. Overlapping type class instances that cause GHC to reject the program with ambiguous dispatch errors
  3. Non-exhaustive pattern matches that compile with warnings then crash at runtime

These mistakes appear frequently in real-world PAGERDUTY code. DodaTech's contributors have identified these patterns through analysis of open-source projects and production systems.

Practice Exercise

Write a pure function that safely divides two integers using Maybe, then test it with edge cases like division by zero and negative numbers.

This exercise reinforces the concepts covered in this guide. Try implementing it before checking online solutions.

FAQ

Why is my PagerDuty service-integration not sending alerts?

Check the integration key in your monitoring tool configuration. Verify that the escalation policy has at least one on-call user assigned and is not in a maintenance window.

How do I test PagerDuty integrations before going live?

Use the PagerDuty API's test endpoint (POST /test) or send a test alert from your monitoring tool (Datadog, Prometheus, Grafana) to validate the integration key and routing.

How does DodaTech use PagerDuty for incident management?

DodaTech routes all production alerts through PagerDuty with automated runbook actions for common incidents. We use event orchestration to deduplicate alerts and reduce noise by 60%.

What is the difference between PagerDuty services and escalation policies?

A service represents a component or application, while an escalation policy defines who gets notified and when. Multiple services can share one escalation policy.

Built by the developers of DodaTech

Doda Browser, DodaZIP & Durga Antivirus Pro