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.
-JM -- Look out for #1. Don't step in #2 either. This message is PGP/MIME signed.
pgpX2fbfyHkGj.pgp
Description: PGP signature
