Is that normal that Pre-processing rules still running to message in maintenance mode period? How can we handle with this?
Please check the below
Tech Tip - maintenance_mode probe behavior
Below is what happens at nas during maintenance mode
interaction with nas probe
nas probe builds list of which device is in under maintenance by regularly asking maintenance_mode probe.
maintenance_mode probe provides the latest info of maintenance_window table (its end_time not expired).
when new alert is arriving at nas probe, nas probe checks dev_id (which is an attribute in alert) and if dev_id is in the list, then nas discards the alert
Could you please detail the issue which you are facing with the pre-processing rules during maintenance mode ?
I only do this in LUA script:
event.custom_2 = ""event.custom_3 = ""return event
I use this to control e-mail and sms send events. So, in maintenance window, this script does not have to execute, considering the rule filter.
in maintenance window, alarm is not arriving at nas probe, so the alarm will never be target of pre-processing.
That is very strange, because I´m asking here because the alarm came to pre-processing when maintenance window is still active.
- alarm severity is informational. informational alarm is exception - not discarded by maintenance window
- wrong device is placed into maintenance.
proper dev_id has to be placed into maintenance, please check alarm dev_id and the dev_id is placed into maintenance.
Ok, I´ll take a look. Thanks for your help
YU, the alarm serverity is informational. So how can we handle with this?
thank you for update
unfortunately it is per a design - maintenance is not designed to spoil informational alert even alarm is coming from device while maintenance window is open for.
so you may want to use NAS pre-processing rule to spoil that alert.
Retrieving data ...