VMware VCSA, alerts coming from different esxi are listed under same alert on OpsGenie

n11 IT Sysadmin Team July 2, 2021

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?

 

 

 

1 answer

1 accepted

1 vote
Answer accepted
Connor Eyles
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
July 4, 2021

Hi @n11 IT Sysadmin Team 

From what I can understand on what is happening here -

  • If esxi-1 generates a memory alert the alarmID=alarm-3
  • If esxi-2 generates a memory alert the alarmID=alarm-3

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:

  • esxi-1-alarm-3
  • esxi-2-alarm-3

Thanks,

Connor

Suggest an answer

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

Atlassian Community Events