Feature Requests webhook alias
Completed
For reasons we have 3 opsgenie webhooks set up. While I can work out which one is which from the api key its not the greatest experience.
It would be good to be able to set a more human readable alias so that I can easily see which each of the webhooks does when configuring new checks or bulk updating.
bob walker
Created on April 20, 2021 · Last update on July 16, 2024
2 Comments
Yeah, that is a nice hack for this. Thanks for the tip.
Labels for updown webhooks have just been added:
https://headwayapp.co/updown-release-notes/webhook-improvements-260104
It's not the case for Slack-compatible webhooks though, for them you can continue to use the little hack (which I slightly improved): Add an anchor at the end of the URL to indicate an alias of your choosing. This anchor will not be sent to your server (it's a client-side HTTP feature) but it'll show in your recipient list and bulk edit screen instead of the URL, example:
https://example.com/xxxxxxx#channel-Ahttps://example.com/yyyyyyy#channel-BSign in to comment