From 866ab77ececf6dfd4f6b17f4e111c525e1edba77 Mon Sep 17 00:00:00 2001
From: Pratik Mankawde <3397372+pratikmankawde@users.noreply.github.com>
Date: Tue, 15 Sep 2026 14:26:17 +0100
Subject: [PATCH] docs(telemetry): describe rotation measurements without
 naming the host

The runbook provenance paragraph named the internal AWS dev box and a
build hash and dates. State what was measured (one mainnet node, same
host and binary, differing only in store state) without the deployment
detail, which belongs in an internal runbook, not the public repo.
---
 docs/telemetry-runbook.md | 5 ++---
 1 file changed, 2 insertions(+), 3 deletions(-)

diff --git a/docs/telemetry-runbook.md b/docs/telemetry-runbook.md
index e1098a30b4..1274ee51df 100644
--- a/docs/telemetry-runbook.md
+++ b/docs/telemetry-runbook.md
@@ -3308,9 +3308,8 @@ increase(nodestore_state{metric="acquire_ledger_timeouts", service_instance_id=~
 
 #### Measured reference points
 
-**Provenance.** The two columns below are our own measurements: node2 on the AWS
-dev box, build `e3c2f8279a`, 2026-07-27/28, same host and same binary for both
-runs, differing only in the state of the store. Use them as the shape to compare
+**Provenance.** The two columns below are our own measurements: one mainnet node,
+same host and same binary for both runs, differing only in the state of the store. Use them as the shape to compare
 against, not as thresholds. The read figures below come from the `read_mean_us`
 gauge, the only read-latency signal exported; the "highest sample" row is the
 largest value that gauge reached over the run, not a read-latency percentile. The third dataset in this section — the 25-minute devnet stall and its