From 7fdf82ae3a924e4654a0040243cfe4d3ad7d751a Mon Sep 17 00:00:00 2001 From: Arve Knudsen Date: Wed, 26 Jun 2024 17:03:13 -0700 Subject: [PATCH] Add two goals after feedback from Ying Signed-off-by: Arve Knudsen --- .../2024-04-10-native-support-for-info-metrics-metadata.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/proposals/2024-04-10-native-support-for-info-metrics-metadata.md b/proposals/2024-04-10-native-support-for-info-metrics-metadata.md index c52db62..75b374d 100644 --- a/proposals/2024-04-10-native-support-for-info-metrics-metadata.md +++ b/proposals/2024-04-10-native-support-for-info-metrics-metadata.md @@ -83,6 +83,8 @@ Goals and use cases for the solution as proposed in [How](#how): The collision can be resolved by constraining the labels via data label matchers. And of course, the user always has the option to go back to the original join syntax (or, even better, avoiding ingesting conflicting info metrics in the first place). * Simplify enriching of query results with info metric data (non-identifying) labels in PromQL, e.g. via a new function, based on aforementioned TSDB API. +* Ensure backwards compatibility with current Prometheus usage. +* Minimize potential conflicts with existing metric labels. ### Audience