Is there a mechanism to remove the selected alarms manually from the dataminer manually. TTL configuration is available but this is a global setting rather than a alarms related to a specific element that may have created a huge amount of valid alarms.
Hi Skrikanth,
If one or few elements are causing a lot of “useless” alarms, it’s always possible to create a new alarm template (which either ignores or filters those alarmed parameters) and assign that special template individually to the elements in question.
Another option is to change the thresholds of the alarms, as well as hysteresis, so that the alarm does not get generated immediately after a value crosses the threshold, but rather waits some time before doing so, thus removing a lot of alarms due to “bouncing” values coming above and below the set thresholds.
Cheers!
Thanks Rodrigo, this certainly helps to reduce the impact of DataMiner having too many alarms for a particular element. However my question is more specific to pruning the alarms from the database so that we can clear the unnecessary data in the database ahead of TTL configuration kicks in.
If removing the data per element is not the best practice then that’s completely acceptable. Just need to understand the best way of handling a single or few elements spewing lot of alarms that may not be providing value.