Every morning I like to fire up vCOps and have a look at my environment and when I do this, I like to see nothing but green (maybe a bit of yellow :))  For the past week or so that hasn't been the case…  Not that I have any performance issues, but I do have what is called a 'fault' on a few of my Virtual Machines.  I've been troubleshooting an issue as of late with something causing a few of my hosts to become disconnected, and HA has been attempting (and failing) to restart a few of my VMs, which in turns generates an alarm on the VM and a fault inside of vCOps.  Well, the issue has since been resolved and everything is running fine again, however vCOps is still hanging on to those faults for some of the VMs.

Now I don't see this as a bad thing, it certainly is nice to have a record of these issues inside of vCOps, but being the persnickety fellow that I am when I log into my vCOps and see those VMs showing up on the heat map coloured in red, well, it drives me a little mental…  I thought maybe if I leave it for a week things would clear up, and while some did, others didn't.  So I guess a little manual intervention is involved.

Basically, a fault in vCOps is triggered by an event occurring from within vCenter Server.  VC Ops will hang on to this fault until vCenter Server reports that the issue has been resolved, thus resulting in a red VM like the one above, and a lower health score to boot!  In some cases (cases like mine) you may need to manually cancel and remove a fault from vCOps.  So in the case you ever need to, the following is how to do so…

Either select your VM, or any inventory item that is higher up on the inventory view and navigate to the Alerts tab.

 

In the Alerts table below, sort, filter, re-arrange however you want and select the fault(s) that you want to cancel and click the 'Cancel' Icon.

Presto!  That's it!  If you navigate back to your dashboard and heat map now you should hopefully see that wonderful greenish tint of all that excellence (after everything refreshes)!  Or in my case there is still more work to do 🙂  Happy Troubleshooting!