PagerDuty
Version: 3.0.0
PagerDuty is an operations performance platform delivering visibility and actionable intelligence across the entire incident lifecycle.
Connect PagerDuty with LogicHub
- Navigate to Automations > Integrations.
- Search for PagerDuty.
- Click Details, then the + icon. Enter the required information in the following fields.
- Label: Enter a connection name.
- Reference Values: Define variables here to templatize integration connections and actions. For example, you can use https://www.{{hostname}}.com where, hostname is a variable defined in this input. For more information on how to add data, see 'Add Data' Input Type for Integrations.
- Verify SSL: Select option to verify connecting server's SSL certificate (Default is Verify SSL Certificate).
- Remote Agent: Run this integration using the LogicHub Remote Agent.
- API Token: All PagerDuty REST APIs require authentication. In order to make successful requests to the API, you must provide a valid form of authorization.
- Generic API Integration Key: The GUID of one of your "Generic API" services. This is the "Integration Key" listed on a Generic API's service detail page.
- API V2 Integration Key: The GUID of one of your Events API V2 integrations. This is the "Integration Key" listed on the Events API V2 integration's detail page.
- After you've entered all the details, click Connect.
Actions for PagerDuty
Trigger Incident
Automatically trigger a PagerDuty incident.
Input Field
Choose a connection that you have previously created and then fill in the necessary information in the following input fields to complete the connection.
Input Name | Description | Required |
---|---|---|
Incident Title | Column name to pull incident title from. | Required |
Incident Explanation | Column name to pull incident explanation from. | Required |
Trigger Incident V2
Automatically trigger a PagerDuty incident (V2).
Input Field
Choose a connection that you have previously created and then fill in the necessary information in the following input fields to complete the connection.
Input Name | Description | Required |
---|---|---|
Incident Title | Column name to pull incident title from. | Required |
Incident Explanation | Column name to pull incident explanation from. | Required |
Release Notes
v3.0.0
- Updated architecture to support IO via filesystemv2.0.7
- Added documentation link in the automation library.
Updated about 1 year ago