False alert: process instances (Oracle tnslsnr listener)

[Anon Anon]

Hi,

With the processes probe you can monitor the number of instances that the probe should find.
We monitor the tnslsnr listener from oracle DB that there is only 1 instance (It seems in the past there was a bug in oracle, when 2 processes with same name are active the users are no longer able to log in).
Nimbus is often reporting that he find 2 instances instead of 1, this for 10 seconds and then closes the alert again. Does anyone have the same problem?
The simple solution is to send the alert after 10 seconds, but the false alert is bad for our statistics we deliver to the upper management.
How can I filter the messages for the first 10 seconds?

Best regards,
steven

[Anon Anon]

Steven,

You could create an AO pre-processing rule that would make the alarm invisible when it first comes in.  Then you would need an AO profile that makes the alarm visible after it repeats X times or is open for X seconds.

When reporting statistics, you would want to exclude all alarms that were still invisible at the time they were closed.  That should make sense from a business perspective, since the alarms should only be invisible for as long as you do not consider them to indicate a problem that requires follow-up.

-Keith