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 for Events API v2, configure the handler (integration) with the provided integration key.

Configuration

Example(s)

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

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

Integration Specification

pagerduty attributes

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

routing_key
description The PagerDuty integration key to use when creating and resolving incidents. NOTE: If you’re using an integration key for PagerDuty’s Events API v1, you can continue to use service_key instead of routing_key.
required true
type String
example 
"routing_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
default 
["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