Uploaded image for project: 'Opsgenie'
  1. Opsgenie
  2. OPSGENIE-28

Auto-close associated alerts when an incident is closed and acknowledge when incident is resolved

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Description:

       
      Customer would like the associated alerts of an incident to automatically be closed, when the incident is closed.

      Also - acknowledge the associated alerts when the incident is resolved, just like the responder alerts.

       

      CS Description:

      None
       

      Performed Tests:

      None

            [OPSGENIE-28] Auto-close associated alerts when an incident is closed and acknowledge when incident is resolved

            as a VAR, we see most of our customers requesting this feature and we haven't been able to provide any easy/practical solution to it so far.

            We have tried to do this via REST API but the authentication method (Integration API Key vs Instance API Key) prevents us from doing this. 

            In our case, simply allowing the /v2/alert/:identifier/close REST endpoint to authenticate against the OG instance API key instead of the Integration key would be a sufficient workaround as we are already providing automation to close incidents from 3d party applications. 

             

            Thanks

            Olivier Botz added a comment - as a VAR, we see most of our customers requesting this feature and we haven't been able to provide any easy/practical solution to it so far. We have tried to do this via REST API but the authentication method (Integration API Key vs Instance API Key) prevents us from doing this.  In our case, simply allowing the /v2/alert/:identifier/close REST endpoint to authenticate against the OG instance API key instead of the Integration key would be a sufficient workaround as we are already providing automation to close incidents from 3d party applications.    Thanks

            This just might be what makes us go to PagerDuty.

            OpsGenie alerts are not well thought out and create a lot of noise, which results in teams ignoring real alerts.

            andre.thenot added a comment - This just might be what makes us go to PagerDuty. OpsGenie alerts are not well thought out and create a lot of noise, which results in teams ignoring real alerts.

            We very much need this.... doing it via actions/oec is likely possible, but users shouldn't need to jump through hoops when working on high priority issues.

            jira_infralinc added a comment - We very much need this.... doing it via actions/oec is likely possible, but users shouldn't need to jump through hoops when working on high priority issues.

            Hello,

            In addition to described above, the functionailty we need is that once the Associated alert is closed by Resolved event from 3rd party tool, then the incident + the Responder alert to be closed automatically as well, not manually.

            PagerDuty, which we're migrating from, has this behavior by default.

            Thank you.

            Yaoz Danilo added a comment - Hello, In addition to described above, the functionailty we need is that once the Associated alert is closed by Resolved event from 3rd party tool, then the incident + the Responder alert to be closed automatically as well, not manually. PagerDuty, which we're migrating from, has this behavior by default. Thank you.

              Unassigned Unassigned
              a3e616cd17e8 John M
              Votes:
              26 Vote for this issue
              Watchers:
              25 Start watching this issue

                Created:
                Updated: