PagerDuty integration is not working in Hipchat Server
Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.
Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
This is for an outdated version of Hipchat Server
This article applies to a version of Hipchat Server which will be deprecated soon. After that period the version will no longer be supported.
You should upgrade to a more recent version of Hipchat Server as soon as you can to take advantage of new features, and security and bug fixes.
Problem
After integrating Hipchat Server to PagerDuty, the integration does not work at all and the rooms are not notified for the PagerDuty activities.
Diagnosis
Environment
- Hipchat Server 2.0.7 and earlier
Cause
When you add an integration in PagerDuty with its type selected as "Hipchat", it will automatically integrate with Hipchat Cloud and it won't work with Hipchat Server.
Resolution
To integrate PagerDuty with Hipchat Server, please follow the steps below:
- Browse to your service in PagerDuty and click on the Integrations tab
- Click on Add an Extension
- Select the Generic Webhook type and name the extension as you would prefer
Set the endpoint URL to the URL below with your custom domain instead of "test.hipchat.com"
https://test.hipchat.com/v1/webhooks/pagerduty/?auth_token=YOURAUTHTOKEN&room_id=YOURID
Where "YOURAUTHTOKEN" is your v1 token generated under "Group Admin -> API" and "YOURID" is the actual ID of your room.
Please notice that usually when you copy your auth token and paste it in that URL, it adds a space right after the "=" sign (as in the example below), and the integration won't work with that space so you will need to remove it.https://test.hipchat.com/v1/webhooks/pagerduty/?auth_token= YOURAUTHTOKEN&room_id=YOURID
Additional notes:
- If the PagerDuty integration was working and stops after an Hipchat Server upgrade, it's possible that you ran across this bug
HCPUB-1407
-
Getting issue details...
STATUS
which is fixed in Hipchat Server 2.1.3