PagerDuty
Visualize PagerDuty services, teams, and users, map PagerDuty users to employees, and monitor changes through queries and alerts.
- Installation guide
- PagerDuty data model
Installation
You will need to create a General Access REST API key on PagerDuty for use in JupiterOne. See their documentation for more information.
Configuration in JupiterOne
To install the PagerDuty integration in JupiterOne, navigate to the Integrations tab in JupiterOne and select PagerDuty. Click New Instance to begin configuring your integration.
Creating a configuration requires the following:
The Account Name used to identify the PagerDuty account in JupiterOne. Ingested entities will have this value stored in
tag.AccountName
when theAccountName
toggle is enabled.Description to assist in identifying the integration instance, if desired.
Polling Interval that you feel is sufficient for your monitoring needs. You may leave this as
DISABLED
and manually execute the integration.Lastly, your PagerDuty API Key.
Click Create once all values are provided to finalize the integration.
Next steps
Now that your integration instance has been configured, it will begin running on the polling interval you provided, populating data within JupiterOne. Continue on to our Instance management guide to learn more about working with and editing integration instances.
Data Model
Entities
The following entities are created:
Resources | Entity _type | Entity _class |
---|---|---|
Service | pagerduty_service | Service |
Team | pagerduty_team | Team |
User | pagerduty_user | User |
Relationships
The following relationships are created:
Source Entity _type | Relationship _class | Target Entity _type |
---|---|---|
pagerduty_service | ASSIGNED | pagerduty_team |
pagerduty_team | HAS | pagerduty_user |
pagerduty_user | MONITORS | pagerduty_service |