niels2000 wrote: > Well, color me confused. > > Not only do I have a hard time understanding the logic behind the template > application, I am also now at a complete loss as to how I can accomplish the > task of raising warning at a certain level and errors at another, for > specific devices. > > I guess I shall have to resort to a Nagios-plugin. I was hoping it wouldn't > come to that.
There are some templates that are special/different than others. The Filesystem and ethernetCsmacd templates are two such templates. They are only used when a device is "modeled"....you don't bind them to a device. Basically, when a device is added to zenoss it is modeled using some python scripts. The modelling process is told what to query by the "collector plugins" assigned to that class. For example, if you go to /Device/Server/Linux and click on the drop down arrow at the top right, you'll see a link for "More" and then "Collector Plugins". These plugins are scripts that tells zenoss how to look for various attributes of the device you are querying. You should see one that says "zenoss.snmp.HRFileSystemMap". This collector will query various snmp attributes of the device to create its filesystems. This is created under the device in the "OS" tab in the box labeled "File Systems". For example, if you have a "/" filesystem...the script creates this for you under the OS tab....it also assigns the "Filesystem" template to this filesystem. You can view it by cliecking on "/" and then on templates. So the Fileystem template is automatically bound to your device's filesystem...and not the device (server) itself. All that filesystem template does is update usedBlocks via snmp. The modeling script is what actually determines the total size of the filesystem. I hope this makes sense. Other templates such as the "Device" can be bound to a specific class or device. If you want to create various alerts for Filesystems....edit the existing template and add more thresholds. If you only want it to apply to specific filesystems on a device...then let the modeling script do it's job and create the filesystem. Once that is done, click on the filesystem and then the templates tab. click on "create local copy" for the filesystem template and modify as needed. -------------------- m2f -------------------- Read this topic online here: http://community.zenoss.com/forums/viewtopic.php?p=25134#25134 -------------------- m2f -------------------- _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
