Why is there no reference to the URL to send the web hook to in the Notification Template setup? Shouldn't there be a part of the trigger that incorporates "https://events.pagerduty.com/v2/enqueue". I'm having no luck getting a notification into PagerDuty from PRTG

Hello Ben
Unfortunately, the link that you provided seems not to be working on my side. Could you double-check it?
When dealing with notifications there are a lot of steps that need to be taken to properly send it out to the Vendor, in this case, Pager duty.
We need to determine how far you are getting in this process.
In other words, can you confirm the notification is actually being sent out and received at Pager duty? Can you check in Logs/System events/Notification Related, and look for any "error code" or "status ok"?
Feel free to open a support ticket to further investigate this as I believed it would be a lot faster.

So I get the ok status in PRTG but nothing shows up in PagerDuty. Pagerduty gives me a new URL that is not at all like whats in the script, infact the script URL returns a 404 where the pagerduty one https://events.pagerduty.com/v2/enqueue does not.

step 4 not have xxxx value. pagerdut update maybe.

See https://www.screencast.com/t/HRmDStWy7ao

Hello Dorian
The image provided seems to be from the Pager duty page. The step you are referring to seems to be a URL. Can you confirm how the URL looks like at this step?
Let me know.
If the documentation needs to be updated,We will be happy to proceed.

This documentation seems to be out of date, and I can't get it to work.

1. On step 3 on the Add A Service page (now called Create a Service), there is no "Use our API directly" option. The first page only has a Name and Description field. Page 2 lets you select an escalation policy or create a new one. Page 3 lets you select an integration, however Use our API directly is not an option. One of the selectable options is named 'Events API v2' and another one (if you search) is called 'PRTG Notification For PagerDuty Events API v2' which seems promising, but not at all what this documentation describes. Incidentally if you add that integration, there's a documentation link which leads to this page.

2. On step 5, the developer tools menu is gone completely, however you can find 'API Access Keys' inside a new menu item named 'Integrations' which lets you generate an API key

3. If you examine the PagerDuty.ps1 script, it links to the URL "https://api.pagerduty.com/incidents", but the PagerDuty page lists the integration URL as "https://events.pagerduty.com/v2/enqueue" -- should we be editing the script for the URL specified in the integration or leaving it as provided?

I have tried both of the listed integration types, at both of the URLs and while I can see script running and the web queries going out (looking at it in Wireshark) so far I have not been able to see anything actually come into PagerDuty, and the return traffic from PagerDuty is [ACK, RST] like the server is saying I got your message but I'm not interested.

Hello Andrew
I'll be reporting this issue and have this KB link updated asap.
Thank you for letting us know.

Does anyone know if something with pagerduty has changed? I've tried multiple times to setup this integration multiple times and pagerduty never shows that it's received anything from PRTG even though PRTG is showing it's successfully executing the powershell script.

Hello there.
Thanks for your question
Yes, the Pager duty page was recently updated with more information, The last update was done on Jan the 9th 2023.
If you are not getting any error from PRTG then it would be advised to contact Pager duty support, and then see what's actually being sent to them and how they are handling this information.