search

Icinga / icingaweb2-module-vspheredb

The easiest way to monitor a VMware vSphere environment.
https://icinga.com/docs/vsphere/latest
GNU General Public License v2.0
100 stars 34 forks source link

Power State monitoring rules not working as excepted #447

Closed Meister1900 closed 1 year ago

Meister1900 commented 2 years ago

Although we configured "Raise CRITICAL for uptime less than10 (seconds)" all the VMs are critical with e.g.: System booted 19h 9m ago

The same issues occures with the default values and inherited values. The only thing that helps is to disable Power State Policy completly.

This behaviour started after the upgrade to vspheredb 1.5.0

Unbenannt

Thomas-Gelf commented 2 years ago

Guess they are not critical because of Raise CRITICAL for uptime less than, but because of Raise CRITICAL for uptime greater than. That one has no internal default, but might be treated as 0 as far as I understand the issue by a quick look at the code. Does the problem go away, when you configure a high value for the greater threshold?

Please note that you have to wait up to two minutes for the daemon to refresh the overall monitoring rule problem overview. When clicking a single Object, the calculation there is live.

slalomsk8er commented 2 years ago

I had the same problem and mentioned it in https://github.com/Icinga/icingaweb2-module-vspheredb/issues/361 - again sorry for mixing Issues.

rules for the host show that a uptime of less then 5min generates a warning but everything else is undefined but isn't ignored:

Meister1900 commented 2 years ago

Yes, the issue goes away when I configure a high value for the greater threshold. Thanks!

slalomsk8er commented 1 year ago

I allso noticed, that a reboot of the guest does NOT change the uptime in the hypervisor's view?!