From 1308e28d8bad161d2f37f91b4699b47eb7498a1b Mon Sep 17 00:00:00 2001 From: Todd Treece <360020+toddtreece@users.noreply.github.com> Date: Thu, 26 May 2022 09:32:04 -0400 Subject: [PATCH] Docs: Document Prometheus NaN breaking change (#49688) --- docs/sources/whatsnew/whats-new-in-v9-0.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/sources/whatsnew/whats-new-in-v9-0.md b/docs/sources/whatsnew/whats-new-in-v9-0.md index b8de9fb3149..b14ab428565 100644 --- a/docs/sources/whatsnew/whats-new-in-v9-0.md +++ b/docs/sources/whatsnew/whats-new-in-v9-0.md @@ -197,6 +197,10 @@ Support for Elasticsearch versions that are after their end of life ( based on h In the Elasticsearch data source, browser access mode was deprecated in grafana 7.4.0 and removed in 9.0.0. If you used this mode, please switch to server access mode on the data source configuration page. +### Prometheus: NaN values representation changed in numeric data + +In the Prometheus data source, when grafana receives numeric data from Prometheus, it may contain NaN (not a number) values. For consistency and performance reasons we changed how we represent such values in Grafana. In previous versions, the behavior was different between alerting queries and other queries (like dashboard queries or explore queries). Alerting queries kept NaN values unchanged, but other queries converted these values to “null”. Starting with grafana 9.0.0, we will always keep NaN values unchanged for all queries. +