[DOCS] Integration with PagerDuty

[jonathanmarsaud]

Hi,

I successfully deployed Supercheck and really enjoy the product!
I'm now trying to integrate it with our 24/7 notifications system PagerDuty. I believed it will be easy as Supercheck takes WebHook integration, but PagerDuty does not deliver a webhook as a simple "Incoming WebHook link" as before (deprecated), but an "Events API v2" which need a JSON payload to be pass, instead of juste a simple link:

curl --request 'POST' \
--url 'https://events.pagerduty.com/v2/enqueue' \
--header 'Content-Type: application/json' \
--data '{
  "payload": {
      "summary": "Test alert",
      "severity": "critical",
      "source": "Alert source"
  },
  "routing_key": "<redacted>",
  "event_action": "trigger"
}'

How can we achieve the PagerDuty integration with Supercheck? As Supercheck mentions integration with PagerDuty, it will be a nice touch to add a support page of how it can be achieved.

[krish-kant]

@jonathanmarsaud looking into this.

[krish-kant]

Hi @jonathanmarsaud — thanks for raising this.

The issue: the Webhook notification provider already had a Body Template field in the UI, but the template was being ignored when actually sending alerts. Only the "Test Connection" button used it. This has now been fixed in v1.3.4-canary.2

Please check updates docs and let me know for any issue.

[jonathanmarsaud]

Hi @krish-kant , we finally tested the proposed version and it works well, PagerDuty correctly received Alert. But now, it seems that the parameter Alert on recovery in the Alert Settings window does not work properly. It sends another event to PagerDuty, but does not close the previously send Alert, creating in fact two alerts in PagerDuty Incident management 😅.

Do you have any clue for this?

[krish-kant]

Hi @jonathanmarsaud, thanks for testing and confirming.

You are right: PagerDuty Events API v2 requires recovery events to be sent as event_action: "resolve" with the same dedup_key as the original trigger event. A static webhook template using only "event_action": "trigger" will create a second PagerDuty incident instead of resolving the first one.

I have updated the webhook template support so Supercheck now exposes lifecycle-safe variables:

• {{pagerDutyEventAction}} sends trigger for failures and resolve for monitor recoveries.
• {{dedupKey}} keeps the trigger and recovery events correlated in PagerDuty.

You can try v1.3.4-canary.5 which will me merged in next release.

https://supercheck.io/docs/app/communicate/alerts

[jonathanmarsaud]

Thanks @krish-kant, will test this ASAP and I will report back here if it works well 👌