Passive service checks via NSCA and requir ed check command defini tion
Ralph.Grothe at itdz-berlin.de
Ralph.Grothe at itdz-berlin.de
Mon Aug 8 15:51:44 CEST 2005
I missed this thought before sending my last reply.
Would you suggest I enabled active checks for the service
and provided the dummy_check returning state UNKNOWN
in order to get these states whenever the passive checks didn't
take place,
for whatever reason?
Well the only reason I can think off is that the remote host
crashed
(or the route thereto).
But I covered this already by host icmp checks.
Another thing strikes me if I enabled active checks.
How should I space them, meaning how to size the intervals?
You see, I could think of a, to me typical seeming, application
of passive checks,
viz. a service that probably is only checked once a day like the
success of the daily backup.
How would I provide an active dummy check for such a situation?
Maybe my thinking is a bit far-fetched?
> -----Original Message-----
> From: nagios-users-admin at lists.sourceforge.net
> [mailto:nagios-users-admin at lists.sourceforge.net]On Behalf Of
> Ralph.Grothe at itdz-berlin.de
> Sent: Monday, August 08, 2005 3:38 PM
> To: pla at softflare.com; nagios-users at lists.sourceforge.net
> Subject: RE: [Nagios-users] Re: Passive service checks via NSCA
and
> requir ed check command defini tion
>
>
> > >> Turn off the cron job. Nagios will be blissfully unaware
> and
> > >> return OK for the service even if the service is down.
> > >
> > > Disabling the cronjob on the remote host?
> > > I can't imagine how the feed should work then.
> >
> > It doesn't work if you turn off the cron job. The point is
> > to simulate
> > what happens if the cron job fails, or that remote host locks
> > up, or...
> >
> > In that situation you won't be getting any passive checks.
> > So the active
> > check kicks in and says everything is OK. That isn't what
you
> want.
>
> Wait as far as I understood, the active check couldn't kick in
> because I disabled it in the service's definition
> (you may have missed in my thread starting posting)
> Or is this a too optimistic expectation from nagios?
>
>
> define service {
> use generic-service
> service_description samos-hpva-state
> host_name samos
> passive_checks_enabled 1
> active_checks_enabled 0
> check_command passive-check-pad
> contact_groups samosadmin
> }
>
>
>
>
> >
> > > So far I could read the status line as what got written to
> the
> > > FIFO above. What difference do you mean?
> >
> > I mean that check_dummy returns "Status is OK" and your
> > plugin probably
> > returns something different. So you can tell whether the
> > passive check
> > is working or if the active check kicked in but only if you
> > read carefully.
> > Which you're unlikely to do if the service is green.
>
>
> I understood.
>
>
>
> -------------------------------------------------------
> SF.Net email is Sponsored by the Better Software Conference &
EXPO
> September 19-22, 2005 * San Francisco, CA * Development
> Lifecycle Practices
> Agile & Plan-Driven Development * Managing Projects & Teams *
> Testing & QA
> Security * Process Improvement & Measurement *
http://www.sqe.com/bsce5sf
_______________________________________________
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
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
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
More information about the Users
mailing list