[Telemetry] Deploy an OTel collector and exercise the OTLP export path end to end #13

New Issue

2026-11-06T15:24:43-05:00

dohertj2 commented

2026-11-06 15:24:43 -05:00

What: OTLP export is wired in all apps (<App>:Telemetry:Exporter=Otlp + :OtlpEndpoint, default Prometheus) but has never been exercised: no OpenTelemetry collector is deployed anywhere. Stand one up (local rig first, e.g. alongside the shared fixtures on 10.100.0.35) and prove export end to end — metrics plus OtOpcUa's spans, which are otherwise recorded with no exporter.

Why: until a collector exists, the OTLP path is untested code, and OtOpcUa's tracing remains effectively a no-op.

Source: components/observability/GAPS.md ("Still open (not code — operational/future)")

**What:** OTLP export is wired in all apps (`<App>:Telemetry:Exporter=Otlp` + `:OtlpEndpoint`, default Prometheus) but has never been exercised: no OpenTelemetry collector is deployed anywhere. Stand one up (local rig first, e.g. alongside the shared fixtures on 10.100.0.35) and prove export end to end — metrics plus OtOpcUa's spans, which are otherwise recorded with no exporter. **Why:** until a collector exists, the OTLP path is untested code, and OtOpcUa's tracing remains effectively a no-op. Source: `components/observability/GAPS.md` ("Still open (not code — operational/future)")

dohertj2 added the type:infra priority:p3 migrated labels 2026-11-06 15:24:43 -05:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: dohertj2/scadaproj#13