Alarms not appearing in console due to incorrect NAS pre-processing regex trailing 'OR' statement

Products

• DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

• Probes (e.g., url_response) are configured correctly and generating alarms locally.
• dr.nimbus or probe logs confirm the alarm packet is being sent to the hub.
• No alarms are visible in the Operator Console (OC) or Infrastructure Manager (IM).
• Increasing nas log level to 5 shows pre-processing rules are firing and excluding the alarms.

Environment

• DX Unified Infrastructure Management (all versions)
• nas probe (all versions)

Cause

An incorrectly formatted Regular Expression in a nas pre-processing rule. Specifically, the use of a trailing pipe followed by a wildcard (|.*) at the end of a regex string. In regex logic, the | symbol acts as an "OR" operator. By ending a string with |.*, the rule is instructed to match the specific patterns defined OR match "anything else" (.*), effectively causing the rule to exclude every alarm that passes through the nas.

Resolution

1. Open the nas probe configuration.
2. Navigate to the Pre-processing Rules tab.
3. Locate the rule that is incorrectly excluding alarms.
4. Correct the Message String regex by removing any trailing |.* or ensuring that all "OR" conditions are specific and intentional.
5. Use the F2 key in the nas GUI to test the regex against specific alarm messages to ensure it only matches the intended targets.
6. Click Apply and OK to save changes.