Alarms from UIM do not match DX O2 Maintenance Windows due to Entity mapping

Products

• DX Unified Infrastructure Management (Nimsoft / UIM)
• DX Operational Intelligence

Issue/Introduction

Alarms originating from DX UIM may fail to match configured Maintenance Windows in DX Operational Observability (O2). This occurs when the alarm entity is identified by the UIM robot name while the Maintenance Window is defined by the host entity.

Environment

DX UIM 23.4.0
apm_bridge probe 1.07
oi_connector probe 1.57
DX Operational Observability (O2) SaaS

Cause

The issue was due to a product limitation where UIM alarms were matched to O2 Maintenance Windows based on the robot entity rather than the host entity, caused by default mapping configurations in the APM Bridge.

Resolution

This issue is addressed by an enhancement that allows the APM Bridge and Connector to adjust attribute mapping for O2 Maintenance Windows.

Fixed in release 26.6.1 and higher.

For users on older versions, ensure that the entity attributes mapped via apm_bridge align with the criteria used in O2 Maintenance Window selections. If you need to speak with a customer representative or a Support Engineer, see Contact Support.

 

Additional Information

Internal Reference: DE662662
Reference for subscribing to updates: How to subscribe to a KB article