I am wanting to extract incident data for reporting purposes in a separate database. Is there a way to be alerted (via webhook) when an incident is changed in any way? I see the alert webhooks (which are kind of useful), but ultimately, they dont fire when the incident is updated. For example, upon marking an incident resolved, OG will trigger webhooks from the generated alerts. However, if someone goes back the incident and updates the Impact Duration fields, no further webhooks fire.
Is there any way to handle this without having to scrape all of the incidents via the API on timer?
Hi @dpetit !
Like you mentioned, we have an outgoing webhook integration which can be used to trigger a request to a custom endpoint based on actions on an Ospgenie alert (i.e. post to webhook when alert is created, closed, etc.)
However this integration can only be triggered off of alert actions in Opsgenie. There isn't a way to have it trigger for incident actions at this time. Like you said, for each incident there are "responder" alert(s) that are generated, which can be used to trigger the webhook. But these alerts don't get updated when you do something like update the impact duration field like you mentioned.
I can enter a feature request to be able to trigger a webhook integration directly based on actions taken to an incident in Opsgenie. But right now there isn't a way to trigger a webhook based on updating the impact duration field for an incident. I believe we will be adding more functionality around triggering integrations off of incident actions, as right now they are designed more around alert actions.
Let me know if you have anymore questions!
Thanks,
Samir
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I'm also interested in this feature as well, I'm looking for my application to be notified when an incident is resolved
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I'm interested in this as well can you link the feature request?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi! I have added additional upvotes to the feature request. Opsgenie feature requests are not public facing currently, so I am unable to share the link. But I have increased the request count on the feature request.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I am also interested in this feature request. Is there a status on this request?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello.
Any update on this issue? We are trying to integrate OpsGenie and Jira Service Desk and need to be able to close/update tickets when an incident is updated. Leveraging the Responder Alert is not reliable unfortunately.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi, any update on this? I really need this feature to automate the post-action when the incidents is created by alert or manual.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
We've resorted to using Power Automate to poll the Incident for a status change and then trigger additional steps from there.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi All - we now have public feature suggestions for Opsgenie in jira.atlassian.com
Here is the link to the suggestion to be able to integrate Opsgenie incidents with external systems (including webhook integration).
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.