Table: pagerduty_priority - Query PagerDuty Priorities using SQL

PagerDuty is an incident management platform that provides reliable incident notifications via email, push, SMS, and phone, as well as automatic escalations, on-call scheduling, and other functionality to help teams detect and fix infrastructure problems quickly. The PagerDuty Priorities feature allows users to define the relative urgency of incidents, which can help streamline response and resolution processes.

Table Usage Guide

The pagerduty_priority table provides insights into the different levels of urgency that can be assigned to incidents in PagerDuty. As an Incident Manager or DevOps engineer, explore priority-specific details through this table, including the name and description of each priority level, and the time frame in which incidents at each priority level should be resolved. Utilize it to better understand and manage your team's response to incidents of varying urgency.

Important Notes

To list the priorities, first enable and configure your priorities.

Examples

Basic info

Explore the priorities in your PagerDuty setup to gain insights into their names, IDs, and descriptions, helping you better understand and manage your incident response hierarchy.

select
  name,
  id,
  description,
  self
from
  pagerduty_priority;

select
  name,
  id,
  description,
  self
from
  pagerduty_priority;

List event rules with highest priority (P1)

Discover the segments that have the highest priority (P1) in the event rules. This can be useful for identifying and prioritizing the most critical rules for incident management.

with priority as (
  select
    id
  from
    pagerduty_priority
  where
    name = 'P1'
)
select
  rs.id as rule_id,
  rs.ruleset_id,
  rs.disabled
from
  pagerduty_ruleset_rule as rs,
  priority as p
where
  p.id = rs.actions -> 'priority' ->> 'value';

select
  rs.id as rule_id,
  rs.ruleset_id,
  rs.disabled
from
  pagerduty_ruleset_rule as rs,
  (
    select
      id
    from
      pagerduty_priority
    where
      name = 'P1'
  ) as p
where
  p.id = json_extract(rs.actions, '$.priority.value');

Schema for pagerduty_priority

Name	Type	Operators	Description
_ctx	jsonb		Steampipe context in JSON form.
description	text		The user-provided description of the priority.
html_url	text		An URL at which the entity is uniquely displayed in the Web app.
id	text		The ID of the priority.
name	text		The user-provided short name of the priority.
self	text		The API show URL at which the object is accessible.
sp_connection_name	text	=, !=, ~~, ~~, !~~, !~~	Steampipe connection name.
sp_ctx	jsonb		Steampipe context in JSON form.
summary	text		A short-form, server-generated string that provides succinct, important information about an object suitable for primary labeling of an entity in a client. In many cases, this will be identical to name, though it is not intended to be an identifier.
title	text		Title of the resource.
type	text		The type of object being created.

Export

This table is available as a standalone Exporter CLI. Steampipe exporters are stand-alone binaries that allow you to extract data using Steampipe plugins without a database.

You can download the tarball for your platform from the Releases page, but it is simplest to install them with the steampipe_export_installer.sh script:

/bin/sh -c "$(curl -fsSL https://steampipe.io/install/export.sh)" -- pagerduty

You can pass the configuration to the command with the --config argument:

steampipe_export_pagerduty --config '<your_config>' pagerduty_priority