If you reboot the host and clear the alarms it should only fire on the VMs in the scope.  There is a bug that basically sticks the rule in memory and doesn't update properly.  Last I looked there is a fix on that slated for 6.6.2 (Core 5.6.4)
Hi,  I'd like to create what i would think should be a relatively simple rule, here are the specifics, if anyone can offer some help that would be great.   Here is what i would expect to happen...... The first point should restrict the scope of the rule to only virtual machines that meet this criteria. If i tick the green 'validate rule scope' box in this section it shows me a list of those virtual machines with this name. Great.  The second point should then take these scoped virtual machines and look at the CPU utilization and compare this to the threshold set in the registry variable.  With reference to the 3rd screenshot (rule alerts) - the first issue is that I am getting alerts for pretty much all of the virtual machines, so it's ignoring the scope.  The second issue is that it's not taking any notice of the severity levels, so it's just alerting for regardless of whether it meets the threshold. Any strangely i've actually disabled the 'warning' alarm so it should event be alerting for this type.  Any advice would be very welcome. Or if there is a better way of doing what im aiming to do that would be fantastic.  Thanks  
vFoglight Rule Alerts not behaving correctly