docs(telemetry): Telemetry(.Serilog) 0.2.0 published; ScadaBridge on AddZbSerilog (ScadaBridge#94, scadaproj#12)
Both packages published to the feed 2026-11-12, packed from 01c6dc1 (the 0.2.0
code + corrected RepositoryUrl, before the 0.2.1 commit); SHA256 of the feed
download matches the local pack. ScadaBridge switched to AddZbSerilog with the
MinimumLevelGovernor + ConfigureLogger hooks (main 2d2e9f35) and deleted its
LoggerConfigurationFactory. Updates the Observability row, Telemetry/CLAUDE.md
and components/observability/GAPS.md.
Claude-Session: https://claude.ai/code/session_01GT67ACmpMR7b9LGRPLijMi
This commit is contained in:
@@ -11,9 +11,9 @@ reach the shared `ZB.MOM.WW.Telemetry` library. Status legend: ⛔ gap · 🟡 p
|
||||
> **✅ ADOPTED — verified 2026-07-18.** `ZB.MOM.WW.Telemetry` + `.Serilog` `0.1.0` are on the Gitea
|
||||
> feed and **all four apps reference both and call `AddZbTelemetry`** (Resource + standard
|
||||
> instrumentation + Prometheus `/metrics`). Logging: OtOpcUa, MxAccessGateway and **HistorianGateway**
|
||||
> (a fourth consumer this file predates) use `AddZbSerilog`; ScadaBridge deliberately keeps its own
|
||||
> `LoggerConfigurationFactory` for min-level governance and adds only the shared `TraceContextEnricher`
|
||||
> — that split is by design, not a gap. Library suite: **34 tests**, green 2026-07-18.
|
||||
> (a fourth consumer this file predates) use `AddZbSerilog`; **ScadaBridge joined them 2026-11-12**
|
||||
> (ScadaBridge#94, `main` `2d2e9f35`) on Telemetry(.Serilog) **`0.2.0`** — published 2026-11-12 — via its
|
||||
> `MinimumLevelGovernor` + `ConfigureLogger` hooks; `LoggerConfigurationFactory` is deleted. Library suite: **34 tests**, green 2026-07-18.
|
||||
>
|
||||
> **The `⛔ not set` divergence tables below are the pre-adoption 2026-06-01 snapshot** — the §1
|
||||
> Resource-attribute gaps they describe are what `AddZbTelemetry` closed. Read them as the
|
||||
@@ -218,7 +218,7 @@ sister apps in one pass, behaviour-preserving. Each adoption landed on a per-rep
|
||||
| Repo | `AddZbTelemetry` (Resource + std instrumentation + Prometheus) | `/metrics` | Logging | Meter (unchanged) |
|
||||
|---|---|---|---|---|
|
||||
| **OtOpcUa** | ✅ replaced hand-rolled `ObservabilityExtensions` | ✅ `/metrics` (path unchanged) | ✅ `AddZbSerilog` (sinks moved to `appsettings`; `LogContextEnricher` kept) | `ZB.MOM.WW.OtOpcUa` |
|
||||
| **ScadaBridge** | ✅ added in `BindSharedOptions` (both Central + Site roots) | ✅ Central; mapped on Site too (see follow-on) | ⚠️ **kept `LoggerConfigurationFactory`** + added shared `TraceContextEnricher` — did **not** adopt `AddZbSerilog` | (none yet; #9) |
|
||||
| **ScadaBridge** | ✅ added in `BindSharedOptions` (both Central + Site roots) | ✅ Central; mapped on Site too (see follow-on) | ✅ `AddZbSerilog` (0.2.0, 2026-11-12, ScadaBridge#94) with `MinimumLevelGovernor` + `ConfigureLogger`; `LoggerConfigurationFactory` deleted | (none yet; #9) |
|
||||
| **MxAccessGateway** | ✅ exports existing `GatewayMetrics` | ✅ new `/metrics` | ✅ MEL→`AddZbSerilog`; `GatewayLogRedactor` exposed via `ILogRedactor` seam (`GatewayLogRedactorSeam`); `GatewayLogScope`/middleware kept as-is | `MxGateway.Server` (name + `ms` units unchanged) |
|
||||
|
||||
### Accepted scope decisions (deviations from the original backlog)
|
||||
@@ -230,10 +230,10 @@ sister apps in one pass, behaviour-preserving. Each adoption landed on a per-rep
|
||||
precedence and silently drop the knob. So ScadaBridge keeps the factory and only **adds the shared
|
||||
`TraceContextEnricher`** to it — gaining trace↔log correlation without regressing the contract. Full
|
||||
`AddZbSerilog` adoption for ScadaBridge would first require teaching the shared bootstrap to accept a
|
||||
caller-supplied minimum-level governance hook (→ #12). **Library half landed in Telemetry `0.2.0` (unpublished, 2026-11-09):** `AddZbSerilog(builder,
|
||||
caller-supplied minimum-level governance hook (→ #12). **Library half landed in Telemetry `0.2.0` (built 2026-11-09, published 2026-11-12):** `AddZbSerilog(builder,
|
||||
configure, s => { s.MinimumLevelGovernor = …; s.ConfigureLogger = …; })` — the governor runs after
|
||||
`ReadFrom.Configuration`, `ConfigureLogger` carries the standby `active-node` filter. ScadaBridge's switch is
|
||||
the remaining follow-on in that repo.
|
||||
`ReadFrom.Configuration`, `ConfigureLogger` carries the standby `active-node` filter. **ScadaBridge switched
|
||||
2026-11-12 (ScadaBridge#94, `main` `2d2e9f35`)** — this deviation is closed.
|
||||
- **MxGateway keeps `GatewayLogScope` + request-logging middleware as-is.** The Serilog MEL provider
|
||||
captures MEL `BeginScope` dictionaries as structured properties, so the scope/correlation code keeps
|
||||
producing the same properties under Serilog. Only the provider swap + the `ILogRedactor` adapter were
|
||||
|
||||
Reference in New Issue
Block a user