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

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

3 seemingly obvious but helpful Opsgenie alerting tips

This list was inspired by some recent chats that I've had with newer Opsgenie customers. Sometimes people get stuck doing something a certain way, or are forcing solutions to work together because of legacy, lack of budget, or "this is the way it's always been done" etc. When that happens, sometimes the features we use in a streamlined tool, aren't as intuitive as we may think. If you're a seasoned Opsgenie user the below might seem obvious. But if you're new to Opsgenie and/or incident management tooling in general, these little tidbits can save you some time and future headaches. 

 

incident management-incident.png

1. Only acknowledge an alert if you plan on doing something about it. 

The purpose of an alert is to notify the right people so that they can take action and solve or prevent a problem. If you acknowledge an alert (possibly as a reflex to receiving the notification), but don't plan to do anything about it, you're sending a confusing message. Your team and other responders will assume the problem is being taken care of, and then the alert becomes the tree that fell in the empty woods (no one heard it, no one knew about it). 

2. You do have to acknowledge an alert to prevent notifications from continuing. 

Each team has a list of escalation policies, routing rules, and on-call schedules. These all work together to notify the right people on call so they can take action quickly. Escalation policies work to prevent alerts from sliding under the radar and will continue to escalate the alert until someone acknowledges it. If a responder does not acknowledge an alert but begins working on it, the escalation policy will continue to notify folks until acknowledgement, and create confusion and likely duplicate work on the team. 

 

3. "Seeing"  an alert, stops your notification flow. 

Opsgenie is smart, and helps to reduce and prevent alert fatigue. If you're logged in to Opsgenie when an alert comes in (whether it be open on your phone or computer) and you click on that alert to see more information you will not receive notifications for that alert. Why? Because Opsgenie knows you "saw" it, and thus there is no need to notify you again. 


That's all for today. If you have a helpful tip or trick feel free to share it in the comments! 

5 comments

Jimmy Seddon Community Leader Mar 04, 2020

This is great @Kate Clavet!  I'm just getting started with help of other awesome members of your team so this is really helpful advice!

Like Kate Clavet likes this
Kate Clavet Atlassian Team Mar 04, 2020

That's awesome @Jimmy Seddon ! Thanks so much for sharing that with me. If you're willing I'd love to set up a chat to hear more about your specific experience. 

Best,
Kate 

While this is generally correct, it isn't absolute.

1: There are options to re-notify after a period of time.

2: While the default is to stop escalation on acknowledgement, you can chose to set it otherwise.

One thing that has bit us before. If a user is in multiple escalation levels, then they will not get notified if the issues is escalated.

for example. a common escalation case. Start with an on call user. Then escalate to thier manager, then escalate to the whole team.

We have people who expected that the oncall user would get notified at the initial level, and then again when the issue is escalated to the whole team. This is not the case. Once a users has been notified, even if a further escalation would make it seem like they would get notified again, they will not.

Regardless of escalation rules. (and not withstanding renotification settings) Once a user has been notified, they will not get notified again. (just like if they have seen the notification, they will not get further notifications even if thier personal rules would send a later alert.

Like Kate Clavet likes this
Kate Clavet Atlassian Team Mar 05, 2020

Thanks so much for sharing @Andrew Laden ! You are certainly correct, it's not absolute. That's what makes Opsgenie such a helpful tool for so many teams, it is truly flexible and can be created to suit various use cases. Thanks for sharing your insights, they are certainly helpful! 

Jack Community Leader Nov 24, 2020

I thought I would add a tip I just learned....

Use "No-one" in a rotation to 'skip' time periods. I was scratching my head on how to have someone on-call every-other weekend. By including "no-one" in the Participants field of a rotation you can make that happen...

Jack --> No-one --> Jack --> No-one...

Like Kate Clavet likes this

Comment

Log in or Sign up to comment
TAGS
Community showcase
Published in Opsgenie

Opsgenie and Amazon team up to launch new DevOps Guru integration - now available!

We’re proud to announce that our integration with Amazon DevOps Guru is now live. The Amazon and Opsgenie product teams have worked together to build a deep integration between Opsgenie and the new...

239 views 0 6
Read article

Community Events

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

Events near you