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.

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

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


1 badge earned


Participate in fun challenges

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


Gift kudos to your peers

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


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!


Combine Notification Policies

We are deploying our application on top of a shared Kubernetes based infrastructure. It sends alerts into OpsGenie via Prometheus and we have no control over thresholds etc.

We are having to maintain a Notification policy which does 2 things:

1 - If a specific tag value is "critical" then upgrade to a P2

2 - Occasionally filter for broken/noisy/spamming alerts when a new feature or change introduces this.

My question is can we have a policy that is effectively an Ignore list then our P" rule is simply:

if tag = critical and name NOT IN <other policy> 

1 answer

0 votes
Mona Singh
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Feb 27, 2023

Hi Jamie,

This is Mona here, happy to help :slightly_smiling_face:

As I understand, you would like to configure Alert Policy in such a way that it updates the priority to P2 if the tag value equals Critical & only triggers for conditions not specified in other Alert policies.

The reason I’m referring to Alert Policy here is that it changes or appends the alert properties like the message, description, or even responder of the alert before it’s created. Assign Teams or Users as responders as well. Alert policies have the option to process more than one policy. If the Continue to next policy option is enabled, the next policy is processed in the alert policy list. This chain execution stops at the first policy which has disabled this option.

However, Notification Policies exist only under Teams. Notification policies apply to notifications of alert actions, like new alert creation, acknowledge notifications, etc. These actions include delay/suppress, auto restart, and auto close.

For more details on the Alert & Notification Policy, you can refer to this doc.

Using Alert Policy, you can configure the matching conditions such that this policy applies to only specific alerts and is unique compared to other configured Alert policies. Please note that using another policy as a condition is not feasible as per the current design in order to avoid policy looping.

Hope it helps :) In case you have any further queries, please feel free to reach out to us by creating a ticket in this link and we’ll take it from there :)


Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events