
PagerDuty
Triggers, acknowledges or resolves a PagerDuty incident
Configuration
| Option | Description |
|---|---|
Routing keyType: string Required: True | The Events API v2 integration key from your PagerDuty service. |
RegionType: choice Required: True | The PagerDuty service region your account runs in. A routing key only works in its own region. |
Event actionType: choice Required: True | Trigger opens an incident. Acknowledge and resolve update the incident with the same dedup key. |
Dedup keyType: string Required: False | Events with the same key update one incident. Acknowledge and resolve need it. If you leave it empty, PagerDuty opens a new incident for each trigger. |
SummaryType: string Required: True | The incident title. PagerDuty keeps the first 1024 characters. |
SourceType: string Required: True | The system that has the problem. |
SeverityType: choice Required: True | Any other value is sent as error. |
ComponentType: string Required: False | The part of the source system that has the problem. |
ClassType: string Required: False | The type of the event, for example firing. |
Custom detailsType: json Required: False | Extra data that PagerDuty shows on the incident and can use in event rules. |
LinksType: json Required: False | A list of links with href and text that PagerDuty shows on the incident. |
Using our REST API you can create this destination like so: