PagerDuty

ENTERPRISE: Built-in integrations are available for Sensu Enterprise users only.

Overview

Create and resolve PagerDuty incidents for events. After configuring a service in PagerDuty, configure the handler (integration) with the provided service key.

Configuration

Example(s)

The following is an example global configuration for the pagerduty enterprise event handler (integration).

{
  "pagerduty": {
    "service_key": "r3FPuDvNOTEDyQYCc7trBkymIFcy2NkE",
    "timeout": 10
  }
}

Integration Specification

pagerduty attributes

The following attributes are configured within the {"pagerduty": {} } configuration scope.

service_key
description The PagerDuty service key to use when creating and resolving incidents.
required true
type String
example
"service_key": "r3FPuDvNOTEDyQYCc7trBkymIFcy2NkE"
filters
description An array of Sensu event filters (names) to use when filtering events for the handler. Each array item must be a string. Specified filters are merged with default values.
required false
type Array
default
["handle_when", "check_dependencies"]
example
"filters": ["recurrence", "production"]
severities
description An array of check result severities the handler will handle. NOTE: event resolution bypasses this filtering.
required false
type Array
allowed values ok, warning, critical, unknown
example
 "severities": ["critical", "unknown"]
timeout
description The handler execution duration timeout in seconds (hard stop).
required false
type Integer
default 10
example
"timeout": 30