There was a reason - that I don't want to have a separate template for each service that I want to check the certificate of, nor do I want to have to bind appropriate templates to each device which may be running something over SSL separately. The amount of management involved in doing this for a bunch of disparate systems would have defeated the object of being able to group hosts in a tree-based structure, and would have been necessary as the original script returned CRITICAL if it couldn't connect to the host/port given.
Instead, I've fixed it by hacking the script so if it can't connect, it returns OK and I've put calls to check every service I can think of in a template which is applied to everything. ZenOSS's other checks are quite enough to determine whether or not a given service is running - all I'm concerned about is "has the SSL certificate expired or not?" - so this should be fine. ------------------------ James Cort -------------------- m2f -------------------- Read this topic online here: http://community.zenoss.com/forums/viewtopic.php?p=9596#9596 -------------------- m2f -------------------- _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
