From d773b14d09533c91a61bfc29bb4ddc3c4a28afd6 Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" <41898282+github-actions[bot]@users.noreply.github.com> Date: Fri, 25 Oct 2024 15:49:17 +0000 Subject: [PATCH] [release-v2.6] Add flush_to_storage config doc (#4237) (cherry picked from commit 12115aa7d971c817378e97db86dabaf3dcd37c0d) Co-authored-by: Kim Nylander <104772500+knylander-grafana@users.noreply.github.com> --- docs/sources/tempo/operations/traceql-metrics.md | 2 ++ docs/sources/tempo/traceql/metrics-queries.md | 2 +- 2 files changed, 3 insertions(+), 1 deletion(-) diff --git a/docs/sources/tempo/operations/traceql-metrics.md b/docs/sources/tempo/operations/traceql-metrics.md index fd14b26a971..d8e156cbefd 100644 --- a/docs/sources/tempo/operations/traceql-metrics.md +++ b/docs/sources/tempo/operations/traceql-metrics.md @@ -80,6 +80,8 @@ metrics_generator: flush_to_storage: true ``` +Setting `flush_to_storage` to `true` ensures that metrics blocks are flushed to storage so TraceQL metrics queries against historical data. + For more information about overrides, refer to [Standard overrides](https://grafana.com/docs/tempo//configuration/#standard-overrides). ## Evaluate query timeouts diff --git a/docs/sources/tempo/traceql/metrics-queries.md b/docs/sources/tempo/traceql/metrics-queries.md index 9d7f396f7b5..65f1d7fabf8 100644 --- a/docs/sources/tempo/traceql/metrics-queries.md +++ b/docs/sources/tempo/traceql/metrics-queries.md @@ -15,7 +15,7 @@ keywords: TraceQL metrics is an experimental feature in Grafana Tempo that creates metrics from traces. Metric queries extend trace queries by applying a function to trace query results. -This powerful feature allows for adhoc aggregation of any existing TraceQL query by any dimension available in your traces, much in the same way that LogQL metric queries create metrics from logs. +This powerful feature allows for ad hoc aggregation of any existing TraceQL query by any dimension available in your traces, much in the same way that LogQL metric queries create metrics from logs. Traces are a unique observability signal that contain causal relationships between the components in your system. Do you want to know how many database calls across all systems are downstream of your application?