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

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,460,668
Community Members
 
Community Events
176
Community Groups

Azure severity not mapping to Opsgenie priority

I'm working on alerting from Azure to Opsgenie. The severity options on the Azure side map from 0-4 while the Opsgenie priority maps from P1-P5. I tried setting "Priority" in the integration to "Custom value to Opsgenie priority" and then setting the mapped priority value to {{severity}} doesn't seem to work. All alerts come into Opsgenie as P3. I can confirm also that my Azure action group is set to disable the common alert schema, as mentioned in a another post.

Does anyone have a suggestion for how to properly map these to disparate values?

1 answer

1 accepted

1 vote
Answer accepted
Wei Wung Atlassian Team Dec 02, 2022

Hi @Emil Varona

How are you doing?  Thank you for reaching out!

Please take a look at the following articles on how you can extract the severity value:

https://community.atlassian.com/t5/Opsgenie-questions/OpsGenie-AWS-Cloudwatch-Alarms-Map-priority/qaq-p/1440305

https://community.atlassian.com/t5/Opsgenie-articles/How-to-Map-Alert-Priorities-in-Opsgenie/ba-p/2044304

https://community.atlassian.com/t5/Opsgenie-questions/How-to-parse-the-subject-and-the-properties-from-aws-cloudwatch/qaq-p/2097135

To determine which field the incoming alert's severity value is parsed into (or if it is just in the incoming payload), you would want to search the Debug Logs (under Settings) using the value of the incomingDataId from the bottom of the alert's Activity Logs tab found in the "Alert created via ..." log entry. 

Like in this community post, you would want to look at the "Processed incomingData" log entry to determine how the payload is parsed and to which field the severity value is captured into, if it is.

Then use one of the applicable methods mentioned in this community post to extract this value. 

The next step would be how you would map 0 to P1, 1 to P2, 2 to P3, etc.  We currently do not have a match-replace function in our implementation of regex, so you would need to use an Alert Policy to do that.  Alert Policies are available in Opsgenie's Standard plan or in JSM Premium plan and higher.

Hope the above helps or please feel free to open up an in-app chat (where available) or a ticket at support.atlassian.com so we can help take a look more closely.

Thanks for your response. I can report that the second community post did the trick. I appreciate your assistance. 

In short, I created an IF-THEN-ELSE scenario within the integration that mapped the severity to the related priority as described in the aforementioned post.

Like Wei Wung likes this

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
TAGS

Atlassian Community Events