Hello Team
On dataminer for a specific element, I have a setup where an alarm triggers a correlation rule based on defined filters, which in turn executes an Automation script to send emails based on some business logic.
My requirement is to suppress that specific alarm from appearing in the Alarm Console for 24 hours after it is first handled. If the same alarm condition still persists after 24 hours, it should trigger the workflow again (i.e., generate a new email) and then be suppressed again for another 24 hours.
However, I’m facing the following challenges:
- I cannot acknowledge the alarm, as it is polling-based and reappears on every poll cycle.
- I cannot apply parameter maintenance, since the alarm is on a table column (row-level).
Given these constraints, what would be the recommended approach to suppress or “mask” this specific alarm for a fixed duration (24 hours) while still allowing it to re-trigger the workflow after that period?
I am unable to find an option to mask an alarm via automation script or via correlation rule.
Hi Ramesh,
Before jumping to masking, is it not an option to use alarm scheduler (see Scheduling an alarm template)?
Please let us know if this cover your use case.
Hope it helps.
Hi Ramesh,
Another option could be assigning a different alarm template to an element via automation script. There is an method to set an alarm template to an element: https://docs.dataminer.services/develop/api/types/Skyline.DataMiner.Automation.Element.SetAlarmTemplate.html#Skyline_DataMiner_Automation_Element_SetAlarmTemplate_System_String_
Please could you let us know if this solve the use case?
But this is a column parameter in a table, and we do not want to suppress alarming for the entire column. Our requirement is to suppress only a specific alarm instance for 24 hours when certain criteria are met. There is a logic on correlation to find this alarm instance based on other column data on the table.
Using an alarm template condition would not work in this case because , suppressing via alarm template will reflect on the entire column. We still need the alarm to be generated so that it can be captured by the Correlation Rule. The Correlation Rule then triggers an Automation script, which sends an email based on some business logic.
Only after the email is sent we want to suppress that specific alarm for 24 hours. After the 24-hour period, if the alarm condition still persists on the next poll, it should again trigger the email workflow and then be suppressed for the next 24 hours. This cycle should continue until the alarm is cleared at the source.
Hello Miguel,
That approach wouldn’t work for our use case, as the alarm timings are not predictable. Our requirement is event-driven—we need to trigger an email and suppress only a specific set of alarms for a defined duration (e.g., 24 hours) starting from when the alarm occurs, rather than based on predefined time schedules.