Custom attributes in DX O2 alarms get cleared when updated alarms from DXUIM do not explicitly include them
Article ID: 440609
Updated On:
Products
Issue/Introduction
## Symptoms
- Updates to alarms sent from DX Unified Infrastructure Management (UIM) to DX Operational Intelligence (OI) cause previously populated custom attributes to be cleared.
- Custom attributes **custom_1 through custom_10** are reset even if the update does not explicitly include or modify these specific fields.
- This behavior complicates alarm enrichment and notification workflows in DX OI.
Environment
DX O2 SaaS / OnPrem
Cause
In DX Operational Intelligence, the attributes **custom_1 through custom_10** are specifically reserved for the source product. When an update for an existing alarm is received from the source (e.g., DX UIM), the source product is expected to send the full set of these reserved attributes. If they are not included in the update payload, they are treated as null and cleared in the DX OI database [Update of UIM alarm](
Resolution
To ensure custom data persists during alarm updates in DX OI, users should utilize higher-indexed custom attributes. DX OI supports a total of 50 persistent custom attributes that are not reserved by source products.
1. **Use custom_11 through custom_60:** Unlike the first ten attributes, attributes starting from **custom_11** up to **custom_60** are intended for user/integration persistence. These attributes will not be cleared by source product updates and will remain available to use in future releases.
2. **Implementation:** Map your specific data or status values to `custom_11` or higher within your TAS (Topology Analytics Service) attribute mapping or alarm enrichment policies [Update of UIM alarm]
Additional Information
IMPORTANT: While custom_1 through custom_10 are visible for filtering in some GUI sections, higher-indexed attributes (custom_11+) may not be fully documented in older versions but are the official method for data persistence across alarm updates.
Feedback
