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
Hi everyone, We’re always looking at how to improve Confluence and customer feedback plays an important role in making sure we're investing in the areas that will bring the most value to the most c...
Connect with like-minded Atlassian users at free events near you!
Find an eventConnect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.
Host an eventYou're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.