The Edwin AI PagerDuty integration is an outbound integration. This means Edwin AI initiates communication by sending incidents to PagerDuty. This integration enables automated incident creation in PagerDuty based on alerting conditions defined in Edwin AI. It supports server-to-server communication and leverages OAuth 2.0 for secure authorization.

You can use the Edwin AI PagerDuty Integration to do the following:

  • Automatically create PagerDuty incidents from Edwin AI alerts
  • Route different incident types to specific on-call teams usingPagerDuty service IDs
  • Configure outbound-only authentication with OAuth 2.0 credentials (client ID and secret)

Configuring the Edwin AI PagerDuty Integration involves the following:

  1. Registering a PagerDuty application
  2. Adding a PagerDuty action to an action group and configuring mapped fields

This process supports centralized alert handling and ensures LogicMonitor and PagerDuty remain synchronized in real time.

Requirements for Configuring the Edwin AI PagerDuty Integration

To configure the Edwin AI integration with PagerDuty, ensure you have the following within PagerDuty:

  • A PagerDuty user with “Advanced” permissions set
  • Your PagerDuty subdomain (for example, company.pagerduty.com)
  • Your PagerDuty region (US or EU)

In addition, in Edwin you need an Edwin AI user with “Manage” permissions set. 

Note: The integration supports outbound communication only and does not support webhook-based or inbound workflows.

Registering a PagerDuty Application for Edwin AI

  1. In PagerDuty, navigate to the App Registration page.

    Note: If you have a developer account with PagerDuty, you are automatically taken to the App Registration page when you log in. If you have a customer account with PagerDuty, and need more information on how to access App Registration in PagerDuty, see Accessing App Registration Page from PagerDuty.

  2. Select My Apps page > select New App > then complete the App Information form and ensure the following:
    • Enter in all required fields
    • In the Functionality section, select OAuth 2.0.
  3. To configure the OAuth 2.0 authentication, select Next, then do the following:
    1. In the Authorization section, select “Scoped OAuth.”
    2. In the Permissions Scope section, select the following permissions:
      • Incidents.read
      • Incidents.write
        For more information, see Scoped OAuth from PagerDuty. 
  4. To generate your PagerDuty Client ID and Client Secret, select Register App.
    Save your Client ID and Client Secret in a secure location for later use. 

After you register your PagerDuty application, send the following information to your Edwin AI administrator:

  • Client ID and Client Secret
  • PagerDuty Subdomain and Region

The Edwin team stores these credentials in the secure backend configuration for your organization.

Adding a PagerDuty Action to an Action Group

  1. In LogicMonitor, navigate to Edwin AI > the Actions page.
  2. Select Edit on either your Alert Correlation action group or Create Incident (Insight) action group.
  3. To configure your action, select “Create PagerDuty Incident” from the Add Action dropdown menu, and do the following:
    Add Action dropdown menu
    1. Enter in the general information. For more information on each field, see Creating and Editing an Action in Edwin AI. 
    2. Enter the following values for the mapped fields:
      • Service ID—Identifies the PagerDuty service that receives the incident.
      • Title—The subject line for the incident. 
      • (OptionalBody details, URL, Incident key fields—Use these fields to enrich the incident with additional context.
        For more information, see Configuration Parameters for Actions – Mapping Fields

        Important: Both Service ID and Title must contain values. If either field is missing, the incident cannot be created in PagerDuty.

  4. Select Submit.

Your PagerDuty action is added to your action group. 

For more information on how to assign actions to rules, see Edwin AI Rules