Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,466,665
Community Members
 
Community Events
176
Community Groups

Webhook Updates Not Firing

I am attempting to deliver updates from my statuspage to a webhook endpoint where I can parse the information and take action based on it (Trigger VictorOps alert for the relevant team(s) when a component is switched from operational). 

I have setup a webhook in Azure LogicApps as well as several through free services online. I configured these  endpoints to respond with a 200 as described in the documentation.

Unfortunately I cannot get StatusPage to fire anything off. I am receiving email updates for every action, but none of my webhooks have received any data. 

1 answer

0 votes

Investigated this with Anthony in a support ticket, but wanted to share some information here as well.

At this time, Statuspage does not honor case-sensitive information in a webhook subscription URL. All addresses are stored as lowercase values.

In this specific case of using an Azure LogicApps webhook, there was a Shared Access Signature value being passed along in the webhook, which requires case sensitive validation. As information was being sent from Statuspage back to LogicApps, there was not an exact match in that SAS value, and thus the payload was rejected.

We've opened this for discussion internally, and if changes are made we will post an update on this thread.

Hello! Is this case sensitivity behavior still the same? I'm trying to troubleshoot similar behavior and the only thing I can see is that there are some caps in the webhook subscription url from the customer. Thanks!

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events