From 613b62ab535ec8dbb944e521267252656e7b86f7 Mon Sep 17 00:00:00 2001 From: George Krajcsovits Date: Mon, 29 Sep 2025 16:21:58 +0200 Subject: [PATCH] Apply suggestions from code review Co-authored-by: Julius Volz Co-authored-by: Arthur Silva Sens Signed-off-by: George Krajcsovits --- docs/feature_flags.md | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/docs/feature_flags.md b/docs/feature_flags.md index 20c398f7bb..5a398b115f 100644 --- a/docs/feature_flags.md +++ b/docs/feature_flags.md @@ -55,17 +55,17 @@ stable feature. Native histograms may be directly scraped from targets (see below). Prometheus can also convert classic histograms scraped from targets into native histograms -with custom buckets during scrape. Native histograms may be ingested on -Remote-Write 1.0, 2.0, OTLP. +with custom buckets during scrape. Native histograms may be ingested via +Remote-Write 1.0, 2.0, or OTLP. Native histograms are currently only supported in the traditional Prometheus -protobuf exposition format. This feature flag therefore also enables a the -protobuf parser by changing the default for the `scrape_protocols` scrape +protobuf exposition format. This feature flag therefore also enables the +protobuf parser by changing the default `scrape_protocols` scrape configuration parameter to `[ PrometheusProto, OpenMetricsText1.0.0, -OpenMetricsText0.0.1, PrometheusText0.0.4 ]`. Which means that Prometheus -will try to negotiate the protobuf format first and if the target supports +OpenMetricsText0.0.1, PrometheusText0.0.4 ]`. This means that Prometheus +will try to negotiate the protobuf format first, and if the target supports the protobuf expostion format then _all_ metrics are ingested via protobuf -(i.e. not only native histograms). The protobuf format allows to expose +(i.e. not only native histograms). The protobuf format allows exposing classic and native histograms side by side. With this feature flag disabled, Prometheus will continue to parse the classic