You can probably tell I got back to tweaking IM again.....
Anyway, I was curious if there is a mechanism that is built in into
IM server to double check the failures. For example, if a probe
detects a condition that normally triggers an alert (let's say Alarm).
Does InterMapper double check that the condition in fact exists or it
was just a blip, glitch, etc before alerting?
I'd be interested to see a feature that allows control over that kind
of behavior. Let's say, just like under Notifiers one can control the
number of repeating alerts, it would be nice to control there number
of times the condition has to be triggered before alerts goes out.
The reason this is important is so we could make sure that the
condition is there before sending an alert to a pager at 3am. I'd like
to be able to setup alerts going to email after one occurrence and to
pager after, let's say 3. Many times, but the time I crawl out of bed
to see what it is, it already cleared.
Setting it up with delayed notification kind of does the job, but not
really. All it does is delays the notification for a minimum of a
minute, which with default probe timers only gives it an extra one
time to probe it.
I'd like to see Intermapper after detecting a condition being able to
verify it a controllable number of times before sending an alert to a
give notifier.
Consider this a feature request, but I'd still want to understand what
the logic of this behavior is today as implemented. I'm suspecting
many on this list would be interested to hear how IM behaves on
condition detection....
Thank you,
Andrey
__________________________________________________________
Andrey Gordon | Integrity Interactive | Network Engineer |
+1.781.398.3518
____________________________________________________________________
List archives:
http://www.mail-archive.com/intermapper-talk%40list.dartware.com/
To unsubscribe: send email to: [email protected]
