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,456,779
Community Members
 
Community Events
176
Community Groups

Azure integration not parsing properties block

If I set some json values on my azure alerts in the data.alertContent.properties block how can I access them from opsgenie?

It looks like they are just ignored, even the docs page has them set but then their lost: https://docs.opsgenie.com/docs/microsoft-azure-integration

Is this just a limitation of opsgenie or is there a way to pass values from azure to opsgenie to give an alert more context.

My use case here is I add tags to my alerts which give them content to which client they correspond and I would like to tag my alerts as such.

1 answer

1 accepted

0 votes
Answer accepted
Samir Atlassian Team Mar 16, 2021

Hi @Matt Browne ,

 

Anything that Opsgenie is receiving in the payload can be parsed into the Opsgenie alerts using dynamic fields.

 

So first thing to check would be the logs in Opsgenie (Settings -> Logs), and look for the "Received integration request" log for an alert sent from Azure to Opsgenie, then you can confirm that we are receiving these "properties" fields.

 

You can then parse them out using something like {{_payload.Properties.key1}}, depending on the structure of the Properties field within that payload.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PERMISSIONS LEVEL
Site Admin
TAGS

Atlassian Community Events