fix(dcl): identify MxGateway native alarms by object-relative reference #4
Reference in New Issue
Block a user
Delete Branch "fix/native-alarm-object-ref-identity"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Surface native Galaxy alarms as 'Z28061.HeartbeatTimeoutAlarm' (SourceObjectReference) instead of the full 'Galaxy!.
Surface native (Galaxy/MxGateway) alarms by their object-relative reference (e.g. "Z28061.HeartbeatTimeoutAlarm") instead of the gateway's full provider reference ("Galaxy!<area>.<object>.<alarm>"). The area is already preserved in Category and the object reference is globally unique within the galaxy, so the full provider prefix added only noise to the alarm identity operators see. MxGatewayAlarmMapper.MapTransition/MapSnapshot now set SourceReference from SourceObjectReference, falling back to AlarmFullReference only when the gateway omits the object reference. +2 mapper tests; full DCL suite green (158).