Nagios Support Forum

RyanMule wrote:this address prompts for a login

     -a, --authorization=AUTH_PAIR
        Username:password on sites with basic authentication

     -e, --expect=STRING
        Comma-delimited list of strings, at least one of them is expected in
        the first (status) line of the server response (default: HTTP/1.)
        If specified skips all other status line logic (ex: 3xx, 4xx, 5xx processing)

     -d, --header-string=STRING
        String to expect in the response headers

     -s, --string=STRING
        String to expect in the content

...

     -l, --linespan
        Allow regex to span newlines (must precede -r or -R)
     -r, --regex, --ereg=STRING
        Search page for regex STRING
     -R, --eregi=STRING
        Search page for case-insensitive regex STRING
     --invert-regex
        Return CRITICAL if found, OK if not

RyanMule wrote: I apologize for the odd request

mcapra wrote:

RyanMule wrote:this address prompts for a login

A very important question; How is it prompting for a login? Is it using basic authentication? Some sort of form based authentication?

The check_http plugin supports basic authentication via the -a argument:

Code: Select all

     -a, --authorization=AUTH_PAIR
        Username:password on sites with basic authentication

In terms of answering the "did the XML page generate" question, hoo boy there's a lot of options starting with checking response codes (200, 400, 503, etc)

Code: Select all

     -e, --expect=STRING
        Comma-delimited list of strings, at least one of them is expected in
        the first (status) line of the server response (default: HTTP/1.)
        If specified skips all other status line logic (ex: 3xx, 4xx, 5xx processing)

Checking response headers (Content-Type, XSS, etc):

Code: Select all

     -d, --header-string=STRING
        String to expect in the response headers

Checking body contents (specific XML key/value pairs maybe?):

Code: Select all

     -s, --string=STRING
        String to expect in the content

...

     -l, --linespan
        Allow regex to span newlines (must precede -r or -R)
     -r, --regex, --ereg=STRING
        Search page for regex STRING
     -R, --eregi=STRING
        Search page for case-insensitive regex STRING
     --invert-regex
        Return CRITICAL if found, OK if not

Really depends on the specific site, but check_http can cover an awful lot of ground by itself assuming basic auth is the authentication mechanism.

If you're having to navigate forms-based authentication, I'd recommend the following documentation (specifically the bit about the "web transaction" wizard):
https://assets.nagios.com/downloads/nag ... ios-XI.pdf

RyanMule wrote: I apologize for the odd request

Doesn't strike me as odd Login checks are super handy for multiple reasons.

ssax wrote:If it is using form based authentication you will need to use the check_http -P option:

Code: Select all

 -P, --post=STRING
    URL encoded http POST data

You will need to URL encode the data:

https://www.urlencoder.org/

You will need to work with your application developers to determine what POST data you need to submit such as username/pass/etc.

Something like this may work:

Code: Select all

/usr/local/nagios/libexec/check_http -H SERVER -f follow -u '/ews/exchange.asmx/wssecurity' --method=POST -P 'username=USER&password=PASS&loginButton=' -s 'TEXT TO SEARCH FOR' -S -p 443 --sni

cdienger wrote:Glad to hear you found another plugin that seems to work. Are we good to lock this one up?

RyanMule wrote:Yes, this can be locked for now.

cdienger wrote:Glad to hear you found another plugin that seems to work. Are we good to lock this one up?