We are actually evaluating opsgenie and we face to a question related to Incident and Responder alert.
We notice that when an incident is created from incident rules, it does different things :
Now we need at this stage to handle the incident from our team and we do not catch from documentation the correct process .
For instance we understand that the Alert responder is the entry point where people will work on to solve the incident.
So the scenario is as below :
Closing the Alert do not close the incident which remains open.
Question 1 :
Does the Responder Alert is the correct working source for the team or does it need to work from incident directly ?
Question 2 :
Is there any sync on Status between incident and Responder Alert. What I means is that if we close the incident, does the Alert is closed automatically or status handling need to be done independently on incident and Alert
Thanks for clarification
Taking action on the responder alert (i.e. acknowledge responder alert) does not update the incident itself. However, it does work the other way, i.e. resolving the incident, will acknowledge the responder alert(s) for that incident. And closing the incident, will close the responder alert(s).
There isn't a "right" vs "wrong" way necessarily. If you want to stop the responder alert from escalating so it doesn't continue notifying, then you would want to acknowledge the responder alert.
Otherwise, you can just take action on the incident itself, and that will update the responder alert(s).
Hello @Samir , I notice one strange things if we work on Incident details :
1 - There is not place to add notes ?
2 - We notice a button call INVESTIGATE but it is necessary to connect to a CI/CD why ? There is no way to have an invesigation without CI CD especially if the incident is from a network issue for instance ?
Hi @serge calderara ,
Yes - there are no notes on incidents, you can add entries to the incident timeline.
And connecting a CI/CD is required for incident investigation, because the incident investigation feature is what allows you to pull in past deployments from your CI/CD tool that could have been a potential cause of the incident.
So without connecting a CI/CD tool, there would be no use of the incident investigation feature.
hi @Samir thanks for your reply
This is not a logical approach that for Incident investigation you need to have a CI/CD.
The resaon for that is that incident does not necessary comes from a software deployement .
From our integration with dynatrace for instance, we would like to start an investigation on the incident which is pure an infrastruture case for which we absolutly do not need any CI/CD.
How this can be done from Incident in that case?
In the past, managing IT infrastructure was a hard job. It required a lot of manual effort and it was hard to keep track of all the necessary information (monitoring, scalability etc). Thankfully, as...
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