PagerDuty

This guide outlines the PagerDuty connector type.

Connector paths

The PagerDuty connector has two paths:

• Service key: sends alerts and Cases one way to a single PagerDuty service, using a service integration key. This is the original PagerDuty connector and does not change.
• Bi-directional: keeps Cases and PagerDuty incidents in sync in both directions, using an account-level PagerDuty integration. It applies to Cases only and is opt-in. See the PagerDuty Bi-directional integration.

Connector configuration

A connector is a specific integration instance within a destination type that links Coralogix to a third-party vendor. The connector configuration defines how the connector communicates with its destination type and varies by destination type. See the PagerDuty connector configuration for details.

Message configuration

Each destination type has a notification schema structure per output type. Schemas define the structure of the message sent to the destination type. Presets expose this message configuration in a reusable format. See the PagerDuty message configuration for details.

Next steps