monitoring http 8888 port

[Max]

It's always a balancing act to find the right combination of
flexibility vs. readability for Nagios configurations.  For larger
groups I tend towards readability and establishing Nagios
configuration coding standards so that multiple authors can work
together and easily understand each others' configurations (like you
would do on a software development team), for times when I am *the*
only user of Nagios I might tend more towards the flexibility of what
you have done below.

- Max

On Jan 6, 2008 5:25 PM, Paul <news at pointdee.co.uk> wrote:
> Please scroll to the bottom
>
> Wim De Geeter wrote:
> > check_command          check_http_port!8888
> >
> >
> > define command{
> >     command_name          check_http_port
> >     command_line             $USER1$/check_http -H $HOSTADDRESS$ -p $ARG1$
> > }
> >
> > John wrote:
> >> I'm trying to monitor an internal webserver that run's on port 8888. I have
> >> this setup in my minimal.cfg file. It's commented out because it gives me an
> >> error that it can't connect.
> >>
> >> #define service{
> >> #        use                             generic-service         ; Name of
> >> service template to use
> >> #        host_name                       hrms
> >> #        service_description             HTTP
> >> #        is_volatile                     0
> >> #        check_period                    24x7
> >> #        max_check_attempts              4
> >> #        normal_check_interval           2
> >> #        retry_check_interval            1
> >> #        contact_groups                  stg-admins
> >> #        notification_options            c,r
> >> #        notification_interval           960
> >> #       notification_period             24x7
> >> #        check_command                   check_http_8888
> >> #        }
> >>
> >>
> >> I also have this in my checkcommands.cfg file
> >>
> >> # 'check_http' command definition
> >> define command{
> >>         command_name    check_http_8888
> >>         command_line    $USER1$/check_http_8888 -H $HOSTADDRESS$
> >>         }
> >>
> >> It's right below my normal check_http lines.
> >>
> >>
> >> Does anyone know what I'm missing here?
> >>
> >> Thanks
> >>
> >> John
> >>
> >>
> >> -------------------------------------------------------------------------
> >> This SF.net email is sponsored by: Microsoft
> >> Defy all challenges. Microsoft(R) Visual Studio 2005.
> >> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> >> _______________________________________________
> >> 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
> >>
> >
> >
> > ------------------------------------------------------------------------
> >
> > -------------------------------------------------------------------------
> > This SF.net email is sponsored by: Microsoft
> > Defy all challenges. Microsoft(R) Visual Studio 2005.
> > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> >
> >
> > ------------------------------------------------------------------------
> >
> > _______________________________________________
> > 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
>
> I find the following to be more flexible and as yet haven't run into any
> issues although it's possible the spaces in $ARG1$ could cause problems
> with some checks
>
> check_command          check_http_custom!-p 8888
>
>
> define command{
>   command_name          check_http_custom
>   command_line          $USER1$/check_http -H $HOSTADDRESS$ $ARG1$
> }
>
> The advantage of this is that you can add other variables without having
> to add another command definition i.e
>
> check_http_custom!-p 8888 -e HTTP/1.0
>
> Paul
>
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2005.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> 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
>

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
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