Hey all - I have several checks that I would like to limit to a specific IP. Many of my boxes support multiple functions (smtp, http, imap, etc), and often have dedicated virtual IPs. Zenoss seems to run the checks against the primary manageIp, even when the service isn't listening on that address. Is there an easy way to restrict a service check to overcome this? Nagios made this easy with their plugin model, but I haven't figured out how to replicate in zenoss. I peeked into the Python code, but I'm not familiar enough with TALES to do this on my own. And hopefully there's a more elegant solution, anyway.
For a little more clarification, here's an example of what I'm trying to do: Device = 10.1.4.2 Also listening on 10.1.4.3, 10.1.4.4 SMTP bound to 10.1.4.3 HTTP bound to 10.1.4.4 the SMTP check is failing because 10.1.4.2:25 isn't responding. same for HTTP. What I would like to do is to be able to go into the device's SMTP check, and tell it to check against 10.1.4.3. The same for HTTP, and for a bonus, give it a URL/hostname to check instead of the simple TCP connect. Am I expecting too much? :) -- Greg Haygood [EMAIL PROTECTED]
_______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
