On this page

• Start Free Trial

Schema Structure

Each destination type has specific schema structures tailored to its output format. For PagerDuty, the default output consists of the following key fields:

Field	Description
Summary	A brief text summary of the event, used to generate the summaries/titles of any associated alerts.
Severity	The perceived severity of the status the event is describing with respect to the affected system. Accepted values: critical, error, warning, info.
Source	The unique location of the affected system, preferably a hostname or FQDN.
Deduplication key	Identifies the alert to trigger or resolve.
Timestamp	The time at which the event was generated. Should be an ISO 8601-compatible date or Unix time in seconds or milliseconds.
Component	[Optional] Component of the source machine that is responsible for the event.
Group	[Optional] Logical grouping of components of a service.
Class	[Optional] The class/type of the event.
Custom details	[Optional] Additional details about the event and affected system. Defaults to {}.
Client name	[Optional] The name of the monitoring client that is triggering this event.
Client URL	[Optional] The URL of the monitoring client that is triggering this event or the ID of the PagerDuty alert.

Previous Connector Configuration

Next Connector Configuration