Skip to Content

PagerDuty connector for Jitterbit Integration Studio

Summary

The PagerDuty connector establishes access to PagerDuty.

The PagerDuty connector provides an interface for creating a PagerDuty connection, the foundation used for generating instances of PagerDuty activities. These activities, once configured, interact with PagerDuty through the connection.

The PagerDuty connector is accessed from the design component palette's Project endpoints and connectors tab (see Design component palette).

Connector overview

This connector is used to first configure a PagerDuty connection. Activity types associated with that connection are then used to create instances of activities that are intended to be used as sources (to provide data in an operation) or targets (to consume data in an operation).

Together, a specific PagerDuty connection and its activities are referred to as a PagerDuty endpoint:

PagerDuty activity types

  • Get Incident: Retrieves an incident from PagerDuty and is intended to be used as a source in an operation.

  • Create Incident: Creates an incident in PagerDuty and is intended to be used as a target in an operation.

  • Update Incident: Updates an incident in PagerDuty and is intended to be used as a target in an operation.

  • Create Note: Creates a note associated with an incident in PagerDuty and is intended to be used as a target in an operation.

  • Manage Incidents: Updates multiple incidents in PagerDuty and is intended to be used as a target in an operation.

  • List Incident: Retrieves multiple incidents from PagerDuty and is intended to be used as a source in an operation.

  • Create Status Update: Creates a status update associated with an incident in PagerDuty and is intended to be used as a target in an operation.

  • Snooze Incident: Snoozes an incident in PagerDuty and is intended to be used as a target in an operation.

Note

This connector is a Connector SDK-based connector, which may be referred to by Jitterbit when communicating changes made to connectors built with the Connector SDK.

Prerequisites and supported API versions

The PagerDuty connector requires the use of an agent version 10.1 or later. These agent versions automatically download the latest version of the connector when required.

The PagerDuty connector uses the PagerDuty REST API v2. Refer to the PagerDuty API Reference documentation for information on the schema nodes and fields.

Troubleshooting

If you experience issues with the PagerDuty connector, these troubleshooting steps are recommended:

  1. Click the Test button in the connection configuration to ensure the connection is successful and to ensure the latest version of the connector is downloaded to the agent (unless using the Disable Auto Connector Update organization policy).

  2. Check the operation logs for any information written during execution of the operation.

  3. Enable operation debug logging (for cloud agents or for private agents) to generate additional log files and data.

  4. If using private agents, you can enable connector verbose logging for this connector using this specific configuration entry of logger name and level:

    <logger name="org.jitterbit.connector.pagerduty" level="DEBUG"/>

  5. If using private agents, you can check the agent logs for more information.

  6. For additional troubleshooting considerations, see Operation troubleshooting.