Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

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

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

OpsGenie Conditional alert silence

Иван Поваляев
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
Oct 25, 2023

Good day! 

We use Zabbix and Prometheus for monitoring. They are sending alerts to opsgenie and those alerts are routed to different Teams channels. So I was wondering can we silence alerts from different sources based on conditions (like name, tag etc.) in opsgenie.

E.g. Some server goes down - we receive Zabbix alert that it is indeed down and then Prometheus alerts that some services dependent on this server are failing. So the idea is to mute Prometheus alerts based on the condition that we already received alert from Zabbix. At this point it doesn't matter whether we receive them as alerts in ALERTS list, just not sending notification will do. Much like alert inhibition in Prometheus.

Thank you!

1 answer

1 accepted

0 votes
Answer accepted
John M
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Oct 25, 2023

Hi @Иван Поваляев ,

You can silence alert notifications based on tags and other alert attributes using team-based notification policies.

The alerts must be assigned to the team where the policies are configured for notification policies to be applied. 

Keep in mind, this would only work if you could configure some way for only the alerts that you didn't want to notify to have those tags. There is no way to have conditions based on an existing alert.  

So, for example, you wouldn't be able to check your open alerts to see if an open Zabbix alert exists before deciding whether to silence a Prometheus alert whose service is dependent on that Zabbix server.

Иван Поваляев
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
Oct 26, 2023

Got it. Thank you very much. 

Like John M likes this

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events