Files
rippled/docker/telemetry
Pratik Mankawde 8a6ecb8093 fix(telemetry): carry the work item through dashboard aggregations
Every aggregation that filtered on xrpl_work_item left it out of its
sum by() grouping, so PromQL dropped the label and the xrpl_ident legend
these panels build from it rendered without the work item. 217 clauses
across the touched boards.

Perf-iac gives each work item its own set of nodes, so service_instance_id
already separates the runs and the visible effect is the legend rather
than merged series. Four clauses are the exception and aggregate across
nodes, where the grouping does real work: Convergence, Lag Behind Network
Tip and Build Version now measure spread, lag and version distribution
within one work item instead of smearing two independent clusters
together. Lag Behind Network Tip also needed its on() join key extended to
match, or two coexisting work items would fail the query outright.

The five heatmap inner by (le) clauses are deliberately untouched: an
extra grouping label would superimpose several distributions.

Also in this change:
- transaction-overview gains per-type-per-stage rate and failure-rate
  panels, so all three requested dimensions exist rather than latency
  alone, and its stage-rate panel picks up the filters and legend its
  siblings already had.
- The acquire-duration panel splits by outcome. An aborted acquisition is
  open until the sweep reaps it, so mixing it into one percentile
  conflated fetch latency with time-to-abandon.
- Ledger Acquire Rate by Outcome gets the same Title Case value mapping as
  its neighbour, and node-health gains the $outcome variable the two
  panels now need.
2026-08-14 21:57:50 +01:00
..
2026-08-04 14:54:19 +01:00