Hi Sameer Dave,
I am sorry you are receiving a lot of alerts; and we will of course assist you to get the best nworks configuration for your environment.
However I have to point out that if there IS a "bug" - it is in Virtual Center, not in the nworks MP.
All that our Collector does, is check the 'VMware Tools Heartbeat Status' for each VM, exactly as the VMware API publishes it. If this status is 'Red', or 'Yellow' - then we generate an alert.
This 'VMTools Heartbeat Status' has been shown in the past to be somewhat unstable/unreliable - *as published in Virtual Center, not in our product!*
Sometimes when we check the vCenter API, we get a status of Red or Yellow, for no apparent reason. Within a few minutes, the status returns to Green - again for no apparent reason. This is why we introduced a Timer in the MP Monitor, so that we would only alert if the Status *remained* Red/Yellow for 2 intervals, rather than alert immediately.
It seems that in some environments, the default (2 intervals = 10 minutes) is not enough - so you can either
* increase the interval by modifying the parameter 'CorrelationInterval' on the Monitor.
* disable the VMTools Heartbeat Monitor (not this does not disable all "VM monitoring" - only this particular state event. All VM performance data, all other VC events, including power changes etc, will still be captured)
So - we are happy to assist you, as I said, to get the best value from the nworks MP. But the 'bottom line' is that we are always dependent on the data that is published by the VMware API, whether that is performance data, events, or VM state-change as in this case.
I hope that clears up the issue, please let me know.
For *anyone* receiving these 'Heartbeat' alerts - please feed back to this thread if you are experiencing this issue, and whether increasing CorrelationInterval helps. This is the feedback we need, we can take it to VMware, and work with them to find a solution for this instability in the Heartbeat value we get from the VI-API.
Senior Product Manager