Icinga / icingaweb2-module-vspheredb

The easiest way to monitor a VMware vSphere environment.

Home Page:https://icinga.com/docs/vsphere/latest

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Not all problems are reported using icingacli vspheredb check

wp-perc opened this issue · comments

Actually, not all objects that fail a Monitoring Rule are reported using icingacli vspheredb check.
If you use icingacli vspheredb check to get ALL OBJECTS of a specific type (Host Systems, Virtual Machines or Datastores) that are failing, not all of them are reported. If I check A SPECIFIC OBJECT, its state is reported fine according to Monitoring Rules definition.

See this screenshot as example:
I am trying to get the list of all failing host, and this list is empty (Everything is fine).
If I check for a specific Host System, I can see it is in a WARNING state.
image

I think this might not be the intended (or the expected) behavior.

Looking at the code, this happens because functions hostsAction, vmsActions and datastoresAction on file CheckCommand.php invoke lookup()->listNonGreenObjects($type). This function returns all and only the Objects with overall status not green of a specific type. Functions that check the state of a single object (hostAction, vmActions and datastoreAction) have a different behavior.

VSphereDB version: 1.6