Hi Simon,

A couple of things here.  Lets's start with the HttpMonitor which is provided by the standard ZenPacks.zenoss.HttpMonitor.  Really all this provides is the device class, /HTTP, an event, and a performance template, HttpMonitor which MAY be applied to any device class under /Devices.  The device class /HTTP supplied with the ZenPack has already had this HttpMonitor template bound to it so that any device you add to the /HTTP device class, also gets this template.  If you navigate to one of the 11 devices that you have, you should see this template listed at the bottom of the left-hand menu?

If you look at the template, by default it just tries to connect to the ip address of the device - nothing fancy - so it doesn't need any other parameters, so there are no extra Config Properties (zProperties) to do with http.  If you want to, you can modify the standard template or, more likely, create a new subclass of devices under /HTTP and create a new copy of the HttpMonitor template that applies to that class, that has extra parameters like users, passwords, SSL,....

On other ZenPacks, I have a slightly different menu path than you for installing ZenPacks (not the VM and mine is 4.2.3).  Either way, I think your menu is for installing ZenPacks that you already have pulled down to your Zenoss server.  Your list of ZenPacks installed just looks like the standard Zenoss ones that would be pre-installed.

The method I would use to install ZenPacks would be to start with the ZenPacks page on the new wiki site - http://wiki.zenoss.org/Category:ZenPacks .  You probably know that we are currently in rather a transition period between the new wiki and the old JIRA site for ZenPacks.  Start with the url above and you often find that following the documentation link takes you back to the old site.  The new site is trying very hard to ensure that ZenPacks work for Zenoss 4.x - hence my recommendation to start there.

Download the correct version of the ZenPack for Zenoss 4 - hopefully there is a link that shows that.  Sometimes there isn't (like with your printer MIB) - no-one has yet updated it for Zenoss 4.  Many ZenPacks include in their name an indication of the pthon version eg. ZenPacks.TwoNMS.PrinterMIB-1.0-py2.6.egg.zip  - the py2.6 indicates Python 2.6 and is no good for Zenoss 4 - you need something with a py2.7.  This naming convention is just that - the ZP does not have to include the version and some don't (like many of Egor's brillinat ZenPacks).

Can I suggest you start with something on the wiki that does have a 2.7 egg file?  Download it to your Zenoss server and then install it there.  I personally always use command line to install ZenPacks so that, if there are issues, then you see them.  As the zenoss user, I would get, say, ZenPacks.skills1st.bridge-1.0-py2.7.egg into /opt/zenoss/local (my choice of directory - I always create a local dir).Then:

cd /opt/zenoss/local

zenpack --install  ZenPacks.skills1st.bridge-1.0-py2.7.egg

zenhub restart

zopectl restart

Some ZenPacks need you to restart zenoss completely with "zenoss restart" - check the documentation on the ZenPack page.

I have just tried to install your Printer MIB on my Zenoss 4.2.3 and it has made a bit of a mess .  Don't go there at present - hopefully I can fix it and release a Zenoss 4.x version.

Cheers,

Jane

Hi Simon,

You have the HttpMonitor template - there at the left (sorry - not on the popup menus from the bottom but under Monitoring Templates).  If you go to Graphs (3rd down in that menu) then you should see values for time and size, provided your Zenoss server can actually get access to the target device.

I am intrigued that you have managed to install the PrinterNMS zenpack - I wouldn't expect it to install anything with py2.6 in its name and it did horrible things to my Zenoss when I tried to recompile it for Python 2.7.  Can you still get to see the INFRASTRUCTURE menu??

If, as zenoss user, you do zenpacks --list

do you see ZenPacks.TwoNMS.PrinterMIB in the list?

Re starting afresh - it depends why you are doing this.  At present, there isn't support for Debian for Zenoss 4.x - expected soon, but "soon" seems to be a long time coming .  If you areally doing a proof-of-concept, then I would hang in there a bit longer with your VM and winkle out some of your issues first.

Cheers,

Jane

Sorry - you need to unzip the file first to get something ending in .egg.  Then run the zenpack install against that.

Cheers,

Jane