APM Alarm Missing ci_unique_id Attribute in DX OI SaaS

Products

• DX Operational Observability
• DX Operational Intelligence
• DX OI SaaS

Issue/Introduction

Customers may report that APM Alarms arriving in AIOps do not include the ci_unique_id attribute, preventing proper CI correlation in the topology and impacting situation grouping and impact analysis.

Environment

DX O2 SaaS (Application Performance Management)

 

Cause

The ci_unique_id attribute is only populated when an APM Alert is configured with Combination set to "Any".

 

When Combination is set to "All", the alert engine aggregates all matching metrics/agents into a single event without preserving individual CI context. As a result, ci_unique_id is not generated.

 

When Combination is set to "Any", the alert triggers individually for each matching metric, preserving the CI context required to populate ci_unique_id.

 

Note: The absence of ci_unique_id may also be expected in the following scenarios, regardless of the Combination setting:

 

- The monitored entity does not exist as a CI in the AIOps topology

- The alarm is related to monitoring agent/infrastructure health (not a business CI)

- The alarm source is not integrated with topology discovery

- Custom metrics (:custom) that do not include standard Kubernetes labels

Resolution

1. Navigate to the APM Alert configuration

2. Locate the Combination field under Metric Groupings

3. Change the value from "All" to "Any"

4. Save the alert configuration

5. Wait for the next alert trigger and confirm ci_unique_id is now populated

 

 

If the issue persists after changing the Combination setting, verify that a corresponding CI exists in the AIOps topology for the monitored entity before escalating further.