Skip to content

Commit a875e72

Browse files
docs: Clarify approx_topk is an experimental feature (backport release-3.3.x) (#16994)
Co-authored-by: Charlie Burnett <CharlieBurnett@users.noreply.github.com>
1 parent 00e80d9 commit a875e72

File tree

1 file changed

+4
-0
lines changed

1 file changed

+4
-0
lines changed

‎docs/sources/query/metric_queries.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -156,6 +156,10 @@ Examples:
156156
157157
## Probabilistic aggregation
158158
159+
{{< admonition type="note" >}}
160+
Probabilistic aggregation is an experimental feature. Engineering and on-call support is not available. Documentation is either limited or not provided outside of code comments. No SLA is provided. To use this feature, set `limits_config.shard_aggregations:approx_topk` in your [Loki configuration](https://grafana.com/docs/loki/<LOKI_VERSION>/configure/#limits_config). To enable this feature in Grafana Cloud, contact Grafana Support.
161+
{{< /admonition >}}
162+
159163
LogQL's `approx_topk` function provides a probabilistic approximation of `topk`. It is a drop-in replacement for `topk` that is great for when `topk` queries time out or hit the maximum series limit. This tends to happen when the list of values that you're sorting through in order to find the most frequent values is very large. `approx_topk` is also great in cases where a faster, approximate answer is preferred to a slower, more accurate one.
160164
161165
The function is of the form:

0 commit comments

Comments
 (0)