From 20a5f2cd6e2a14a3556d85575504ba202957b912 Mon Sep 17 00:00:00 2001 From: javiermolinar Date: Thu, 31 Oct 2024 08:42:04 +0100 Subject: [PATCH] correct traceql metrics documentation --- docs/sources/tempo/traceql/metrics-queries/_index.md | 2 +- docs/sources/tempo/traceql/metrics-queries/functions.md | 8 ++++---- 2 files changed, 5 insertions(+), 5 deletions(-) diff --git a/docs/sources/tempo/traceql/metrics-queries/_index.md b/docs/sources/tempo/traceql/metrics-queries/_index.md index 9f4c2a2fe77..82368e83a66 100644 --- a/docs/sources/tempo/traceql/metrics-queries/_index.md +++ b/docs/sources/tempo/traceql/metrics-queries/_index.md @@ -60,7 +60,7 @@ Refer to [Solve problems using metrics queries](./solve-problems-metrics-queries ### Functions -TraceQL metrics queries currently include the following functions for aggregating over groups of spans: `rate`, `count_over_time`, `quantile_over_time`, `histogram_over_time`, and `compare`. +TraceQL metrics queries currently include the following functions for aggregating over groups of spans: `rate`, `count_over_time`,`min_over_tim`,`max_over_time`, `quantile_over_time`, `histogram_over_time`, and `compare`. These functions can be added as an operator at the end of any TraceQL query. For detailed information and example queries for each function, refer to [TraceQL metrics functions](./functions). diff --git a/docs/sources/tempo/traceql/metrics-queries/functions.md b/docs/sources/tempo/traceql/metrics-queries/functions.md index 2c20a34674f..9302f513baf 100644 --- a/docs/sources/tempo/traceql/metrics-queries/functions.md +++ b/docs/sources/tempo/traceql/metrics-queries/functions.md @@ -12,7 +12,7 @@ keywords: -TraceQL supports `rate`, `count_over_time`, `quantile_over_time`, `histogram_over_time`, and `compare` functions. +TraceQL supports `rate`, `count_over_time`,`min_over_tim`,`max_over_time`, `quantile_over_time`, `histogram_over_time`, and `compare` functions. ## Available functions @@ -25,10 +25,10 @@ These functions can be added as an operator at the end of any TraceQL query. : Counts the number of matching spans per time interval (refer to the [`step` API parameter](https://grafana.com/docs/tempo//api_docs/#traceql-metrics)). `min_over_time` -: Returns the minimum value of matching spans values per time interval (see the `step` API parameter) +: Returns the minimum value for the specified attribute across all matching spans per time interval (refer to the [`step` API parameter](https://grafana.com/docs/tempo//api_docs/#traceql-metrics)). `max_over_time` -: Returns the minimum value for the specified attribute across all matching spans per time interval (refer to the [`step` API parameter](https://grafana.com/docs/tempo//api_docs/#traceql-metrics)). +: Returns the maximum value for the specified attribute across all matching spans per time interval (refer to the [`step` API parameter](https://grafana.com/docs/tempo//api_docs/#traceql-metrics)). `quantile_over_time` : The quantile of the values in the specified interval @@ -101,7 +101,7 @@ For example, you could choose to calculate the minimum duration of a group of sp The time interval that the minimum is computed over is set by the `step` parameter. The `max_over_time()` let you aggregate numerical values by computing the maximum value of them, such as the all important span duration. -The time interval that the maximum is computer over is set by the `step` parameter. +The time interval that the maximum is computed over is set by the `step` parameter. For more information, refer to the [`step` API parameter](https://grafana.com/docs/tempo//api_docs/#traceql-metrics).