question PagerDuty Webhook Inconsistencies in Community Central forum

PagerDuty Webhook Inconsistencies

andyrod156 — Tue, 09 Jul 2024 18:32:43 GMT

Hello,

We have the integration set up with PagerDuty, however, updates do not come in from PagerDuty. ServiceNow side creates a PagerDuty ticket and is able to update with Notes and Status.

Checking the Webhooks in ServiceNow, each Health Check reads "SNow Entity Lined to a PagerDuty Service has an incorrect Webhook ID".

I have double and triple checked the PagerDuty Webhook ID, Service and Escalation ID and everything matches up with what PagerDuty shows.

I'm stumped as to what else could cause these inconsistencies.

Re: PagerDuty Webhook Inconsistencies

Sam_SN — Tue, 17 Sep 2024 18:18:25 GMT

I am also facing the same issue after Washington DC Upgrade. I have validated everything, cleanup the webhooks, created new webhooks however I still don't see any webhook import record being created in ServiceNow when I am triggering the incident in PagerDuty. When I try to test the webhook, it goes into disabled state after some time which means ServiceNow is not accepting the payload request from PagerDuty.

On the other hand, It is working fine from ServiceNow to PagerDuty and all the updates are being synced.

Re: PagerDuty Webhook Inconsistencies

andyrod156 — Tue, 17 Sep 2024 19:00:30 GMT

We actually was able to get this resolved after realizing that our PagerDuty instance was only active in Prod.

We were working off our Dev environment in ServiceNow and the outbound services were off so those updates were not being sent to PagerDuty via Webhooks.

We then tested in our Prod environment and were successful in both outbound and inbound communications from SN>PD as well as PD>SN.

I'm not sure if that would help in any way. Best of luck to you in your work.

Re: PagerDuty Webhook Inconsistencies

Sanny007 — Tue, 24 Sep 2024 23:37:41 GMT

Hi - Did you use extension v7.0 or v3 webhook?

Re: PagerDuty Webhook Inconsistencies

Sam_SN — Wed, 25 Sep 2024 17:11:28 GMT

I resolved this issue as there was an authentication issue with the webhook. I had to remove old webhooks and create new v3 webhooks.