The general way I tend to look at alerts is turn everything off first.  Then turn on only the bits that make sense.  Generally, I want to know about VM's issues, CPU/Memory/Running out of disk space (I like growth rate vs. fixed thresholds);ESX hosts dropping off/maintenance mode/dead;Datastores running out of space;Clusters running out of space and that's about it.  In the end this works out to be about a dozen or so rules.  Even then I will tailer them slightly per environment, but it's hard to find a perfect mix that works OOTB for everyone.  Usually, I will spend about an hour or so from install and then tweak after a month or so to fine tune them.  In the end, a lot of the rules will not apply to everyone, but better to have them there to turn off/on vs. you having to start from scratch IMO.  Thomas
SO does anyone have a best practice monitoring collection that they use for their VMware environment? There are over 50 rules to select with the VMARE Cartridge/agent. Just wondering if anyone has paired it down to a monitoring profile that doesn't create so many alerts, theybecome white noise. Their is a BMC footprint here and being asked to evaluate  the BMC COEE Capacity Optimization tool. There appears to be some metric gathering overlap between tools and monitoring as well. Wondering if anyone has used that tool either in conjunction with vfoglight or by itself.
Best Practice monitoring of VMware between vFoglight versus BMC COEE