PagerDuty (Edge)

Configure PagerDuty as a Source in your Pipeline

Perform the following steps to configure your PagerDuty Source:

1. Click Pipelines in the Navigation Bar.

2. Click + Create Pipeline in the Pipelines List View.

3. On the Select Source Type page, select PagerDuty.

4. On the Select Destination Type page, select the type of Destination you want to use.

5. In the Configure Source screen, specify the following:

   

   • Source Name: A unique name for your Source, not exceeding 255 characters. For example, PagerDuty Source.

   • In the Connect to PagerDuty section, specify the following:

     • API Key: The API key that you obtained from PagerDuty.

6. Click Test & Continue to test the connection to your PagerDuty Source. Once the test is successful, you can proceed to set up your Destination.

---

Data Replication

Hevo replicates data for all the objects selected on the Configure Objects page during Pipeline creation. By default, all supported objects and their available fields are selected. However, you can modify this selection while creating or editing the Pipeline. To ingest a child object, you must also select its parent object. For example, to ingest the Incident Notes object, you must also select the Incidents object. The Data Model lists the child objects of each parent object.

Hevo replicates data in the following ways:

• Historical data: In the first run of the Pipeline, Hevo ingests the existing data of the selected objects. For the following objects, PagerDuty returns only recent data, so Hevo ingests the data of a limited period:

  Object	Period of Historical Data
  Analytics All Services Metrics	The last 364 days
  Audit Records	The last 30 days
  Oncalls	The last 89 days
  Paused Incident Report Alerts	The last 179 days

• Incremental data: In each subsequent run, as per the sync frequency:

  • For the Incidents object, Hevo ingests the incidents created since the last run. To capture the changes made to recent incidents, such as acknowledgements and resolutions, Hevo also re-ingests the incidents created in the last seven days.

  • For the Analytics Raw Incidents object, Hevo ingests the incidents updated since the last run and re-ingests the incidents updated in the last day.

  • For the Change Events, Log Entries, and Notifications objects, Hevo ingests the records created since the last run and re-ingests the records of the last day.

  • For the Analytics All Services Metrics object, Hevo ingests the daily metrics since the last run and re-ingests the metrics of the last ingested day.

  • For the Audit Records, Oncalls, and Paused Incident Report Alerts objects, Hevo ingests the records since the last run.

  • For all other objects, Hevo ingests the entire data of the object.

You can resync all the objects except the child objects. Resyncing a parent object also resyncs its child objects.

PagerDuty limits each API key to 960 REST API requests per minute. Requests that exceed this limit are rejected by PagerDuty with an error. Read Rate Limits — REST API.

Note: You can create a Pipeline with this Source only using the Merge load mode. The Append mode is not supported for this Source.

---

Schema and Primary Keys

Hevo uses the following schema to upload the records in the Destination. For a detailed view of the objects, fields, and relationships, click the ERD.

---

Data Model

The following is the list of tables (objects) that are created at the Destination when you run the Pipeline:

---