On Fri, Feb 19, 2010 at 1:11 PM, Kevin Keane <subscript...@kkeane.com> wrote: > Personally, I'm not sure if there is a single "best way". That is why I keep > promoting separating the protocol from the transport. Basically, Nagios > protocol data fits into Layer 6 or 7 of the OSI model, while the encryption > and authentication really should be handled by layer 4 or 5.
We have written in addtion to our other agents an HTTP-based agent that uses either RESTful or non RESTful style URLs for requests. Creating an HTTP RESTful style interface spec would be a pretty clean way to define a standard without getting into implementation discussions and would provide a common ground for plugins. As with SNMP or SSH HTTP comes with a performance price but more and more with Nagios I am seeing (because it is so flexible) that defining standards for a user group / org that uses Nagios is much harder than performance tuning is. ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Nagios-users mailing list Nagios-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nagios-users ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. ::: Messages without supporting info will risk being sent to /dev/null