alert problem

[David Barr]

We have an alert configured to trigger if we haven’t received a message in 6 minutes and if that condition has been true for 29.5 hours.  We received a message for that system at 3:22pm on Monday.  The alert triggered on Tuesday at 9:00am.  The thread had been running the entire time.  Has anyone seen this bug before? Is there a better way to configure this alert so that it will work properly?

Also, the reason that we have the “comparing” value to a much smaller value than the “duration” value is so that we minimize false alerts that happen when a process is restarted and Cloverleaf doesn’t remember the last receive time.

Topic

[James Cobane]

I think there may be a couple of issues going on.  Since there is a time window of 9:00 – 17:00, and the fact the Duration is longer than an actual day, may be causing some conflicts.  Would it be more reasonable to check if you haven’t rec’d something for 6 minutes for a duration that is less than 8 hours (The window of 9:00 – 17:00)?

Jim Cobane

Henry Ford Health

[Michael Hertel]

If a train leaves from Chicago…

this is too much math for me!

[Chris Williams]

Can anyone say for certain what the Last Receive comparison units are? I can’t seem to find anything in the documentation. We all assume it is seconds.

The one alert I have configured to work with Last Receive is set to trigger >= 3600, and it fires after the connection is idle 5-6 minutes. The text in %A is “Thread last inbound message received time … is more than or equal to 3600”

Chris Williams

[Author]

Replies