Pratik Mankawde 72642b5dc6 feat(telemetry): add tx apply latency panel by type and stage ...

The existing apply-pipeline panels show latency by stage (all types
combined) or by type (single span). Neither answers "for a given
transaction type, which stage dominates its latency". Add a p95 panel
grouped by both tx_type and stage, filterable via the $tx_type and
$stage variables. Both dimensions already exist in spanmetrics, so no
collector change is needed. Reflow the section so the full-width
failure panel sits below the new full-width panel.

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

2026-06-05 13:39:59 +01:00

..

cpp_files

ci: Add clang to nix images (#7308)

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

telemetry

feat(telemetry): add tx apply latency panel by type and stage

2026-06-05 13:39:59 +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