From 46d7718a52ff33accb15dc0501736fbdb6833cab Mon Sep 17 00:00:00 2001 From: Teknium <127238744+teknium1@users.noreply.github.com> Date: Fri, 9 Oct 2026 14:25:50 -0700 Subject: [PATCH] docs(telemetry): v4 takes additive values in place after its stable release Owner ruling for gateway_pause_failed: extend package schema v4 in place (additive only; ingest validates the envelope and every shape already sent stays valid) instead of bumping to v5. The two sentences that said v4 was extended only while canary-only now say so. --- website/docs/developer-guide/relay-shared-metrics.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/website/docs/developer-guide/relay-shared-metrics.md b/website/docs/developer-guide/relay-shared-metrics.md index 66fa807001..240a909630 100644 --- a/website/docs/developer-guide/relay-shared-metrics.md +++ b/website/docs/developer-guide/relay-shared-metrics.md @@ -500,8 +500,8 @@ database and the count is not reported. #### Install and update failure reasons -Since package schema v4 (extended in place while v4 was canary-only), two existing metrics say why -they failed. Rows recorded before the change keep their old field set and still package. +Since package schema v4 (extended in place; additive only, so every shape already sent stays valid), +two existing metrics say why they failed. Rows recorded before the change keep their old field set and still package. | Metric | Dimensions added | Question it answers | |---|---|---| @@ -537,7 +537,7 @@ locally for 30 days. Pending package rows and counters with unexported deltas are never pruned. Package schemas v1, v2 and v3 remain unchanged for existing outbox files. New packages use v4, which adds `failure_class` to `hermes.compression.count` and -`hermes.memory.op.count` and still accepts their v3 field sets (and, extended in place, +`hermes.memory.op.count` and still accepts their v3 field sets (and, extended in place with additive values only, also after v4 shipped in a stable release, `failure_class` on `hermes.extension.install.count` / `hermes.update.run` plus `registry` on the former, still accepting their earlier v4 field sets), as v3 accepted the v2 field sets of `hermes.model_route.count`, `hermes.tool_call.count` and the task