Overview
Purpose
Automatically escalate incidents to on-call engineers and sync acknowledgment/resolution actions.
What It Does
Automatically creates incidents in your paging system when Jira incidents are created
Syncs acknowledgment and resolution actions between Jira and your paging system
Routes incidents to the appropriate on-call team based on product ownership
Supported Platforms
PagerDuty
We support two-way sync with PagerDuty. When an incident is created or status changed in Phoenix Incidents, we create and update the status of the associated incident in PagerDuty.
Splunk On-Call
We support two-way sync with Splunk On-Call. When an incident is created or status changed in Phoenix Incidents, we create and update the status of the associated incident in Splunk On-Call.
Note: Splunk and PagerDuty only support 3 statuses (Triggered, Acknowledged and Resolved), and that once a PagerDuty/Splunk Incident is resolved, it can not be changed (unlike an Incident type in Jira).
How to Configure
Select Paging Platform
Before you begin setting up your paging integration, you need to select which one you are using.
PagerDuty
You must key in two pieces of information, REST API Key & Bot Email
API KEY: Create an API KEY in PagerDuty and paste the key in REST API Key
Bot Email: Enter the email address that was used to create the API KEY in Bot email. The email must match the email that created the API KEY. We recommend using a bot/service account for this. Something that isn't tied to a specific user, so if that person leaves, the integration doesn't break.
Once the information is entered in, click Connect PagerDuty
Congratulations, you now have connected Phoenix Incidents to PagerDuty!
Splunk On-Call (previously VictorOps)
This is a 2 step process.
Step 1:
You must key in four piece of information
API ID: Create an API KEY in VictorOps and paste the API ID here
API KEY: Paste the API KEY you created above here
Organization Slug: This is a unique identifier found in your VictorOps URL (e.g.,
https://portal.victorops.com/client/{Org_ID}) and is used to identify and link your accountBot Username: This is the username of the user that configured the API KEY. The username must match the username that created the API KEY. We recommend using a bot/service account for this. Something that isn't tied to a specific user, so if that person leaves, the integration doesn't break.
Once the information is entered in, click Save Credentials
Step 2:
Follow the instructions and click Test Webhook
On successful connection, you will get the confirmation
Congratulations, you now have connected Phoenix Incidents to VictorOps!