Hi Shawn,

Based on what you've described I'd suspect it's the 10m delay, but you'd want to compare the status history and the change history below as Adam indicated.

The only other options that should cause a 'red' to be yellow should all be shown pretty clearly on the HTML of the page itself. Things like 'modify's or a dependency failure should be indicated.

Do you see any unusual errors in either the xymonnet or the xymond logs around this period?

-jc

On Mon, October 5, 2015 4:11 pm, Adam Goryachev wrote:

Hi Shawn

The status page should say how long the status has been that colour for, or else you can click the history button to see more details and when the status changed colour.

Regards, Adam

On 06/10/15 03:40, Shawn Heisey wrote:

...

Below is the text of the status page for the HTTP test on one of my hosts, copied out of a browser window. Note that the specific test line shows "red" (the X icon) ... but this test as a whole is showing a yellow status, and therefore we did not receive an alarm notification. This is monitoring a production website and we were notified of the problem by the customer, not our own monitoring. This makes us look unprofessional.

Why would a 404 response code not result in a red status, especially when the inner test is marked red in the text? The Xymon server is version 4.3.21, built as an RPM from unmodified source.

I do have "delayred=http:10" on the hosts.cfg line. Could this be a case where the customer notified us before the delayred period expired?

Thanks, Shawn

===================================

Mon Oct 5 10:29:12 2015: Not Found

red http://spark.REDACTED.com:8080/ - Not Found

HTTP/1.1 404 Not Found Server: Apache-Coyote/1.1 Content-Length: 0 Date: Mon, 05 Oct 2015 16:28:24 GMT Connection: close

Seconds: 0.01

---

Xymon mailing list Xymon at xymon.com http://lists.xymon.com/mailman/listinfo/xymon

-- Adam Goryachev Website Managers www.websitemanagers.com.au

---

Xymon mailing list Xymon at xymon.com http://lists.xymon.com/mailman/listinfo/xymon