From 870b4708033ec40f387e43fceed2647ae481fc65 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Lukas=20Juozas=20Janu=C5=A1aitis?= Date: Mon, 3 Mar 2025 16:45:50 +0200 Subject: [PATCH] docs(migration): clarify on content-type headers MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: Lukas Juozas JanuĊĦaitis --- docs/migration.md | 11 +++++++++-- 1 file changed, 9 insertions(+), 2 deletions(-) diff --git a/docs/migration.md b/docs/migration.md index 44cd466b3d..77fa5df682 100644 --- a/docs/migration.md +++ b/docs/migration.md @@ -129,8 +129,15 @@ If a scrape target is not providing the correct Content-Type header the fallback protocol can be specified using the `fallback_scrape_protocol` parameter. See [Prometheus scrape_config documentation.](https://prometheus.io/docs/prometheus/latest/configuration/configuration/#scrape_config) -This is a breaking change as scrapes that may have succeeded with Prometheus v2 -may now fail if this fallback protocol is not specified. +This is a **breaking change** as scrapes that may have succeeded with Prometheus v2 +may now fail if this fallback protocol is not specified. Make sure your scrape +endpoints respond with one of the supported Content-type headers: + +- `application/vnd.google.protobuf;proto=io.prometheus.client.MetricFamily;encoding=delimited` +- `text/plain;version=0.0.4` +- `text/plain;version=1.0.0` +- `application/openmetrics-text;version=0.0.1` +- `application/openmetrics-text;version=1.0.0` ## Miscellaneous