Connector Configuration

This guide presents the connector configuration for the PagerDuty destination type.

Configuration

UI label	API field name	Type	Required	Allows notification source type overrides	Description
Service key	`integrationKey`	`String`	true	true	Also known as an Integration Key, this unique identifier allows notifications to be sent to a specific PagerDuty service.
Dynamic service key	`dynamicintegrationKey`	`String`	false	true	Specify a dynamic, data-driven value for the service key using alert metadata. Useful if you need to route alerts to different PagerDuty services based on different conditions.

Templating for dynamic routing

The Service key field supports dynamic templating, enabling dynamic routing by inserting variables into the notification configuration. This allows events to be sent to different services within PagerDuty based on their attributes.

Here is an example Dynamic service key configuration:

{% if alert.groups['team_name'] == 'alpha'%}
  930aaaaaaaaaaaaaaaaaaaaaaaaaa0d1
{% elif alert.groups['team_name'] == 'beta' %}
  930bbbbbbbbbbbbbbbbbbbbbbbbbb0d1
{% else %}
  930xxxxxxxxxxxxxxxxxxxxxxxxxx0d1
{% endif %}

Message Configuration

Next Message Configuration