From ac525462ce996caeceb828ab56072d23af1eac00 Mon Sep 17 00:00:00 2001 From: Aliaksandr Valialkin Date: Mon, 12 Oct 2020 13:25:17 +0300 Subject: [PATCH] docs/MetricsQL.md: mention that VictoriaMetrics keeps metric names after applying functions which dont change time series meaning --- docs/MetricsQL.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/MetricsQL.md b/docs/MetricsQL.md index dad59993d6..b21637f881 100644 --- a/docs/MetricsQL.md +++ b/docs/MetricsQL.md @@ -15,6 +15,8 @@ The following functionality is implemented differently in MetricsQL comparing to * MetricsQL removes all the `NaN` values from the output, so some queries like `(-1)^0.5` return empty results in VictoriaMetrics, while returning a series of `NaN` values in Prometheus. Note that Grafana doesn't draw any lines or dots for `NaN` values, so usually the end result looks the same for both VictoriaMetrics and Prometheus. +* MetricsQL keeps metric names after applying functions, which don't change the meaining of the original time series. For example, `min_over_time(foo)` or `round(foo)` + leave `foo` metric name in the result. See [this issue](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/674) for details. Other PromQL functionality should work the same in MetricsQL. [File an issue](https://github.com/VictoriaMetrics/VictoriaMetrics/issues) if you notice discrepancies between PromQL and MetricsQL results other than mentioned above.