Getting Alarm Info

[pryorda]

From @l11h on March 1, 2018 13:24

It would be great to get Alarm info for VM's / Hosts
For VM there is an overallStatus option which works but it would be great to write to a label which alarm was executed.
This way we can easily check if we need to deal with it or not / how many alarms there are for the VM

Copied from original issue: rverchere/vmware_exporter#35

[rmontenegroo]

What kind of alarms are you referring to?
It is possible to get alarms like "Virtual machine CPU usage" and so.
And what is the main idea? Get those alarms and stick'em all together in a label like "alarms" ? Or each alarm is a individual label?
For example: Virtual machine CPU usage has an internal short description of alarm.VmCPUUsageAlarm, that would be informative, and maybe useful if appended to an label "alarms".
How does that sound to you?

[pryorda]

As long as this doesn't slow the process down or add 1000s of metrics I'm okay with it.

[rmontenegroo]

I have not tested anything yet but I was thinking of creating two metrics of alarms count: one for red overall status and the second for yellow. There would be an extra label indicating the list of alarms set;
So it would be 2 more metrics with an extra field. And we could leave those metrics optional.
What do you think?
Brainstorming here. :-)

[pryorda]

I think it should be fine.

[alecorps]

Hi, i feeling prometheus exporter is not the good tool to check alarms. On your example, i think it’s a better way to collect cpu usage, and configure an alert in prometheus or grafana to notify alert manager.

[rmontenegroo]

I understand and i agree it is not an elegant solution. But I would have VMware alarms thresholds replicated in my alert monitor, something already setup on vcenter. Not to mention all the rework to replicate the rules. Furthermore I can keep statistics on alarm occurrence of some vendor equipment. Em sáb, 2 de mai de 2020 04:44, alecorps <[email protected]> escreveu:

…

Hi, i feeling prometheus exporter is not the good tool to check alarms. On your example, i think it’s a better way to collect cpu usage, and configure an alert in prometheus or grafana to notify alert manager. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#1 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AO5BSPJLLLDUTL24PZENHDLRPPFMDANCNFSM4FHRBQBA> .

[rmontenegroo]

Please, take a look at

https://github.com/rmontenegroo/vmware_exporter/tree/alarm_info

I am a bit entangled with these git branches :D
For some reason, I can't PR to your mater right now.

[pryorda]

Hi, i feeling prometheus exporter is not the good tool to check alarms. On your example, i think it’s a better way to collect cpu usage, and configure an alert in prometheus or grafana to notify alert manager.

Hey, I dont think its good to collect all alarms rathers. Just the status that vms or hosts are in. Warn, Critical, Etc. I wanted to see where @rmontenegroo went with this

[pryorda]

Please, take a look at

https://github.com/rmontenegroo/vmware_exporter/tree/alarm_info

I am a bit entangled with these git branches :D
For some reason, I can't PR to your mater right now.

Try to reset your changes, stash them, rebase off of the current master, then apply your new changes. Don't force push until everything looks right.

[rmontenegroo]

I think I got it now.

[pryorda]

Closing for inactivity. We have merged some alarm changes in so it should help.