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,463,395
Community Members
 
Community Events
176
Community Groups

Azure alerts not mapping correctly

I"m using the Common Alert Scheme (https://docs.microsoft.com/en-us/azure/azure-monitor/alerts/alerts-common-schema?WT.mc_id=Portal-Microsoft_Azure_Monitoring) from Azure Alerts and have my integration setup as follows:

 

Screen Shot 2021-08-26 at 8.41.44 AM.png 

However, I when an alert comes in, its not filling out values properly

Screen Shot 2021-08-26 at 8.44.25 AM.png

1 answer

1 accepted

2 votes
Answer accepted

Hi there Rob, 

 

Thanks for reaching out! This appears to be an issue with the payload that is being sent from Azure to Opsgenie. When the 'Common alert schema' option has been toggled on in Azure, this changes the format and structure of the payloads that Azure sends to Opsgenie. You can find out more details on this here: https://docs.microsoft.com/en-us/azure/azure-monitor/alerts/alerts-common-schema

 

Are you able to try switching back to the standard alert schema for this alert type in Azure? To switch to the standard alert schema, this is a setting that needs to be made on the Azure side. You should see an option in the action/webhook definition in Azure that is sending to Opsgenie, and you can toggle the 'Enable the common alert schema' option off. For more details, see this section here: https://docs.microsoft.com/en-us/azure/azure-monitor/alerts/alerts-common-schema#through-the-azure-portal

 

Apologies for any inconvenience that switching back to the standard alert schema in Azure may cause at this time. Since the common alert schema is currently being used and the values in the payload being sent from Azure are not being mapped over to the alert in Opsgenie, this indicates that there is a mismatch in the format. The expected incoming data format is laid out in our documentation as defined in here: https://support.atlassian.com/opsgenie/docs/integrate-opsgenie-with-microsoft-azure/

 

Best regards,

Skyler

I will turn off the common alert schema flag and see if this fixes the issue.  Thanks!

Like Skyler Ataide likes this

Quick follow up, changing from using Common Alert Schema flag fixed the issue and the data mapping per the documentation is now working.

Like Skyler Ataide likes this

Great to hear! Thanks for following up with this update. smile

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
TAGS

Atlassian Community Events