[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
badhttp test problem - alerting on single failure
- To: hobbit (at) hswn.dk
- Subject: badhttp test problem - alerting on single failure
- From: Charles Jones <jonescr (at) cisco.com>
- Date: Wed, 11 Oct 2006 00:51:07 -0700
- Authentication-results: sj-dkim-4.cisco.com; header.From=jonescr@cisco.com; dkim=pass ( 60 extraneous bytes; sig from cisco.com verified; );
- Dkim-signature: a=rsa-sha1; q=dns; l=3200; t=1160553058; x=1161417058; c=relaxed/simple; s=sjdkim4002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=jonescr@cisco.com; z=From:Charles=20Jones=20<jonescr@cisco.com> |Subject:badhttp=20test=20problem=20-=20alerting=20on=20single=20failure; X=v=3Dcisco.com=3B=20h=3D2oCS5NAHogZ2hSEUZ4EwauBFlEg=3D; b=FrwiRw1YUwTEVVI13UJepTIwuuRkZy3m6LC4wvnyibWLcTAZ6PvBScUNI2pMJjGnFmvF9U/l DkA4uKzjccjwi0muY0gNXqxnuU7gW7gG5rqihgGfBK2NbN7O4GxNn2Xm;
- User-agent: Thunderbird 1.5.0.7 (Windows/20060909)
I have a host where I am doing two http tests against. One of the URLs
has shown a tendency to false alarm (go red and then a minute later back
green), twice a night.
In an attempt to reduce these false alarms, I used the "badhttp" tag as so:
---snippet from bb-hosts---
1.2.3.4 URL-Site_Portal # cont;http://mysite.com/public/index.html;Found
http://www.mysite.com/private/index.html badhttp-*-0000-1800:1:2:4
---
The second URL is the one that blips, and adding the badhttp tag has not
helped, it still alerts after a single failure, and history shows no
status changes to clear or yellow.
Here is a cut and paste of the status when it alerted red (The second
check was listed below this one, and was green - also interestingly, the
second check shown on the status page is the first URL from the bb-hosts
line):
Wed Oct 11 07:05:56 2006: Server timeout ; OK
http://www.mysite.com/private/index.html - Server timeout
Seconds: 10.31
Is there any way that I can troubleshoot this? Could it be caused from
doing two http tests against the same site (maybe badhttp only takes
effect for the first one)?
-Charles