Submitting active check results?

[Kyle Tucker]

> On Fri, Apr 14, 2006 at 10:11:27AM -0500, Marc Powell wrote:
> > An active check is one in which the host or service check_command is run
> > by nagios itself. You can force an active check to happen by
> > re-scheduling the next check of the service.

> > A passive check is one in which the host or service state is determined
> > by another program (submitting a passive result via the GUI, NSCA, a
> > cron job or other external process). In this case, nagios isn't actively
> > determining the state of the service itself but is simply taking the
> > results of a PROCESS_SERVICE_CHECK_RESULT directive in the external
> > command file at face value. Passive checks are most often utilized for a
> > distributed monitoring configuration but can have other uses like SNMP
> > trap handling, etc.

> I'd like to add that there is no penalty for submitting a
> passive check result for a service that performs active checks
> -- it'll be treated as if nagios performed the check itself.

Thanks all for the clarifications. This begs one more question. There
seems to be no option to log active checks. Why not? I'd think it would
be useful at times to just see what Nagios is checking as it happens.

-- 
- Kyle 
---------------------------------------------
kylet at panix.com   http://www.panix.com/~kylet    
---------------------------------------------


-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Nagios-users mailing list
Nagios-users at 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