PagerDuty Connector

Introduction

PagerDuty is a cloud-computing company launched in August 2009 to improve incident responses and safeguard users from IT threats.

It's software-as-a-service (SaaS) incident response management platform provides IT teams with knowledge about incidents as soon as they occur.

Purpose

PagerDuty offers two APIs: the PagerDuty API and the Events API. In this article and library content, we aim to demonstrate how the Events API operates. With the Events API, you can transmit any kind of events related to machine attributes, tables or analytics from a Tulip application or automations to your PagerDuty platform.

API Doc

The following Connector Function highlighted in this document have leveraged PagerDuty's Events API Docs.

Pre-Requisites

Subscribe to an account or free trial on PagerDuty's platform. On the website, you'll need to create a Service Integration, which you can find under the Integration menu. Once the service is created, it can be integrated via the Events API. Finally, import the PagerDuty connector from the library.

Set the following details on the imported Connector shown on the next step.

Tulip Connection Details

The following information would need to be configured on Tulip's HTTP connector.

Running On: Cloud Connector Host
Host: events.pagerduty.com
Port:443
TLS: Yes
Authentication: No Auth
Headers: No headers

Authentication

Authentication is done directly in the body of the functions, with the routing_key paramter.

This token can be set in the application as well in the "Token" inputs. This integration key can be located in the PagerDuty Platform -> Integrations -> Service Integrations -> Choose or create service -> Events API V2

Prebuilt Connector Functions

POST - Send Alert Event

Alert events create incidents on a service in PagerDuty. The incident will be assigned to the person on-call. This will generate a notification (phone call, SMS, email, or mobile push notification dependng on the on-call responder's preferences).

POST - Send Change Event

Change events provide context to responders when triaging an incident. Currently, they are shown in the PagerDuty web application in these places.