Custom situation definition fails to match ASM test names with special characters

Products

• DX SaaS

Issue/Introduction

When you configure a Custom Situation definition in DX SAAS, you may find that filters targeting the ci_unique_id or App Synthetic Monitor (ASM) test names return no matches.

This occurs even when the filter string appears to be an exact match to the test name shown in the UI, particularly when the name contains hyphens (-) or spaces.

Environment

• DX Operational Intelligence (OI) / AIOps SaaS
• App Synthetic Monitor (ASM)

Cause

The DX O2 situation engine performs literal string matching. If your source metric attribute (such as metric_external_id) contains an extra or trailing white space—often introduced during manual naming or configuration—a filter string that lacks that exact character count fails to match. In this case, an extra space is present after the hyphen in the metric path (e.g., "### - ####").

Resolution

To resolve this issue, you must ensure the filter string matches the raw alarm attribute exactly:

1. Identify the Raw Attribute: You examine the JSON attributes of the affected alarm. Locate the metric_external_id or ci_unique_id.
   • Example snippet: "metric_external_id": "App Synthetic Monitor|Monitors|####|### - ####:Result Code"
2. Locate Hidden Spaces: You check for double spaces after hyphens or trailing spaces at the end of the test name string.
3. Adjust the Filter:
   • You update the Situation Definition filter to include the exact character sequence found in step 1.
   • Alternative: You change the filter operator to Contains and use a unique substring that does not include the problematic special characters or spaces.
4. Verify the Fix: You use the Preview button in the Situation Definition editor to confirm that the expected alarms now appear in the results.