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

Alert Rules vs Alert Policies Best Practice

What is the best practice on when to use Alert Rules vs Alert Policies? The documentation (Alert creation flow | Opsgenie | Atlassian Support) describes the process of alert creation. First we have "Integration create alert rules", then the "Global alert policies" followed by "Team alert policies". I understand the difference between global and team alert policies and why you'd want to use one over the other but don't know what's the best practice with using the rules within the integration configuration vs applying alert policies afterwards.

I'm currently applying most of my logic at the Integration level, and can see that there are plenty of filters available there to support future use cases, but don't quite understand why you'd also have alert policies that seem to be able to do similar things.

What are the pros and cons of each approach? 

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.
Sep 28, 2023 • edited Sep 29, 2023

Hi @James Allen 

Great question! While integration actions and policies can perform the same function of modifying alerts, with the policies being processed only after the initial 'create' action, they are able to perform an additional round of modifications.

While the initial 'create' action might add some custom field from the payload to a different field in the alert body, the policy can then filter for that field and perform additional modifications based on it's value. 

Policies can also be paused and automatically disabled and enabled using schedules via maintenance policies, so if you have a very specific modification that you may need to change, delete or pause at some point, it may be better to use a policy, rather than having to modify the integration configuration. This allows for better separation of concerns. 

The other difference is that policies have a time-based filter, while integration actions do not. 2023-09-28_20-47-41.png

Thanks for that @John M I will continue to use the create actions for the alerts for now and then will rely on policies in future when I want to add more complex actions or if we decide to have different results depending on timing.

Like John M likes this

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events