fix(dcl): identify MxGateway native alarms by object-relative reference #4

Merged
dohertj2 merged 1 commits from fix/native-alarm-object-ref-identity into main 2026-06-16 19:58:07 -04:00
Owner

Surface native Galaxy alarms as 'Z28061.HeartbeatTimeoutAlarm' (SourceObjectReference) instead of the full 'Galaxy!.

Surface native Galaxy alarms as 'Z28061.HeartbeatTimeoutAlarm' (SourceObjectReference) instead of the full 'Galaxy!<area>.<object>.<alarm>' provider reference; area preserved in Category. +2 mapper tests; DCL suite 158 green. Deployed + verified live on wonder.
dohertj2 added 1 commit 2026-06-16 19:57:58 -04:00
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).
dohertj2 merged commit 9b78e6071d into main 2026-06-16 19:58:07 -04:00
Sign in to join this conversation.
No Reviewers
No Label
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: dohertj2/ScadaBridge#4