Customizing PagerDuty Alerts

To customize event alerts sent to PagerDuty event sinks, use the @pagerduty. prefix for keys. For example, if you want to customize payload.source, use @pagerduty.payload.source as the key. Any keys prefixed with @pagerduty. will only be used for the PagerDuty alert. Any keys not prefixed with @pagerduty. will be routed to the payload.custom_details object.

See the PagerDuty API for the request body information.

PagerDuty alerts will work without any custom formatting, as Scanner provides defaults for the following required/important keys:

Key	Default
payload.summary	{{@alert.name}}
payload.source	scanner.dev
payload.timestamp	{{@alert.timestamp}}
payload.severity	critical
event_action	trigger
dedup_key	{{@alert.detection_rule_id}}
routing_key	The integration key provided in the PagerDuty event sink configuration