From 102f34da41f9a3daa4708cb94e8e817fac96cf5e Mon Sep 17 00:00:00 2001 From: Arve Knudsen Date: Mon, 17 Nov 2025 17:30:41 +0100 Subject: [PATCH] Update blog/posts/2025-11-14-introducing-info-function.md Co-authored-by: Owen Williams Signed-off-by: Arve Knudsen --- blog/posts/2025-11-14-introducing-info-function.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/blog/posts/2025-11-14-introducing-info-function.md b/blog/posts/2025-11-14-introducing-info-function.md index bf895dac..169b72bd 100644 --- a/blog/posts/2025-11-14-introducing-info-function.md +++ b/blog/posts/2025-11-14-introducing-info-function.md @@ -10,7 +10,7 @@ Traditionally, complex PromQL join syntax is required in Prometheus to add even The new, still experimental `info()` function, promises a simpler way, making label enrichment as simple as wrapping your query in a single function call. In Prometheus 3.0, we introduced the [`info()`](https://prometheus.io/docs/prometheus/latest/querying/functions/#info) function, a powerful new way to enrich your time series with labels from info metrics. -`info` doesn't only suffer simpler syntax however. +`info` doesn't only offer a simpler syntax however. It also solves a subtle yet critical problem that has plagued join queries for years: The "churn problem" that causes queries to fail when "non-identifying" info metric labels change. Identifying labels here in practice means those that are joined on.