fix(telemetry): make Tempo search filters dynamic

Change the six remaining `type: static` search filters in tempo.yaml to
`type: dynamic` so Grafana queries Tempo for available tag values instead
of requiring manual free-text entry. Aligns service-name, node-id,
network-type, span-name, span-status, and span-duration with the existing
node-version and network-id filters.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This commit is contained in:
Pratik Mankawde
2026-07-06 17:41:38 +01:00
parent 3789ac45e2
commit 0505ca35aa

View File

@@ -36,7 +36,7 @@ datasources:
tag: service.name
operator: "="
scope: resource
type: static
type: dynamic
# service.instance.id: unique node identifier — defaults to the
# node's public key (e.g., nHB1X37...). Distinguishes individual
# nodes in a multi-node cluster or network.
@@ -44,7 +44,7 @@ datasources:
tag: service.instance.id
operator: "="
scope: resource
type: static
type: dynamic
# service.version: xrpld build version (e.g., "2.4.0-b1").
# Filter traces from specific software releases.
- id: node-version
@@ -66,7 +66,7 @@ datasources:
tag: xrpl.network.type
operator: "="
scope: resource
type: static
type: dynamic
# --- Span intrinsic filters ---
# name: the span operation name (e.g., "rpc.command.server_info").
# Use to find traces for a specific RPC command or subsystem.
@@ -74,18 +74,18 @@ datasources:
tag: name
operator: "="
scope: intrinsic
type: static
type: dynamic
# status: span completion status ("ok", "error", "unset").
# Filter for failed operations to diagnose errors.
- id: span-status
tag: status
operator: "="
scope: intrinsic
type: static
type: dynamic
# duration: span wall-clock duration. Use with ">" operator
# to find slow operations (e.g., duration > 500ms).
- id: span-duration
tag: duration
operator: ">"
scope: intrinsic
type: static
type: dynamic