Table: pagerduty_service_integration - Query PagerDuty Service Integrations using SQL

PagerDuty Service Integrations are connections between PagerDuty and various other systems, tools, and services. These integrations allow incidents to be triggered, acknowledged, and resolved within PagerDuty based on events occurring in the connected systems. They form a crucial part of incident management workflows, helping teams to respond quickly and effectively to operational issues.

Table Usage Guide

The pagerduty_service_integration table provides insights into the integrations between PagerDuty and other systems. As an incident manager, you can use this table to understand the sources of incidents within your PagerDuty environment, including the types of integrations, their configurations, and their associated services. This information can help you to optimize your incident response processes and ensure that your team has the necessary context to resolve incidents efficiently.

Examples

Basic info

Explore which PagerDuty service integrations have been created by analyzing their names, IDs, and creation dates. This can provide insights into your system's integration history and help you understand the vendor details associated with each service.

select
  name,
  id,
  service_id,
  created_at,
  jsonb_pretty(vendor) as vendor
from
  pagerduty_service_integration;

select
  name,
  id,
  service_id,
  created_at,
  vendor
from
  pagerduty_service_integration;

List all vendor specific integrations of a service

Discover the segments that have specific integrations with vendors for a service. This can be useful to identify and manage third-party dependencies and assess potential risks associated with vendor-specific integrations.

select
  name,
  id,
  service_id,
  created_at,
  vendor ->> 'summary' as vendor_name
from
  pagerduty_service_integration
where
  vendor is not null;

select
  name,
  id,
  service_id,
  created_at,
  json_extract(vendor, '$.summary') as vendor_name
from
  pagerduty_service_integration
where
  vendor is not null;

Schema for pagerduty_service_integration

Name	Type	Operators	Description
_ctx	jsonb		Steampipe context in JSON form.
created_at	timestamp with time zone		The date/time when this integration was created.
html_url	text		An URL at which the entity is uniquely displayed in the Web app.
id	text	=	An unique identifier of the integration.
integration_email	text		Specify for generic_email_inbound_integration. Must be set to an email address @your-subdomain.pagerduty.com.
integration_key	text		Specify the integration key for the service integration.
name	text		The name of this integration.
self	text		The API show URL at which the object is accessible.
service	jsonb		Describes the information about the queried service.
service_id	text	=	An unique identifier of the queried service.
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.
vendor	jsonb		Describes the information about a specific type of integration.

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_service_integration