prometheus/docs
1
0
Fork 0
mirror of https://github.com/prometheus/docs.git synced 2026-02-05 15:45:27 +01:00
Code Issues Releases Activity

Update blog/posts/2025-11-14-introducing-info-function.md

Browse Source 
Co-authored-by: Owen Williams <owen.williams@grafana.com>
Signed-off-by: Arve Knudsen <arve.knudsen@gmail.com>
This commit is contained in:
Arve Knudsen
2025-11-17 17:30:54 +01:00
committed by GitHub
parent 102f34da41
commit 933a579d8f
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
blog/posts/2025-11-14-introducing-info-function.md
View File

@@ -12,7 +12,7 @@ The new, still experimental `info()` function, promises a simpler way, making la
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 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.
In practice, "identifying labels" refers to those labels that the join is performed on.
Whether you're working with OpenTelemetry resource attributes, Kubernetes labels, or any other metadata, the `info()` function makes your PromQL queries cleaner, more reliable, and easier to understand.