Pratik Mankawde 1120964e47 fix(telemetry): resolve sub-ms span buckets and unmatchable consensus_mode filter ...

Two live-verified dashboard defects found while auditing the devnet nodes.

Sub-millisecond spanmetrics buckets. The ladder started at 1ms, but most
xrpld spans are far below that: tx.preflight means ~0.012ms and tx.preclaim
~0.15ms. On the live nodes the first bucket held 13,761,009 of 13,761,419
tx.preflight samples (99.997%), so histogram_quantile pinned every p95/p99
at a constant 0.95ms and ~10 latency panels reported a boundary artifact
rather than a measurement. Adds 0.01/0.05/0.1/0.25/0.5ms ahead of 1ms in all
three bucket lists, which must stay identical or the connector misbuckets.

consensus_mode filter on spans that never carry the label. Only
consensus.round and consensus.ledger_close are stamped with consensus_mode
(verified against live series), so panels 1, 3, 12 and 14 -- which query
consensus.validation.send, consensus.proposal.send and
consensus.accept.apply -- blanked as soon as an operator picked any value
from the Consensus Mode dropdown. Drops the selector from those four; ids 2
and 11 keep it because their spans do carry it.

Note: existing histogram series retain the old le boundaries, so
span-latency panels show a discontinuity at collector restart.

2026-07-30 19:54:04 +01:00

..

telemetry

fix(telemetry): resolve sub-ms span buckets and unmatchable consensus_mode filter

2026-07-30 19:54:04 +01:00