From 8dcd6f9b4a5ba4120c2635a23e2b70f38d2b8bb1 Mon Sep 17 00:00:00 2001 From: Pratik Mankawde <3397372+pratikmankawde@users.noreply.github.com> Date: Fri, 5 Jun 2026 19:19:55 +0100 Subject: [PATCH] fix(telemetry): raise TraceQL metrics max_duration to 168h TraceQL metrics queries default to a 3h max range (query_frontend.metrics.max_duration), so a dashboard set to a longer window failed with "range ... exceeds 3h0m0s". Add a query_frontend block raising it to 168h, matching the search max_duration, so the consensus close-time panels work at 6h/12h/24h ranges. Co-Authored-By: Claude Opus 4.8 --- docker/telemetry/tempo.yaml | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/docker/telemetry/tempo.yaml b/docker/telemetry/tempo.yaml index b2997bda53..24c092ca95 100644 --- a/docker/telemetry/tempo.yaml +++ b/docker/telemetry/tempo.yaml @@ -17,6 +17,14 @@ stream_over_http_enabled: true server: http_listen_port: 3200 +# Raise the TraceQL metrics query range limit. The default +# query_frontend.metrics.max_duration is 3h, so a dashboard set to a longer +# window (e.g. 6h/12h) fails with "range exceeds 3h0m0s". 168h matches the +# search max_duration and gives dashboards generous headroom. +query_frontend: + metrics: + max_duration: 168h + distributor: receivers: otlp: