On This Page
PagerDuty is a SaaS-based platform that gives business leaders, DevOps, developers, and IT operations the tools they need to avoid and handle business-impacting crises and provide excellent customer service. PagerDuty puts the appropriate information in the hands of the right people in real-time, every time, because of native integrations, on-call scheduling and escalations, machine learning, business-wide response orchestration, analytics, and more.
PagerDuty authenticates API requests from Hevo to access your account data with HTTP Basic authentication.
An active PagerDuty account from which data is to be ingested.
The API Token is available to authenticate Hevo on your PagerDuty account.
You are logged in as an Account Owner or Admin user, to obtain the API token. Else, you can obtain the API token from your account owner or administrator. Read User Types to know about the different types of user accounts in PagerDuty.
Creating the API Key
Hevo uses an API token to authenticate itself on your PagerDuty account.
Perform the following steps to create the access token:
Log in to your PagerDuty account.
In the title header of the PagerDuty Overview page, click Integrations, and select API Access Keys from the drop-down.
In the API Access Keys page, click + Create New API Key to create the API Key.
In the Create API Key window, specify a unique name for this API Key, and click Create Key.
Copy the API Key and save it securely like any other password.
You have successfully created your API Key. Use this key for creating Hevo Pipelines.
Configuring PagerDuty as a Source
Perform the following steps to configure PagerDuty as the Source in your Pipeline:
Click PIPELINES in the Asset Palette.
Click + CREATE in the Pipelines List View.
In the Select Source Type page, select PagerDuty.
In the Configure your PagerDuty Source page, specify the following:
Pipeline Name: A unique name for the Pipeline, not exceeding 255 characters.
API Key: The API key that you created in your PagerDuty account.
Click TEST & CONTINUE.
Proceed to configuring the data ingestion and setting up the Destination.
|Default Pipeline Frequency||Minimum Pipeline Frequency||Maximum Pipeline Frequency||Custom Frequency Range (Hrs)|
|1 Hr||1 Hr||24 Hrs||1-24|
Note: You must set the custom frequency in hours as an integer value. For example, 1, 2, 3 but not 1.5 or 1.75.
Pagination: An API response for each PagerDuty object fetches one page with a maximum of 100 records. However, you can configure PagerDuty using the REST API to retrieve up to 10,000 records via pagination, with the sum of
offsetparameters not exceeding 10,000. Here, the
limitis the maximum number of records that can be fetched by the API on each call, and the
offsetvalue is from which the API starts fetching in each subsequent run of Pipeline. Read Pagination for more information.
Rate Limit: PagerDuty imposes a limit of a maximum of 900 API calls per minute per organization to ensure that their system remains stable for usage by all users. Read API Rate Limits to know more about rate limits, and configure a suitable ingestion frequency for your Pipeline.
Schema and Primary Keys
Hevo uses the following schema to upload the records to the Destination database:
The following is the list of tables (objects) that are created at the Destination when you run the Pipeline:
|Business Services||Full Load||Contains the details of all the incidents affecting the business.|
|Change Events||Incremental||Contains the details of the updates to the product or system. For example, configuration changes.|
|Escalation Policies||Full Load||Contains the details of all the guidelines defined for service escalations. An escalation policy automates incident assignment and connects services with individual users.|
|Extension Schemas||Full Load||Contains the details of all the extensions used by the employees to communicate inside or outside the organization. For example, Slack, Generic Webhook and more.|
|Extensions||Full Load||Contains the details of all the applications attached to a service, to receive incident updates.|
|Incidents||Full Load||Contains the details of an issue that has occurred in a system and needs to be resolved.|
|Log Entries||Incremental||Contains the details of all the events and changes that happened at the time of the incident.|
|Maintenance Windows||Full Load||Contains the details of services temporarily disabled by PagerDuty for a set period of time.|
|Oncalls||Full Load||Contains the details of all the users available for responding to any incident, at a given point of time.|
|Rulesets||Full Load||Contains the details of the set of rules for creating and routing of events.|
|Schedules||Full Load||Contains the details of all the available on-call time slots for the users.|
|Services||Full Load||Contains the details of all the entities that you monitor, such as emails and databases.|
|Tags||Full Load||Contains the details about the label that is used to organize escalation policies, teams, or users into multiple categories.|
|Teams||Full Load||Contains the details of a group of users that represent an organization.|
|Users||Full Load||Contains the details of all the users that have access to the PagerDuty account.|
|Vendors||Full Load||Contains the details of all the third-party applications that can be integrated into PagerDuty.|
Hevo does not capture information for records deleted in the Source objects.
Hevo does not provide you with the option to select the historical sync duration for loading historical data. All the historical data in your Harvest account is loaded.
Refer to the following table for the list of key updates made to this page:
|Date||Release||Description of Change|
|Feb-17-2023||NA||Updated section, Source Considerations to add information about Pagination limit using RestAPI|