How to monitor complex websites?

[Frank Thyes]

Hi Richard,

+++ Richard Luys-Nagios User [Wed, Jun 07, 2006 at 12:40:39PM CEST]:
> 
> I have to monitor a website that is more complex than check_http can  
> handle. Please advise.
> 
> 1.
> The website we need to monitor contains a MDM application for a product  
> search. This is dynamic and browser-restricted content. The User-Agent  
> string of the browser is checked and if not correct you will be redirected  
> to a static error page, instead of the search form which is dynamically  
> generated (with some fields filled in with defaults).
> 
> 2.
> This website runs on a cluster consisting of 5 nodes. Users connect to  
> these nodes based on a round-robbing principle. When a node goes down it  
> is possible that they get a error-message telling them the server is  
> unavailable. When this happens the node-number of the node that is  
> misbehaving can be found in a cookie. So what we like to have is the  
> following:
> - check the website
> - if it gives an error read the nodenumber from the cookie
> - Create a CRITICAL for the website with the node-number in the output
> 
> We need to monitor this website, but check_http cannot (afaik) send a  
> specified User-Agent string. Is anybody aware of another solution, or  
> should I create one? If the latter: I was thinking about creating a check  
> based on wget, since wget is able to send User-Agent strings and can do  
> something with cookies as well. Can someone with enough knowledge on this  
> matter tell me if this is doable, or should I walk another path?
> 
> Please advise, any suggestions are welcome!

Use Perl.

Regards
Frank
-- 
#!/usr/bin/perl 
print&f(($_=(3x3)."3+33")=~s=3(?![^3]|$)=&f=eg);
sub f{eval(@_?$_:"'$&+'x3");}


_______________________________________________
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