Hello, Templates are definitely the way to go, and it is exactly because they make it really easy for you to do something like this across lots of devices. They are more of a core feature than a buried element. The short version: One really easy way to do this would be to make a device class, call it Web, move all the server devices that host the sites you want to monitor into this. Then make a template that performs the site monitoring you want to do across all the site and bind it to this class. Now, all your sites will be monitored, with just these 2 steps! You don't have to set any custom strings, since you can specify a variable in the template which can work for ALL the cases you would have. With a template, you don't need to do any copy and pasting, and likely no customization in each case.
I go into a lot more detail and reasoning on this process (and cover some more complicated cases you might very well run into) in a HowTo I just wrote regarding website monitoring using the HttpMonitor ZenPack (which uses check_http). It is located here: http://www.zenoss.com/community/docs/howtos/monitoring-websites-with-httpmonitor That describes the case I gave above with a lot more detail. By the way, my suggestion about making a new device class applies if you are monitoring more servers in Zenoss than just your webservers. If you only had webservers being monitored, you could just bind the template you make onto the /Devices device class and it would apply to all of them, it is the same idea. Good luck! -Sam -------------------- m2f -------------------- Read this topic online here: http://community.zenoss.com/forums/viewtopic.php?p=12987#12987 -------------------- m2f -------------------- _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
