ReferenceDriverPagerdutyAlert Task

PagerDuty Alert Task

Learn how to send PagerDuty alerts from Synnax when statuses change.

The PagerDuty integration watches status keys and opens or resolves PagerDuty incidents when they change. Error, warning, and info variants send an event with the matching severity. Success resolves the open incident. Events are deduplicated by status key, so repeated changes update the existing incident.

The integration runs on the Synnax Core, not on the Driver, so the Core must reach events.pagerduty.com over HTTPS.

For the task lifecycle, see Task Basics.

Prerequisites

  1. A PagerDuty account.
  2. A PagerDuty service with an Events API v2 integration. In PagerDuty, open Services -> Service Directory, select the service, then Integrations -> Add Integration -> Events API v2.
  3. The 32-character integration key (routing key) from that integration.

Severity Mapping

Synnax Status Variant PagerDuty Severity
Error error, or critical when the alert sets errors_critical
Warning warning
Info info
Success Resolves incident

Supported Operating Systems

Platform Status
Windows ✓ Supported
Linux ✓ Supported
macOS ✓ Supported
Docker ✓ Supported

Task Configuration Reference

Parameter Type Required Default Description
routing_key string Yes - 32-character PagerDuty Events API v2 Integration Key
alerts array Yes - List of alert configurations

Alert Configuration Reference

Each alert maps a Synnax status key to a PagerDuty event. The task needs at least one alert that is not disabled.

Parameter Type Required Default Description
status string Yes - The Synnax status key to watch
disabled boolean No false Excludes the alert from the task
errors_critical boolean No false Map error variant to critical PagerDuty severity instead of error
component string No "" Component of the source machine (e.g., "engine-1")
group string No "" Logical grouping of components (e.g., "engines")
class string No "" Class/type of the event (e.g., "engine-failure"). Named class_ in Python

How-To