H: correct the peer gauge gating in the docs Name otel.enabled plus otel.export_unit_metrics, and state that disabled peers have no series

This commit is contained in:
ari committed 2026-10-20 16:14:19 -04:00
1 parent 9c770b0576
commit 3f017725f8
1 file changed
+1 -1
+1 -1
View File
@@ -87,7 +87,7 @@ With peers enabled, MCP exposes `list_peers`, `get_peer` and the resource `peers
## OpenTelemetry
Four observable gauges, registered only with peers enabled and `otel.metrics.enabled`, read from the registry snapshot on each scrape: `peer.up` (attributes `peer.name`, `peer.check` = `server`/`api`), `peer.api.auth_ok` (`peer.name`), `peer.check.duration_seconds` (`peer.name`, `peer.check`) and `peer.last_change_timestamp_seconds` (`peer.name`, `peer.check`). No URL, version or token in attributes. A removed peer disappears from the next scrape. Outbound proxied requests carry a span named `peer.request` with `peer.name`, and the caller's `traceparent` is passed through, so a trace spans the fleet.
Four observable gauges, registered only with peers enabled and OTLP metrics on (`otel.enabled = true` together with `otel.export_unit_metrics = true`), read from the registry snapshot on each scrape: `peer.up` (attributes `peer.name`, `peer.check` = `server`/`api`), `peer.api.auth_ok` (`peer.name`), `peer.check.duration_seconds` (`peer.name`, `peer.check`) and `peer.last_change_timestamp_seconds` (`peer.name`, `peer.check`). No URL, version or token in attributes. A removed peer disappears from the next scrape, and a peer declared with `enabled = false` has no series at all: its checks never run, so a `0` would turn an intended switch-off into a false alarm. Outbound proxied requests carry a client span named `peer.request` with `peer.name`, and the caller's `traceparent` is passed through, so a trace spans the fleet.
## Credentials and threat model