Yes, I do realize we could take out the service ping check, but no, our
commands are different for host/service check as we want to get latency and
packet loss statistics on our service check:
Host check:
command_line $USER1$/check_fping -H $HOSTADDRESS$ -c 5000.0,100% -n 5 -i
50
Service check:
command_line $USER1$/check_fping -H $HOSTADDRESS$ -w $ARG1$ -c $ARG2$ -n
5 -i 50
I changed my host check so that it won't report warnings. We were getting
too many false DOWNs on the host check, since documentation states that
anything returned from the plugin other than OK will show that the host is
DOWN.
True, I could look at the event handler but I don't think I'm ready to go
there yet. For sure we will be looking at what Icinga 2 can offer!
On Thu, May 2, 2013 at 1:06 PM, Michael Friedrich <
michael.friedr...@gmail.com> wrote:
> On 02.05.2013 18:51, Zachary McGibbon wrote:
> > I'm trying to figure out a way to submit a passive check result for a
> > PING service check when a host comes back up. Our Icinga installation
> > is quite large and by the time the host comes back up, it takes a while
> > for the service check to kick in. Since the PING failed before, it
> > still shows critical.
>
> Question aside - I assume that the host check command is the exact same
> as the service 'PING' check - why not just drop the ping check and focus
> on the host itsself?
>
> Such a duplication does not make much sense but seems to be common
> practice. (which is why icinga2 won't have a check_command, but takes a
> virtual service state whereas a service can be a business process later
> then too).
>
>
>
> >
> > Besides setting up a contact for the up state and having it run the
> > passive submit, does anyone have another idea how I could trigger the
> > passive result on host up?
>
> eventhandlers are run on every state change, so you might trigger that
> one, putting a command to pass a checkresult to the service then too.
> but that's just an ugly idea, not tested.
>
> kind regards,
> michael
>
> >
> > Thanks
> >
> >
> >
> ------------------------------------------------------------------------------
> > Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET
> > Get 100% visibility into your production application - at no cost.
> > Code-level diagnostics for performance bottlenecks with<2% overhead
> > Download for free and get started troubleshooting in minutes.
> > http://p.sf.net/sfu/appdyn_d2d_ap1
> >
> >
> >
> > _______________________________________________
> > icinga-users mailing list
> > icinga-users@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/icinga-users
>
>
> --
> DI (FH) Michael Friedrich
>
> mail: michael.friedr...@gmail.com
> twitter: https://twitter.com/dnsmichi
> jabber: dnsmi...@jabber.ccc.de
> irc: irc.freenode.net/icinga dnsmichi
>
> icinga open source monitoring
> position: lead core developer
> url: https://www.icinga.org
>
>
> ------------------------------------------------------------------------------
> Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET
> Get 100% visibility into your production application - at no cost.
> Code-level diagnostics for performance bottlenecks with <2% overhead
> Download for free and get started troubleshooting in minutes.
> http://p.sf.net/sfu/appdyn_d2d_ap1
> _______________________________________________
> icinga-users mailing list
> icinga-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/icinga-users
>
------------------------------------------------------------------------------
Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET
Get 100% visibility into your production application - at no cost.
Code-level diagnostics for performance bottlenecks with <2% overhead
Download for free and get started troubleshooting in minutes.
http://p.sf.net/sfu/appdyn_d2d_ap1
_______________________________________________
icinga-users mailing list
icinga-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/icinga-users
