Lower severity of an alarm using preprocessing rule

Document ID : KB000034685
Last Modified Date : 14/02/2018
Show Technical Document Details


Customers may have various production operational reasons for wanting to lower the severity of an alarm or alarms related to alarm management processes and standard operating procedures for production.


You may be sending major/critical alarms to your help-desk system as P1 Critical Events that page your on call personnel. You may be getting? sporadic major alarms from controllers that say "Failed to send set_hub to spooler (communication error)".? This is a known problem that's fixed in robot version 5.52 and it generally isnt a serious condition and it seems to eventually resolve itself in most cases.? You may not want to ignore the alarms in case there is a real problem so as an alternative, you want them to show up in the alarm viewer as warnings so you can see them but they don't wake people up in the middle of the night.



NMS 5.61 or higher
nas 3.72 or higher

As an example, simply add a Script under Auto Operator->Scripts and save it as "lower severity of an alarm"

event.level = 4
event.message = "steved" (or some message you want it to filter on)
return event

Don't bother testing it using the green arrow (Validate and Execute script) as it won't work and it will return an error if you try to test it in the AO window.

See screen shot below for sample pre-processing configuration where the Filter type is custom, and reference the script you just created. Name your rule lower severity of an alarm or something like that.

Then use the nas Status window and rt-click and send a test alarm with Critical severity (level 5) and message like Test message from steved

And you will see in the alarm sub-console window the alarm will automatically be changed to a major severity. (level 4).

(hint: filter on the message /.*steved.*/ and Apply the filter so you can see it easily among your alarm message),