Trigger Alert
The Trigger Alert step opens a new incident in PagerDuty. If an open incident with the same Alert ID already exists, PagerDuty returns the existing incident and does not create a duplicate.
Opens a new incident in PagerDuty. If an open incident with the same Alert ID already exists, PagerDuty returns the existing incident and does not create a duplicate. This makes Trigger Alert safe to call repeatedly for the same source event.
Fields
|
Provider |
See the Common Fields section in Alert Steps. |
|
Summary (required) |
Short, one-line description of what happened. PagerDuty displays this as the incident title and across mobile push notifications. |
|
Severity (required) |
One of:
Severity determines the notification policy that PagerDuty uses to decide how aggressively to page. |
|
Service (required) |
The PagerDuty service that owns the new incident. The dropdown defaults to the service that you selected as the Default service on the PagerDuty connector, but you can override it per-step. The Service determines which escalation policy and on-call schedule fire. |
|
Source (optional) |
Free-text identifier of where the alert came from (a hostname, an IP, a Check Point Firewall name, an Endpoint device name, and so on). PagerDuty records this for context. It is not used for deduplication. |
|
Alert ID (optional) |
See the Common Fields section in Alert Steps. |
|
Description (optional) |
Long-form context for the incident. Up to 16,384 characters. PagerDuty forwards the text end-to-end and displays it in the incident body. |