Raygun & Pagerduty

Hi resarf,

Apologies for the delay in getting back to you on this one. Just wanted to post an update and let you know we've recently released Webhook support for Alerting. This means triggered alerts notifications can now be sent to any URL as JSON formatted data. PagerDuty looks like they support POSTing JSON data to their Events v2 API and allow the transformation of that data into an expected format via their Custom Change Event Transformer. This might be a good option to achieve your desired result.

Kind regards, Matt

I'll leave Matt to respond to the main request, but as a note:

It would be much easier if you supported a generic email in notifications

This is something we're discussing. Biggest issue is abuse (you'd be amazed, we even get spammers automating our 'invite a team member' just to inject a message as the name of the user being invited...).

So being mindful of how we open up the system to allow arbitrary emails, BUT, don't end up getting ourselves blacklisted everywhere for spam (which of course also costs us money to send).

Implementing a basic 'any email address would be fine' is relatively easy, ensuring that it works for everyone, but not abusers, is where there is some complexity :-) It's not a 'no', just wanted to provide some context on our internal discussions about this :-)

I hope that helps, and I'll leave you with Matt about the overall improvements we can make with PagerDuty.

John-Daniel Trask

Hi Resarf,

Thanks for the feedback. I did some further digging and testing and it looks like you're correct. PagerDuty do allow sending custom events via a webhook endpoint, but unfortunately it appears this only supports emitting change events rather than full trigger events. My only other suggestion at this point would be to receive the webhooks to an endpoint on your end and send them to PagerDuty or use an integration platform like Zapier. Appreciate your suggestions for how we can improve this, I'll get these raised with our product team.

Thanks,

Matt