This article provides instructions for configuring and using the Glean PagerDuty connector. This integration allows Glean to ingest and index PagerDuty data, helping users search for and reference on-call information and escalation paths directly from Glean’s enterprise search.

​
Supported Features and Limitations

The PagerDuty connector is designed to bring core on-call and escalation workflow data into Glean, focusing on supported use cases and documenting its current boundaries.

​
Supported Objects/Entities

  • Escalation Policies
  • Schedules

​
Key Features

  • On-Call Data Indexing: Indexes key PagerDuty objects, including escalation policies and schedules.
  • Access Management: Uses PagerDuty’s API to fetch user and team data for access management, ensuring search results respect PagerDuty’s access models.
  • Read-Only Access: Operates with a Read Only API Access Key, adhering to the principle of least privilege.

​
Supported API Endpoints/Features

  • /escalation_policies: Crawls escalation policy definitions if enabled in the configuration
  • /schedules: Crawls schedule configurations if enabled in the configuration
  • /users: Fetches user information for access management
  • /teams: Retrieves team information for access management
  • /audit/records: Obtains audit logs detailing user interactions with PagerDuty entities

​
Limitations

  • Deployment: This connector is limited to PagerDuty cloud accounts via API access and does not support on-premise or self-hosted deployments.
  • Scope: The connector’s indexing is limited to escalation policies and schedules only. Other objects, such as incidents and alerts, are not crawled at this time.
  • Data Access: The connector does not support write or administrative actions.

​
Requirements

To set up the PagerDuty connector, you must have the following:
  • PagerDuty Access: An active PagerDuty subscription with an account owner or administrator role.
  • Glean Access: Administrative permissions within the Glean Admin Console.
  • API Access Key: A PagerDuty Read Only API Access Key generated from the PagerDuty web interface.

​
How to Set Up the Connector

Follow these steps to configure the PagerDuty connector within the Glean Admin Console.

​
Step 1: Obtain the API Key

  1. Log in to your PagerDuty account as an administrator.
  2. Generate a Read Only API Access Key as described in the official PagerDuty documentation. For more information, see Generate a General Access REST API Key.

​
Step 2: Configure in Glean

  1. In the Glean Admin Console, navigate to Data Sources and select Add Data Source, and select PagerDuty.
  2. Provide a Name for the data source.
  3. Enter the API Access Key you just obtained from PagerDuty into the designated field.
  4. Click Save.
The connector will automatically test the connectivity and begin the initial crawl.

​
Permissions & Security

  • Permission Propagation: The connector uses PagerDuty’s API to enforce access controls. This ensures that Glean search results are limited to only those objects users have permission to view in PagerDuty.
  • Least Privilege: The connector uses a Read Only API Access Key, ensuring it can only ingest data and cannot perform any administrative or write actions.
  • Data Ingestion: Only escalation policies, schedules, and associated user, team, and audit metadata are ingested, minimizing exposure of sensitive details.