mirror of
https://github.com/XRPLF/rippled.git
synced 2026-08-21 22:30:57 +00:00
370130a9f9
The two key-job latency panels on node-health declared milliseconds while querying `job_running_us` / `job_queued_us`, which record microseconds. Every reading was a thousand times too large: the p95 for acceptLedger, 241495us, rendered as "241 sec" instead of 241ms. job-queue.json already read the same metrics as microseconds, so the two dashboards disagreed by 1000x on identical data. Also replace the generic `ops`, `cps` and `cpm` units, which Grafana renders as the literal "ops/s", "counts/s" and "counts/min", with custom-suffix units naming what each panel counts -- jobs, ledgers, validations, lookups. The per-minute panels already scale correctly in their queries; only the noun was missing. Normalise the micro sign to U+00B5 throughout. Four axis labels used the visually identical Greek mu, U+03BC, while every unit field used the micro sign. Ledger Close Rate plots ledgers closed beside ledger fetches, which one unit cannot describe; give the fetches series its own unit on a right-hand axis. Drop two field overrides on NodeStore Read Latency that restated the panel unit as a custom suffix -- a suffix is appended verbatim, so it would have suppressed magnitude scaling and left large values unreadable, the same defect fixed above. Queries are unchanged apart from the transaction path piechart, which moves from rate() to increase(): a per-slice "per second" reading is not a share of a total. Alongside, widen the Complete Ledger Ranges table to full width, hoist the stat panels above the fold, and bring the touched panels up to the tooltip and null-spanning guidelines.