From 9f55acef38c9ff46e55e4b3cef312e71dadefaa0 Mon Sep 17 00:00:00 2001 From: Pratik Mankawde <3397372+pratikmankawde@users.noreply.github.com> Date: Thu, 3 Sep 2026 20:19:27 +0100 Subject: [PATCH] docs(telemetry): name the label the consensus dashboard actually filters on The Consensus Health template-variable table documented $node as resolving via exported_instance. That dashboard defines $node as label_values(target_info, service_instance_id) and its panels filter on service_instance_id; exported_instance appears in it zero times. exported_instance is a real label, but it belongs to the StatsD boards shipped alongside, where Prometheus renames a scraped instance label that collides with the target's own. Documenting it against an OTel dashboard pointed readers at the wrong pipeline's label. --- OpenTelemetryPlan/09-data-collection-reference.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/OpenTelemetryPlan/09-data-collection-reference.md b/OpenTelemetryPlan/09-data-collection-reference.md index ee97467ba2..e1010a0242 100644 --- a/OpenTelemetryPlan/09-data-collection-reference.md +++ b/OpenTelemetryPlan/09-data-collection-reference.md @@ -781,7 +781,7 @@ The Consensus Health dashboard includes 5 close-time panels added in Phase 4: | Variable | Source Attribute | Description | | ------------------------- | ------------------------------------- | ------------------------------------------------------------------------ | -| `$node` | `exported_instance` | Filter by xrpld node instance | +| `$node` | `service_instance_id` | Filter by xrpld node instance | | `$service_name` | `service_name` | Filter by service (`service.name`, e.g. `xrpld`) | | `$deployment_environment` | `deployment_environment` | Filter by deployment tier (`local` / `test` / `ci` / `prod`) | | `$xrpl_network_type` | `xrpl_network_type` | Filter by network (`mainnet` / `testnet` / `devnet`) |