Wondering whether DataMiner is able to re-alarm, after a set time (configurable?), if the same alarm point is still in an alarm state (according to the alarm template parameters). So, the user would take ownership of the alarm, triage, and look to restore service. However, if it’s still in alarm, an hour later, it would audibly re-alarm, and increment a counter. Also, would there be a way to suppress that alarm from re-occurring every hour, if it’s a known issue that will take 12 hours to resolve, for example? Aware the user can mask the alarm, but doing so removes it from the Active Alarms table, so would need to be a ‘silence’ or ‘suppress’ setting.
Hi Ben,
Wondering whether DataMiner is able to re-alarm, after a set time (configurable?), if the same alarm point is still in an alarm state (according to the alarm template parameters). So, the user would take ownership of the alarm, triage, and look to restore service.
I am not sure if this is possible off the shelf. A possible option could be resending a SNMP trap whenever an alarm is still available. You could use this trap to trigger a custom workflow that could send a notification to users about these alarms so they can acknowledge.
However, if it’s still in alarm, an hour later, it would audibly re-alarm, and increment a counter.
Since you will receive a trap every X amount of seconds, you could implement a counter to keep track for how long the alarm has been unattended. This could trigger another custom notification.
Also, would there be a way to suppress that alarm from re-occurring every hour, if it’s a known issue that will take 12 hours to resolve, for example? Aware the user can mask the alarm, but doing so removes it from the Active Alarms table, so would need to be a ‘silence’ or ‘suppress’ setting.
Indeed, masking should cover this requirement. A possible option could be updating an alarm property so you can use it as filter in the active alarm tab.
Hope it helps.