You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Greetings of the day.
We are facing challenges with Opsgenie Integration: Webhook alerts not creating any incident on Statuspage.
We've successfully established a Webhook integration between our vendor’s Poly status page and Opsgenie. This integration enables us to receive alerts from Vendor's Poly status page directly into Opsgenie. The primary goal of this integration is to ensure that our end users stay well-informed about any outages or scheduled maintenance by receiving alerts through Opsgenie to Atlassian Statuspage.
However, we've encountered a challenge in the integration process. While Opsgenie alerts receiving from other sources like Grafana and Runscope are working smoothly and are being forwarded to the Atlassian Statuspage, the same effectiveness is not being observed for alerts obtained through the Webhook integration with Poly's status page.
In other words, despite the successful configuration of alerts within Opsgenie for the status page, these configured alerts are not triggering incidents on the Atlassian Statuspage as expected. But the alerts from Grafana and Runscope are successfully making their way to the Statuspage, highlighting that the integration between Opsgenie and the Statuspage is functional.
Our objective is to rectify this issue and ensure that the alerts received via the webhook integration from Vendor's Poly status page to opsgenie are also able to initiate incidents on the Atlassian status page, just like the alerts from the other integrated tools (Grafana, Runscope).