I have a question from a user: Can we mask a row or multiple rows of a table in advance to prevent an alarm from being generated?
For example, in the image below, the user wants to perform testing or maintenance on the highlighted interface, which would normally trigger alarms. Before the alarm is generated, can the user mask that interface in advance so that no alarm is triggered or appeared in active alarm when testing or maintenance begins?
Is there any other way to suppress alarm generation for that interface beforehand, aside from the masking method?
I believe the desired behaviour can be obtained, but with a slightly different approach.
1. Preventively mask the full element (but that means receiving NO alarms for any of the Parameters) - for a period of time (the maintenance window), so that when the planned work is over, if any alarms are still present, they can be promptly notified.
2. Changing the Alarm Template at scheduled times, so that the specific parameter is excluded from monitoring, during the maintenance - a bit of an overkill for just one interface... but possible - some VBxx0 integrations for DM used to have a built-in feature like this, e.g. to exclude from monitoring specific TV programs not aired over night, in order to prevent alarms when not required.
3. If the Protocol (and licensed capacity) allows "DVE creation" for each interface, then the DVE can be masked as in point 1 (gonna be a lot more elements, though)
In practice, to mask a specific alarm, without losing visibility over the rest of KPIs in the element, the alarm needs to be raised first - as an alarm ID is needed to mask a specific alarm.
HTH