You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Hello community,
We successfully integrated OpsGenie and VMware VCSA.
We have several alert definitions on vCenter like CPU usage, memory usage etc.
Memory alerts coming from different esxi's are listed under same alerts on OpsGenie.
It's because alarmID is used as alias for categorizing alarms by default.
Eg:
If esxi-1 generates a memory alert, we are getting notification for it.
If esxi-2 generates a memory alert at the same time with esxi-1, we are not able to get an alert for it. This alert is listed under esxi-1 alert. Both alert has alarmID=alarm-3 for memory usage.
What parameter should be used as alias to seperate this alerts or what is the best practice here?
From what I can understand on what is happening here -
Because they share the same alarmID then the alerts will get deduplicated, this is why you only see 1 alert.
Here is a recommendation on what you can do is to include the ESXi name in the alias alongside the alarmID. This will mean when the same alarm happens to the separate ESXi machines, different alerts will get created.
So the 2 different Alias will look something like this:
Thanks,
Connor
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.