Tried it but didn't work with VMware CLI SDK 5.1 because of bora panic "buffer too small" errors. Had to delete and recreate all ESXi servers in Zenoss because they were filled with phony VM entries that could not be removed.otherwise.

This is actually an issue with us here as well. Last time I attemted to get something working It just didn't work or work to the level that I wanted it to.

Zenoss has been great with all our monitoring here but with our strong VMware infrastructure, Zenoss in my opinion is falling behind here and this is huge part of monitoring. So much so that we are looking at another tool to just monitor the VMware infrastructure though as always it doesn't do everything like application monitoring so we are going to be end up using two tools to do this.

I really wish Zenoss would build it more into thier core for monitoring this.

I also struggled with esxtop zenpack.  I was experiencing the buffer too small error.  This appears to be a problem with how subprocess is being used in python.

I was able to get the zenpack somewhat working by editing the resxtop function as follows:

[code]

def resxtop(self, command):

        import os

        """

        Run the resxtop command and return the output into a cache file,

        or die and print the error message.

        """

        password = self.options.password

        env = dict(VI_PASSWORD=password)

       # proc = subprocess.call(command, stderr=PIPE, shell=True)

       # proc.check

        os.system(command)

[/code]

Unfortunately, while the VMs are listed under the guest section of the device page, so is a bunch of other junk.

FYI, the SSL bug in vSphere CLI was corrected a couple of days ago, so be sure to download CLI 5.1 update 1 if you're trying to use this or other zenpacks that utilize CLI tools.

I've put together a working version (atleast for me) of the ESXTop Zenpack. It is available in the GitHub:

https://github.com/ju55i/ZenPacks.zenoss.EsxTop/tree/develop

It works at least with the 5.0 version of the resxtop. I've also optimized it a little bit. There was a import from ZenUtils in the check_esxtop command which triggers lots of other imports and causes a massive slowdown. I brought the imported function straight to the module.