mirror of
https://github.com/XRPLF/rippled.git
synced 2026-08-21 14:20:56 +00:00
2095a3d2f1
The four job-latency panels on node-health declared milliseconds while querying `job_running_us` / `job_queued_us`, which record microseconds (MetricsRegistry records the raw value, and the instrument description says microseconds). Every reading was therefore a thousand times too large: the p95 for acceptLedger, 241495us, rendered as "241 sec" instead of 241ms. job-queue.json already read these same metrics as microseconds, so the two dashboards disagreed by 1000x on identical data. Switch node-health to microseconds to match. Also replace the generic `ops` and `cps` units, which Grafana renders as the literal "ops/s" and "counts/s", with custom-suffix units naming what each panel counts -- messages, fetches, calls, mismatches. Two panels plot more than one quantity on a single axis, which no single unit can describe. Give each series its own unit through field overrides: reads per second beside two queue depths on NuDB Read Pressure, and ledgers beside fetches on Ledger Close Rate, the latter on a right-hand axis. State Duration Rate plots a seconds-per-second time share, which can exceed 1.0 and so is not a percentage; label it as the ratio it is. The normalised share already exists as its own panel. Queries are unchanged; the values were already correct. Alongside, bring the touched panels up to the dashboard guidelines and hoist the stat panels above the fold.