Ok, I'm fairly new around these parts too so maybe I shouldn't be answering this but I'll give it a shot.
Just as a quick side note, the Zenoss class and template structure was quite confusing at first to me. After spending a couple of weeks playing with it, pouring over the guides, list archives and asking questions here I think I'm starting to get the hang of the idea behind how it operates. So it's starting to make sense and is quite powerful. Anyway on to answering your questions. According to the admin guide Zenoss plugins map information into the Zenoss standard model. I think basically what this means is that a collector plugins are used primarily to tell Zenoss where to grab the bits of information to fill out sections of the status, os, hardware, and software tabs on a device. To monitoring the items you indicate I don't believe that a collector plugin is needed. CPU, Temp, Memory will all have a given OID that's going to be the same for all your foundry gear. If you look at the templates in the /devices/network/router/cisco you'll see a good example of what you want to do. You'll notice the device template is specific to that class, it's been copied to that location and altered to collect memory and cpu information as well. Most likely to do what you want all you need to do is create a foundry class in the devices tree. Then copy the default devices template to your foundry class and add in the new data sources for the OIDs you want to monitor. Optionally you can add thresholds and graphs as well. If I am in error in this matter hopefully one of the veterans will step in and correct me -------------------- m2f -------------------- Read this topic online here: http://community.zenoss.com/forums/viewtopic.php?p=15658#15658 -------------------- m2f -------------------- _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
