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
Hi, I have a scenario whereby I only wish to add a team as a responder on an alert when I get multiple occurrences of that alert. I'm aware of being able to delay notifications based upon de-deduplication count, but I can't see anyway to delay adding a team as a responder. In this use case, I don't want the additional responder to take any action (and not even be aware of the alert) until it occurs multiple times.
Hi @William Lee ,
That unfortunately is not possible at this time, but we have an open feature request you can follow, watch and vote for here: https://jira.atlassian.com/browse/OPSGENIE-471
Like you mentioned, closest functionality Opsgenie has at this time is with a notification policy that delays / suppresses notifications until a deduplication threshold is met.
You could also auto-close the alert after x-time through the notification policy so no action is realistically needed on these types of alerts:
Thanks, @Nick H. That looks like the feature I need! Unfortunately, the auto-close suggestion won't work for me as I also want to be able to include time as additional criteria i.e. only assign a team as a responder if an alert occurs multiple times (with the same alias) within a 30-minute period and it's possible the additional responder may act before the 30 minutes is up.