Hi Massimo.
this service doesn't seem to work when using the -H option, unless i remove
the $ARG1$.
The service definition is:
define service{
use service-template
host_name localhost
hostgroup_name websites
service_description HTTP
check_command check_http
}
I try and use the same check_command to check for keywords using:
define service{
use service-template
host_name website.com
service_description HTTP-keyword
check_command check_http!-s "This will be a keyword"
}
On Tue, Aug 17, 2010 at 4:39 AM, Massimo Forni <forni.massimo@...:
> Hi, can you post the service definition?
> In particular the check_command option.
>
>
> 2010/8/16 Daunce <daunce@...>:
> > Hmm. I still can't work it out why check_http -I $HOSTADDRESS$ $ARG1$
> > Works with nothing in $ARG1$, yet check_http -H $HOSTADDRESS$ $ARG1$
> > doesn't.
> > Can anyone else confirm it happens for them too, or am I doing something
> > wrong?
> > Cheers.
> >
> >
> >
> > On 12/08/2010, at 2:33 PM, Andrew D <daunce@...> wrote:
> >
> > Thanks for your replies.
> > It appears it's the empty $ARG1$ i'm sending. also dependant on if i am
> > using check_http with -I or -H.
> > Is this as expected?
> > To get around this, I've had to define a command definition for each
> variant
> > of the check_http (for certs, non standard ports, https, keywords etc),
> > which i didn't think i would have to when
> > following http://docs.icinga.org/1.0.2/en/monitoring-publicservices.html
> (but
> > i'm using -H instead).
> > See the Processing line below:
> > Returns OK:
> > =======================================================
> > **** BEGIN MACRO PROCESSING ***********
> > Processing: '$USER1$/check_http -H $HOSTADDRESS$'
> > Done. Final output: '/usr/local/icinga/libexec/check_http -H
> website.com'
> > **** END MACRO PROCESSING *************
> > =======================================================
> >
> > Returns Critical:
> > =======================================================
> > **** BEGIN MACRO PROCESSING ***********
> > Processing: '$USER1$/check_http -H $HOSTADDRESS$ $ARG1$'
> > Done. Final output: '/usr/local/icinga/libexec/check_http -H
> website.com
> > '
> > **** END MACRO PROCESSING *************
> > **** BEGIN MACRO PROCESSING ***********
> > Processing: 'SERVICE ALERT:
> > website.com;HTTP;$SERVICESTATE$;$SERVICESTATETYPE$;$SERVICEATTEMPT$;Name
> or
> > service not known
> > '
> > Done. Final output: 'SERVICE ALERT: website.com
> ;HTTP;CRITICAL;HARD;3;Name
> > or service not known
> > '
> > **** END MACRO PROCESSING *************
> > =======================================================
> >
> > Returns OK:
> > =======================================================
> > **** BEGIN MACRO PROCESSING ***********
> > Processing: '$USER1$/check_http -I $HOSTADDRESS$ $ARG1$'
> > Done. Final output: '/usr/local/icinga/libexec/check_http -I
> website.com
> > '
> > **** END MACRO PROCESSING *************
> > =======================================================
> >
> > Regards,
> > Andrew
> >
> >
> > On Wed, Aug 11, 2010 at 10:00 PM, Michael Friedrich
> > <michael.friedrich@...> wrote:
> >>
> >> Andrew D wrote:
> >> >
> >> > Not sure if this is the appropriate place for (silly?) questions, but
> >> > here goes.
> >> >
> >> > Is there a way to see the exact command sent from icinga?
> >> >
> >> > If i try it from the shell, it works, but in the config file, it
> >> > doesn't work. So perhaps i have messed up, so i'd like to see the
> >> > exact command sent and see how it expands the check_http! line.
> >> >
> >> > The icinga.log only shows the result of checks. Or can i turn on
> >> > verbose logging?
> >>
> >> enable debugging, and set the debug_level to fit your needs in
> icinga.cfg
> >>
> >> Kind regards,
> >> Michael
> >>
> >>
> >> --
> >> DI (FH) Michael Friedrich
> >>
> >> Vienna University Computer Center
> >> Universitaetsstrasse 7 A-1010 Vienna, Austria
> >>
> >> email: michael.friedrich@...
> >> phone: +43 1 4277 14359
> >> fax: +43 1 4277 14279
> >> web: http://www.univie.ac.at/zid
> >>
> >> Icinga Core& IDOUtils Developer
> >> http://www.icinga.org
> >>
> >>
> >>
> >>
> ------------------------------------------------------------------------------
> >> This SF.net email is sponsored by
> >>
> >> Make an app they can't live without
> >> Enter the BlackBerry Developer Challenge
> >> http://p.sf.net/sfu/RIM-dev2dev
> >> _______________________________________________
> >> icinga-users mailing list
> >> icinga-users@...
> >> https://lists.sourceforge.net/lists/listinfo/icinga-users
> >
> >
> ------------------------------------------------------------------------------
> > This SF.net email is sponsored by
> >
> > Make an app they can't live without
> > Enter the BlackBerry Developer Challenge
> > http://p.sf.net/sfu/RIM-dev2dev
> >
> > _______________________________________________
> > icinga-users mailing list
> > icinga-users@...
> > https://lists.sourceforge.net/lists/listinfo/icinga-users
> >
> >
> ------------------------------------------------------------------------------
> > This SF.net email is sponsored by
> >
> > Make an app they can't live without
> > Enter the BlackBerry Developer Challenge
> > http://p.sf.net/sfu/RIM-dev2dev
> > _______________________________________________
> > icinga-users mailing list
> > icinga-users@...
> > https://lists.sourceforge.net/lists/listinfo/icinga-users
> >
> >
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by
>
> Make an app they can't live without
> Enter the BlackBerry Developer Challenge
> http://p.sf.net/sfu/RIM-dev2dev
> _______________________________________________
> icinga-users mailing list
> icinga-users@...
> https://lists.sourceforge.net/lists/listinfo/icinga-users
>
|