A user shared their experience trying to set up a Pagerduty integration in Scoutbees. They mention encountering difficulties as Pagerduty’s webhook is considered more of a REST API call instead of following the "webhook standard." However, it is possible that Pagerduty has updated this. A workaround suggested is to use Pagerduty’s email integration. URL mentioned: https://buttercms.com/blog/webhook-vs-api-whats-the-difference/
Read the entire ‘Troubleshooting Pagerduty Integration in Scoutbees’ thread below:
Pagerduty integration in Scoutbees… I have setup MS Teams… pretty straight forward. Anyone try to setup pagerduty in ScoutBees? I see the ability to add a webhook. Welp, diving in and see what i can figure out!
Maybe unsurprising to those that know me: I have tried. But, it was in October 2020, so this might have since been addressed by us or possibly pagerduty has made changes. The biggest issue back then was that what PD called a webhook, was more a Rest API call, not following the "webhook standard". For those who want a quick refresher on the difference https://buttercms.com/blog/webhook-vs-api-whats-the-difference/
More specifically, we sent the details about an alert in the Json body in what a true incoming webhook would be able to consume, but PD would not, because they expect the payload to be structured differently.
Now, if this is still the case? I think the only way we could fix it was by having a true PD integration using their APi instead of the generic webhook integration. I can’t remember that ever being built.
But it is possible that PD redid their homework and now supports "real webhooks"
they are using their events api 2.0 or something like that… but they do have email integration… so that could be the work around.. not have to fiddle with api or webhook stuff.. 🙂
Continue reading and comment on the thread ‘Troubleshooting Pagerduty Integration in Scoutbees’. Not a member? Join Here!
Categories: All Archives, ControlUp Scripts & Triggers, ControlUp Synthetic Monitoring