feat(infra): shared dev OTel collector; OTLP proven end to end for all four apps (#13)
- infra/otel-collector/: zb-otel-collector (otelcol-contrib 0.162.0) on 10.100.0.35 — OTLP gRPC :4317 / HTTP :4318, debug + file exporters, Prometheus re-export :8889, health :13133; README runbook + otelsum.py summariser. Deployed. - components/observability/2026-11-12-otlp-end-to-end-evidence.md: metrics + traces received from OtOpcUa, HistorianGateway, ScadaBridge (Site) and MxAccessGateway; OtOpcUa Galaxy driver allowlist defect fixed in lmxopcua#892 (db86b996). - GAPS.md, current-state banners, index row, Telemetry CLAUDE.md: #13 closed; follow-ups #54 (wonder-tier collector), #55 (resource identity + logs over OTLP), ScadaBridge#133 (Central role). Telemetry 0.2.1 deliberately left unpublished (no lib change needed). Claude-Session: https://claude.ai/code/session_01GT67ACmpMR7b9LGRPLijMi
This commit is contained in:
@@ -22,7 +22,13 @@ reach the shared `ZB.MOM.WW.Telemetry` library. Status legend: ⛔ gap · 🟡 p
|
||||
> listener, OTLP opt-in wiring) were **all subsequently executed the same day** — see the
|
||||
> "Follow-ons — DONE 2026-06-01" table at the bottom of this file, which this banner previously
|
||||
> contradicted (reconciled 2026-08-07). Only the operational items under "Still open" there
|
||||
> (deploying an OTel collector → #13; further ScadaBridge instruments → ScadaBridge#81) remain.
|
||||
> (further ScadaBridge instruments → ScadaBridge#81; collector on the wonder tiers → #54) remain.
|
||||
>
|
||||
> **✅ OTLP PROVEN END TO END — 2026-11-12 (#13, closed).** Shared dev collector `zb-otel-collector`
|
||||
> on 10.100.0.35 ([`infra/otel-collector/`](../../infra/otel-collector/)); metrics **and** traces arrived
|
||||
> from OtOpcUa, HistorianGateway, ScadaBridge (Site) and MxAccessGateway. One defect fixed: OtOpcUa's
|
||||
> Galaxy driver meter/source were missing from the allowlists (lmxopcua#892). Evidence:
|
||||
> [`2026-11-12-otlp-end-to-end-evidence.md`](2026-11-12-otlp-end-to-end-evidence.md).
|
||||
|
||||
## Divergence vs spec
|
||||
|
||||
@@ -256,7 +262,12 @@ behaviour-preserving except the intentional, no-consumer-yet metric-shape change
|
||||
|
||||
**Still open (not code — operational/future):**
|
||||
|
||||
- **OTLP is opt-in but unexercised** (→ #13) until an OTel collector endpoint is deployed and the
|
||||
`<App>:Telemetry:Exporter=Otlp` + `:OtlpEndpoint` config is set. The wiring is in place; only a
|
||||
collector is missing.
|
||||
- ~~**OTLP is opt-in but unexercised** (→ #13)~~ — **DONE 2026-11-12**: exercised end to end against
|
||||
`zb-otel-collector` (10.100.0.35:4317) for all four apps (ScadaBridge Site role only; Central →
|
||||
ScadaBridge#133). See [`2026-11-12-otlp-end-to-end-evidence.md`](2026-11-12-otlp-end-to-end-evidence.md).
|
||||
- **No collector on the wonder tiers** (DEV vd03, QA vq03/vq04) — every deployed box is still
|
||||
Prometheus-only. → #54
|
||||
- **Resource identity + logs-over-OTLP gaps** found by #13: `service.version` absent on all four apps;
|
||||
`site.id`/`node.role` absent on OtOpcUa, MxAccessGateway, HistorianGateway; no app passes the exporter
|
||||
settings to `AddZbSerilog`, so logs never travel over OTLP. → #55
|
||||
- **Further ScadaBridge instruments** beyond the first 4 are additive future work (not blocking). → ScadaBridge#81
|
||||
|
||||
Reference in New Issue
Block a user