We were able to setup a threshold for the percentage of CPU usage and set some actions (via a command line programming) to be taken should the threshold be exceeded for VMs running under VMware VirtualCenter and successfully triggered the alarm.

The reactive measures that can be taken should a threshold be broken include running other applications, popping up an alert, triggering a sound and sending a notation to a log.

As for Hyper-V VMs, we were able to view some performance data from Hyper-V, but not all metrics (such as CPU or RAM usage). Some of the ones we could view included network connections per second and the Hyper-V VM health summary.

Security gets more direct attention in NSM/ASM than the other products we tested, including the aforementioned definable user roles. There is also a security management component within NSM, even though it is not specifically targeted toward its virtualization management components. With NSM security management, we were able to lock down parts of NSM. There were different assets permission, asset groups and user groups available to create a secure environment. With these assets, we could control access to the NSM/ASM consoles and commands available to them.