Instances, Alerts and keeping data

Started by Tursiops, July 22, 2016, 02:56:34 AM

Previous topic - Next topic

Tursiops

Hi,

I noticed that when an instanced DCI triggers an alarm and the instance itself is then later removed, the alarm remains in the system.
Guess it would make sense if alarms were removed from the system together with DCI data when an instance is removed?

Along the same line, it would also be nice to be able to tell the system to keep an instance "active" for a (per instance DCI configurable) period, just in case the same instance comes back later. In our case we have some systems that have USB drives which we are monitoring for disk space. The drives are sometimes detached for some time, but do come back. Once the disk is detached though, the instance will eventually be removed, wiping the DCI data, keeping any potential "zombie alarms" and then creates a new DCI later when the disk is reattached.

I could think of other scenarios where keeping the "old" DCI data for a while would make sense, guess it all depends on how much one actually utilises instance discovery and instance discovery filters.

Cheers

tomaskir

Both of the issues you mention were mentioned multiple times here on the forums, and I think there are also bug-tracker feature requests for them.

I definatelly agree this needs addressing, +1 from me :)

Victor Kirhenshtein

There is an issue in bug tracker: https://dev.raden.solutions/issues/976. I'll try to implement it in 2.1 branch.

Best regards,
Victor