Open codingwatermelon opened 5 years ago
@codingwatermelon: you want to see currently "triggered" alarms, correct?
Yes, that would be nice! Currently triggered alarms. I think otherwise, alarms are prone to getting lost in "Alarm History", plus the additional alarm filtering would be nice.
Would it be possible to integrate Icinga notifications with vCenter alarm triggers by the way?
The shipped check commands for Icinga should already notify objects with a triggered alarm. They just do not show what the alarm says.
Sorry if this is a dumb question but where are these check commands?
I have the same question: where are these check commands? Is there any chance to configure email notifications based on vCenter events/alerts?
So can we configure Icinga email notifications based on vcenter events/alarms? If so, how?
icingacli vspheredb check host --name esxvdilp70.example.com
This kind of check needs to be run on the Icinga host that has vspheredb installed.
Use the checks in https://icinga.com/docs/icinga-2/latest/doc/10-icinga-template-library/#icingacli as a template.
As a bonus one can automate the icinga config for the hosts and services by using this module as director import source.
Feature Request
I think that there should be another menu that shows all of the currently configured alarms on the ESXi hosts/vCenters. You should then be able to filter by different types of alarms in the "Alarm History" menu (similarly to how you can currently filter events in "Event History").
Additionally, it would be nice to be able to configure Icinga notifications based on vCenter events/alerts (not sure how that would be implemented though).