Pratik Mankawde 24f60ab1d4 feat(telemetry): make consensus panels show real consensus timing and rounds ...

The consensus duration panels plotted span wall-clock
(traces_span_metrics_duration_milliseconds), which is ~3-8 ms of
instrumentation overhead, not the real consensus time (~3000 ms). And
the close-time value panels plotted an ever-rising absolute epoch line.
Rework them to answer the actual operational questions, all from
attributes that already exist on the consensus spans:

- Time to Reach Consensus (p50/p95) and Average Time to Reach Consensus:
  round_time_ms on consensus.accept — the wall-clock to agree a ledger.
- Consensus Rounds per Ledger (Establish Count): avg and max of
  establish_count on consensus.establish — how many proposal rounds it
  took to converge (1 = first proposal).
- Previous Round Time per Ledger: previous_round_time_ms on
  consensus.round.

Reorder the dashboard into an investigation flow: health/throughput ->
time-to-consensus and rounds -> ledger close/apply timing -> close-time
detail -> failures/mode/mismatch. Assign stable sequential panel ids.

Verified each query returns data via the Grafana datasource proxy
(p95 ~4096 ms, avg ~2825 ms, rounds ~2).

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

2026-06-05 19:35:34 +01:00

..

cpp_files

ci: Add clang to nix images (#7308)

2026-05-26 15:45:33 +00:00

telemetry

feat(telemetry): make consensus panels show real consensus timing and rounds

2026-06-05 19:35:34 +01:00

check-sanitizers.sh

style: Use shfmt instead of bashate (#7326)

2026-05-26 18:28:23 +00:00

nix.Dockerfile

ci: Add clang to nix images (#7308)

2026-05-26 15:45:33 +00:00