Galaxy driver spans and galaxy.events.* counters are never exported (missing from the OTel allowlists) #892
Reference in New Issue
Block a user
Delete Branch "%!s()"
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?
What:
AddOtOpcUaObservabilityhandsAddZbTelemetrystrict allowlists (ZbTelemetryOptions.Meters/.ActivitySources, no wildcard) that named onlyZB.MOM.WW.OtOpcUa(+ the LocalDb meter). The in-process Galaxy driver opens its spans (galaxy.subscribe_bulk,galaxy.unsubscribe_bulk,galaxy.stream_events,galaxy.write,galaxy.get_hierarchy) on ActivitySourceZB.MOM.WW.OtOpcUa.Driver.Galaxy, and its event pump recordsgalaxy.events.*counters (received / dispatched / dropped / replay_gaps / stream_attached / undecodable / early_*) on a Meter of the same name. Neither is registered, so all of them are silently dropped from/metricsand from OTLP.Found by: scadaproj#13 (first end-to-end OTLP exercise against a collector).
Fix: a public
GalaxyDriverTelemetryNamesin the Galaxy driver;ObservabilityExtensions.ObservedMeters/ObservedActivitySourcesname it; listener-side tests (span sampled / instrument enabled) with an unregistered-name negative control, mutation-checked.Fixed on master
db86b996(fix0b90379f):GalaxyDriverTelemetryNames+ObservabilityExtensions.ObservedMeters/ObservedActivitySources;ObservabilityAllowlistTests(listener-side, negative control, mutation-checked: dropping the Galaxy entries fails 3/8). Galaxy driver tests 584/584. Live OTLP proof of the host's other spans/metrics against the scadaproj#13 collector is in scadaprojcomponents/observability/2026-11-12-otlp-end-to-end-evidence.md; a livegalaxy.*span was not driven (needs a Galaxy driver deployment). Not deployed.