Alarm not assigned to DXO2 Service.

Products

• DX Operational Observability

Issue/Introduction

Users may observe that certain alarms are missing critical updates, resulting in the alarm showing as not assigned to any service.

Observation: The alarm's lifecycle events indicate that the updates (e.g., a service enrichment update and a customer-configured custom script update) were successfully processed.

Result: Despite being processed, the actual alarm drops one of the updates, leading to incomplete data in the system.

Cause

DE663117 - race condition related to how alarm versions are tracked. When an alarm is updated, it is assigned a version timestamp based on the system time in milliseconds which has been found too short.

Resolution

To resolve this timing conflict, the system's versioning mechanism has been enhanced. The alarm version field value has been extended from milliseconds to microseconds. This increased precision ensures that rapid, simultaneous updates receive unique version identifiers and are no longer rejected. Fix will be delivered in the following versions:

SaaS Environments: The fix is targeted for release in version 26.4.1.

On-Premises Environments: The fix is targeted for version 26.2.