Hello all,
Is it possible to limit the type of notices that are generated and displayed in the alarm console (an editable template or config file that dictates which Notices are considered valid within a DMS)? Alternatively, is it possible to have the notices cleared automatically after some amount of time to eliminate the need for a user to manually clear them from the alarm console?
Example Notice types that we’d be interested in limiting or automatically clearing include:
- “Alarm history exceeded 100 alarms – Revise Template”
- “Duplicate name detected”
Hi Ben, Thank you for the feedback. I completely agree (as well as the userbase of this particular DMS) that under normal circumstances, the correct approach should be to solve the root cause of the notices.
However, we are amidst migrating the solution to a brand new upgraded DMS where we do plan to invest efforts in solving the root cause of the notices. The necessary alarm template changes are understood to address the alarm history notices. We do not yet know if the duplicate name notices will be observed on the new DMS (they may never be observed), but if they are, we will be addressing root cause.
Given the operational days of the legacy system are numbered and development time and general configuration changes are not desirable on a system that is going to be decommissioned soon, the user base was interested in knowing of an easy way to automate the management of these notices.
As Ben mentioned above, it is indeed advisable to avoid situations like this all together as these limits are typically put in place for a reason. However, if you need to, you can configure some of them. How to do that specifically depends on the specific notice. I suggest to do a search of the DataMiner Docs to find more information.
Specifically, the notice about the history exceeding 100 alarms can be configured, or even disabled in MaintenanceSettings.xml in the AlarmsPerParameter tag. See https://docs.dataminer.services/user-guide/Reference/Skyline_DataMiner_Folder/More_information_on_certain_files_and_folders/MaintenanceSettings_xml.html#alarmsettingsalarmsperparameter.
The notice “Duplicate name detected” can not be disabled as far as I’m aware.
Thank you for the information Tobe!
Hi Thomas – would the proper way forward not be to address the root cause of these notices. An alarm history that exceeds 100 updates often indicates poorly configured alarm thresholds and a lot of toggling. Or are these legitimate life cycle updates (ownership transitions and other meaningful properties). Alarm hygiene is the foundation of a healthy fault management solution.
And similar for the duplicate name. This cannot be addressed by fixing this?