That is a good workaround, thanks. The workaround I chose was to make
this particular alert page on yellow. But I really need to clarify my
understanding of why an http alert would turn yellow. We have a *lot*
of mission-critical http alerts.
On Thu, Jun 14, 2012 at 9:06 PM, Ralph Mitchell <user-00a5e44c48c0@xymon.invalid> wrote:
I don't know why it's flagging the way it is, but could you break it out
into individual checks?
10.1.2.3 web1.example.com # CLASS:webzone ssh apache
http://web1.example.com/url1.htm
0.0.0.0 web1-url2 # noconn
http://web1.example.com/url2.cfm
0.0.0.0 web1-url3 # noconn
http://web1.example.com/url3.cfm
It's not ideal, but it would give you separate visibility and reporting
until the yellow/red problem is worked out.
Ralph Mitchell
On Wed, Jun 13, 2012 at 6:16 PM, Betsy Schwartz <user-c61747246f66@xymon.invalid>
wrote:
Any thought on this? We just had another missed outage. I am going to have
to start paging on http yellow until this is resolved - UGH
Thanks Betsy
On Jun 7, 2012, at 8:48 AM, Betsy Schwartz <user-c61747246f66@xymon.invalid>
wrote:
I have this default set:
0.0.0.0 .default. # DOWNTIME=0:0000:0300 delayred=http:10
and servers that are monitoring three URL's like so:
10.1.2.3 web1.example.com # CLASS:webzone ssh apache
http://web1.example.com/url1.htm http://web1.example.com/url2.cfm
http://web1.example.com/url3.cfm
What I'm seeing is, with one URL going red with a timeout after 22
seconds, the http test is going YELLOW and then going RED ten minutes
later. Does delayred turn the test yellow? If not, why is this test
turning yellow? We want it to be RED.
What exactly determines whether an http test is red or yellow?
thanks Betsy