this could be because our Monitor responds to CHANGES in the status of VMs; only when VMs Tools status changes for VMs (or when new VMs are added; or when nworks is first installed) do we send an event that triggers this monitor.
To prove this, you can rebuild the State Table - this contains various configuration items on hosts and VMs, and we create when we first connect to vCenter.
If you -
- stop the nworks Virtual Infrastructure Collector service
- delete the file StateTbl.xml in the Collector install folder, in /Data subfolder
- start the nworks Virtual Infrastructure Collector service
After the above is complete, the Collector will rebuild this file, and will resend all events on VMware Tools status for all VMs. That should trigger the Monitor.
(note, new VMs, and changes in existing VMs, will always be automatically captured - the above is just to re-send events for existing VMs)