Set up the
PagerDuty Connector so that you can create incidents and send events from a workflow.
Setup has two parts: a PagerDuty connection for every action except Send event, and a PagerDuty Events connection for Send event itself.
You need the app-engine:apps:install permission.
Use the
PagerDuty Connector with a PagerDuty API key to automate incident creation and retrieve on-call information via the PagerDuty REST API.
Workflows requires some permissions to run actions on your behalf.
Other permissions are required by actions that come bundled with the
PagerDuty Connector itself.
To fine-tune permissions granted to Workflows:
app-settings:objects:readstate:app-states:readstate:app-states:writestate:app-states:deleteFor more on general Workflows user permissions, see Manage workflow permissions.
To interact with PagerDuty, you need an API key. To learn how to obtain it, refer to the PagerDuty official documentation.
You need a configured connection for each of your PagerDuty environments.
The Send event action uses the PagerDuty Events API v2 and requires a separate Events connection configured with a routing key. Use this connection to trigger, acknowledge, and resolve incidents in PagerDuty directly from a workflow.
A routing key is a 32-character integration key that identifies the PagerDuty service integration or the global integration that receives events from Dynatrace.
To get the routing key, see the PagerDuty documentation:
You need a configured events connection for each PagerDuty service that receives events from Dynatrace.
To add PagerDuty connection settings, you need the following permissions:
ALLOW settings:objects:read, settings:objects:write, settings:schemas:read WHERE settings:schemaId = "app:dynatrace.pagerduty:connection"
To add PagerDuty Events connection settings, you need:
ALLOW settings:objects:read, settings:objects:write, settings:schemas:read WHERE settings:schemaId = "app:dynatrace.pagerduty:events-connection"
For more details, see Permissions and access.