Objective
Describe the steps to perform web sites monitoring for keywords.
Target audience
Intended for OpMon administrators and IT teams, that need to perform Web Sites monitoring for keywords
Solution
How should we monitor Web Sites? Easy, monitoring the 80 TCP port Maybe, but monitoring the 80 TCP port doesn’t guarantee that the page is OK, I ask you all:
- What if there has been a problem with the page development
- What if there is a problem on the site that shuts down the page?
- What if there is an error in the homepage of your site?
We can also monitor the apache process (NRPE) or the IIS (SNClient)? Yes, thinking on the possibility of having a NAT being done for the wrong service. Of course, but even so doesn’t solves the development problem! All this story to say that we can also monitor a particular word of a particular page with the same check_http, as shown below:
1) Access your server
cd /usr/local/opmon/libexec/
2) Sintaxe
./check_http -I IP-Servidor-Web -u http://EndereçoDoSite/Pagina.html -R PalavraChave
3) Testing
./check_http -I 216.34.181.96 -u http://nagios.sourceforge.net/docs/3_0/quickstart.html -R quickstart
4) Response
HTTP OK HTTP/1.1 200 OK – 0,456 second response time |time=0,456224s;;;0,000000 size=4844B;;;0
5) Looking for a keyword that doesn’t exist (e.g.: Luciano)
./check_http -I 216.34.181.96 -u http://nagios.sourceforge.net/docs/3_0/quickstart.html -R Luciano
6) Reply
HTTP CRITICAL – pattern not found|time=0,439705s;;;0,000000 size=4844B;;;0
Source: Nagios na Prática