Yellow->red escalation, bug or feature?

If an alert's been yellow for a while and then goes red I do want to
be alerted - but I only want the tier1 person to be alerted.

The current behavior of immediately paging all the way up the food
chain to the tier4 people, the minute it goes red,  seems wrong to me
- and it is REALLY upsetting our tier4 people who are getting woken up
at 3am for stuff the tier1 person can handle.

(This is happening for us most often with disk space. People are not
super-fast at cleaning up disk space. But I'm waking up managers for
disks that have hit 90% full and that's just not cool)

If other people like the behavior, making it a knob we can turn is
fine. Just something I can do to keep from waking the whole crew up.


On Wed, Jan 11, 2012 at 2:55 PM, Josh Luthman
<user-4c45a83f15cb@xymon.invalid> wrote:

I think we need a new argument for this new condition, something like
DURATIONWHILERED

Josh Luthman
Office: XXX-XXX-XXXX
Direct: XXX-XXX-XXXX
XXXX Wayne St
Suite XXXX
Troy, OH XXXXX


On Wed, Jan 11, 2012 at 2:53 PM, Gore, David W (David)
<user-368fd67cc6bd@xymon.invalid> wrote:

Since it has been argued that it is not exactly a bug I would only humbly
request that the current behavior is not changed but enhanced for those who
want it to work differently.   If an alert has been alarming for x time and
then goes red do you want to wait even longer to be alerted.  Yellow time +
red time or yellow time and now its red so alert, provided the yellow time
exceeds the red threshold.


~David


From: xymon-bounces at xymon.com [mailto:xymon-bounces at xymon.com] On Behalf Of
Carl Melgaard
Sent: Wednesday, January 11, 2012 04:56
To: 'xymon at xymon.com'
Cc: 'user-834d44be5e50@xymon.invalid'

Subject: Re: [Xymon] Yellow->red escalation, bug or feature?


Hi,


It would be interesting to see if this bug could be squashed, now that
flap-detection is in the game. But I haven’t seen Henrik on this list for a
good time now – he’s active on the developer-list, tho – so I’m crossposting
it there.


Regards,


Carl Melgaard


Fra: xymon-bounces at xymon.com [mailto:xymon-bounces at xymon.com] På vegne af
SebA
Sendt: 10. januar 2012 12:24
Til: Xymon at xymon.com
Emne: Re: [Xymon] Yellow->red escalation, bug or feature?


I agree that this is not a new issue.  I have discussed this before
(http://lists.xymon.com/archive/2009-January/023201.html (Henrik's reply:
http://lists.xymon.com/oldarchive/2009/02/msg00133.html) and
http://lists.xymon.com/archive/2008-September/020998.html).


But now that we have flap detection, I'm not sure that Henrik's listed
problem with changing it is really an issue.  So I hope it can be changed!


BTW, The oldarchive is better for following threads (provided they don't
cross month boundaries):

http://lists.xymon.com/oldarchive/2008/09/msg00057.html

Compare with the previous link.  However, the new archive keeps
attachments.  It would be nice if the functionality of both archives were
merged...

Kind regards,

SebA


From: xymon-bounces at xymon.com [mailto:xymon-bounces at xymon.com] On Behalf Of
Ryan Skadberg
Sent: 09 January 2012 20:23
To: Xymon at xymon.com
Subject: Re: [Xymon] Yellow->red escalation, bug or feature?

I've seen this exact same issue going all the way back to hobbit, so this is
not a new issue with 4.3.  I would love to see it fixed though, as it's very
annoying to get paged when you are second or third on call and everyone gets
notified on the first red.


Skadz


On Mon, Jan 9, 2012 at 2:12 PM, Elizabeth Schwartz
<user-c61747246f66@xymon.invalid> wrote:

You're saying yellow for an hour and red for a few seconds triggers
like it was red for an hour?

I note that the previous example was for a custom test but I also have
seen this for the disk test:
(set to email  every 8 hours when yellow)


Sat Dec 24 10:53:27 2011        red     0:49:09
Sun Dec 18 03:01:51 2011        yellow  6 days 7:51:36

Thu Dec 22 17:54:39 2011 jumpstart.example.com.disk (10.100.4.33)
user-e49400df80ec@xymon.invalid[139] 1324594479 100
Fri Dec 23 01:54:40 2011 jumpstart.example.com.disk (10.100.4.33)
user-e49400df80ec@xymon.invalid[139] 1324623280 100
Fri Dec 23 09:54:47 2011 jumpstart.example.com.disk (10.100.4.33)
user-e49400df80ec@xymon.invalid[139] 1324652087 100
Sat Dec 24 10:54:27 2011 jumpstart.example.com.disk (10.100.4.33)
user-e49400df80ec@xymon.invalid[139] 1324742067 100
Sat Dec 24 10:54:27 2011 jumpstart.example.com.disk (10.100.4.33)
alert1[149] 1324742067 100
Sat Dec 24 10:54:27 2011 jumpstart.example.com.disk (10.100.4.33)
alert2[152] 1324742067 100
Sat Dec 24 10:54:27 2011 jumpstart.example.com.disk (10.100.4.33)
alert3[153] 1324742067 100
Sat Dec 24 10:54:27 2011 jumpstart.example.com.disk (10.100.4.33)
alert4[154] 1324742067 100