We have a Slack webhook that's used to subscribe to a statuspage.io page for a 3rd party system we use. On a semi-regular basis, we get an email to the email address we used stating:
We've detected a problem with your webhook endpoint subscribed to the [3rd party] status page, so we've deactivated the webhook.
Please make sure that your webhook endpoint of https://hooks.slack.com/services/[...] is responding with a 2xx response code within 30 seconds of initial connection.
Once you're confident you've addressed the issue preventing the webhook from completing successfully, you should visit the [3rd party] status page to re-subscribe the endpoint to continue using it.
I understand that it's fruitless having a system continuing to call a broken webhook endpoint, but given the frequency with which this occurs (plus the fact that Slack webhooks rarely seem to fail elsewhere) I wonder if the failure handling for broken webhooks on the statuspage.io is a bit too aggressive?
The manual process required to resubscribe the webhook every time this happens is quite a pain, and means that it often doesn't get done which reduces the value of the functionality.
We're excited to announce the release of a long-requested feature on Statuspage. Now visitors to your status page can subscribe to get notified in Slack when you report an incident or maintenance. Th...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events