Sep 28, 2012 11:06 PM
esxtop with Zenoss 4.2
-
Like (0)
Hi,
I'm currently testing Zenoss 4.2 in order to deploy it as soon as I straighten all annoyances.
One show stopper I encounter is I can't make esxtop work properly in Zenoss. Resxtop works well from command line. check_esxtop as well. But in Zenoss, all I get is a component named "Virtual Machines" with the number of Vm's on the host. But clicking this componed won't list any vm's on the right pane. The events list for this device says "No data returned from this command".
zCommandUserName and Password are set for the esxtop class. Modeling seems to act correctly.
Is anybody having problems with esxtop under Zenoss 4.2?
In 3.2, I used to use VMWare Esxi monitor because I couldn't make esxtop work at that time. So I'm new to esxtop. I thought it is a good idea to use it as it is supplied with the core zenpack bundle.
I run zenoss in CentOS 6.1 with most current packages.
Thanks
Anybody monitoring ESX with Zenoss 4.2 out there?
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.
I need to do ESX monitoring with 4.2 soon so I'll test it and let you know.
Okay thank you.
I had to use CLI v4.1. I couldn't make ESXTOP work otherwise because of a certificate issue that have been brought up with version 5.0 and higher. We use vSphere 4.1 anyway.
sorry to necropost, but did anyone else manage to get esxtop to work with zenoss 4.2? I'm also running centos 6.x like the original poster, and am having a heck of a time getting either the esxi zenpack, or esxtop to work.
Well, I put this on the shelf for now. Zenoss 3.2 works good and will stick with it for now.
As stated above, I've never really been able to make esxtop work right even with Zenoss 3.2. I turned around to use Esxi Monitor Zenpack a long while ago.
Unfortunately, this is things that happen with community software. Not a bad comment though, you guys doing great job. It's a sad thruth.
vCLI 5.1 has a mandatory SSL certificate string that wasn't supposed to be there. If you are using the default self signed, then there are options for workarounds. I just installed vCLI 5.0.0 and made it work.. But here's more options..
http://blogs.vmware.com/vsphere/2012/11/resxtop-fails-to-connect-to-a-vsphere-5-1-host.html
Well, althoug I decided to stop struggling with vCLI 5 because of this SSL cert issue, this was not my problem. We run vSphere 4.1 anyway.
esxtop works if I use it from the command line. However, Zenoss vmware zenpack either report random data or nothing at all within Zenoss.
Have you been able to make this part work?
Here's the solution to the SSL certificate check:
http://communities.vmware.com/thread/426152
basically add something like this to Zenoss's .bashrc
export HTTPS_CA_FILE=/etc/pki/tls/certs/ca-bundle.crt
export HTTPS_CA_DIR=/etc/pki/tls/certs
However, it still doesn't work for me because I get the buffer too small error. I'm using Zenoss 4.2.3 and vSphere 5.1.
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.
Actually, I've finally made esxtop work. I've found that it was working after all, but outputing too much unecessary info. Found this thread to clear the output: thread/14853
Then the funny thing about that is now esxtop only reports running vm's on the infrastructure which is a non sense from a management stand point.
I far prefered the VMWare ESXi Monitor from Eric Enns which reported all configured VM's with RAM, OS Type and actual state (up or down). Each vms also show guest perf graphs as well. On the general Graphs we can see host perf. Far better than the core EsxTop zenpack.
The problem now is I can't install the Vmware data source dependancy on 4.2. Need to resolve this and say goodbye to esxtop. In addition, esxtop has often been reported as a cpu hog in the past.
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.
PLEASE HELP!!!!
I need a working VMware ESXi Plugin for Zenoss 4.2.4.
Can anyone fix the ESXTop Plugin please or write a new plugin for Zenoss to monitor ESX?
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.
Follow Us On Twitter »
|
Latest from the Zenoss Blog » | Community | Products | Services Resources | Customers Partners | About Us | ||
Copyright © 2005-2011 Zenoss, Inc.
|
||||||||