In this scenario, customer has alarm enrichment configured to populate the "Custom 3" and "Custom 4" alarm fields.
However, sometimes these fields are not populated. This problem happens randomly, and without any change being done in the alarm_enrichment rules/configuration:
Sometimes, after customer restarting NAS and alarm_enrichment probes and acknowledging/deleting the current alarms, the new alarms are generated with these fields populated:
This problem is solved by deploying NAS_9.20_T2 probe. Please open a support case in order to obtain this probe version.