Pratik Mankawde 283218896b fix(telemetry): use avg not quantile for close-time value panels ...

The Raw Proposals and Effective/Quantized panels showed wrong values
(e.g. 759M, 852M, even 0) against a true value of ~834M. Cause:
quantile_over_time bucketizes into an exponential histogram tuned for
duration distributions, so it cannot represent large absolute integers
(Ripple-epoch seconds) accurately.

Switch both panels to avg_over_time, which returns the correct value
(verified ~833,996,7xx matching the raw span attribute). Average is also
the semantically right aggregation here: close time is a single agreed
value per consensus round, not a latency distribution, so a median was
never meaningful.

Set the unit to none rather than seconds: the value is Ripple-epoch
seconds (Unix = value + 946684800) and TraceQL metrics cannot do the
offset arithmetic in-query, so a duration unit would misrender it.
Clarify in the description that the absolute level tracks wall-clock and
the useful signal is per-node spread / raw-vs-effective gap.

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

2026-06-05 18:48:31 +01:00

..

cpp_files

ci: Add clang to nix images (#7308)

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

telemetry

fix(telemetry): use avg not quantile for close-time value panels

2026-06-05 18:48:31 +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