From f3b0af852786974469f0c82234ee2a219b8d36f0 Mon Sep 17 00:00:00 2001
From: Pratik Mankawde <3397372+pratikmankawde@users.noreply.github.com>
Date: Fri, 4 Sep 2026 12:39:53 +0100
Subject: [PATCH] docs(telemetry): name the renamed close-time attr in the
 acquire comment

The cardinality note points at the close-time dimension rule above it, so
it needs the emitted key name.
---
 docker/telemetry/otel-collector-config.yaml | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/docker/telemetry/otel-collector-config.yaml b/docker/telemetry/otel-collector-config.yaml
index e98f9cdc51..87b365c83c 100644
--- a/docker/telemetry/otel-collector-config.yaml
+++ b/docker/telemetry/otel-collector-config.yaml
@@ -220,9 +220,10 @@ connectors:
       # Deliberately NOT promoted: ledger_hash and ledger_seq. Both are
       # per-ledger values, so a dimension on either would mint a new metric
       # series for every ledger acquired -- the same unbounded-cardinality rule
-      # already applied to close_time above. They stay span-only and are
-      # searchable in Tempo instead (see the parquet_dedicated_columns block in
-      # tempo.yaml), which gives per-ledger lookup with no metric series.
+      # already applied to close_time_ripple_epoch_s above. They stay span-only
+      # and are searchable in Tempo instead (see the parquet_dedicated_columns
+      # block in tempo.yaml), which gives per-ledger lookup with no metric
+      # series.
       - name: outcome
       - name: acquire_reason
       # Sync-diagnostic span dimensions. Each is a small, closed value