Sazabi
Integrations

Integrating Sazabi with PagerDuty

Route Sazabi alerts to PagerDuty for incident management and on-call scheduling.

Learn how to integrate Sazabi with PagerDuty so you can route alerts directly to your on-call team and manage incidents through PagerDuty.

About the Sazabi integration for PagerDuty

The Sazabi integration for PagerDuty routes alerts directly to PagerDuty for incident management and on-call scheduling. When Sazabi detects issues in your telemetry data, alerts automatically trigger PagerDuty incidents.

With the Sazabi integration for PagerDuty, you can:

  • Automatically trigger PagerDuty incidents from Sazabi alerts.
  • Map Sazabi alert severities to PagerDuty priority levels.
  • Include relevant context like error messages and affected services in each incident.
  • Link back to Sazabi for deeper investigation.

Prerequisites

Before you connect PagerDuty, make sure you have:

  • A Sazabi account. Request access at sazabi.com
  • A PagerDuty account with permission to manage integrations.
  • An Events API v2 integration configured in PagerDuty.

Installation

Get your PagerDuty routing key

In PagerDuty, go to Services -> Service directory and select your service. Under the Integrations tab, find or create an Events API v2 integration. Copy the Integration Key (also called the routing key).

Configure severity mapping

Under Settings -> Integrations -> PagerDuty, configure how Sazabi alert severities map to PagerDuty incident priorities.

How it works

Once connected, Sazabi sends alerts to PagerDuty using the Events API v2. Each alert includes:

  • Error messages and descriptions
  • Affected services
  • Links back to Sazabi for deeper investigation

Severity mapping lets you control which Sazabi alert severities create PagerDuty incidents and at what priority level. For example, you might configure critical Sazabi alerts to create high-priority PagerDuty incidents, while warning alerts create low-priority incidents.