docs(migration): clarify on content-type headers

Signed-off-by: Lukas Juozas Janušaitis <lukas.janusaitis@hostinger.com>
This commit is contained in:
Lukas Juozas Janušaitis 2025-03-03 16:45:50 +02:00
parent 2ef8706c27
commit 870b470803

View file

@ -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` 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) 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 This is a **breaking change** as scrapes that may have succeeded with Prometheus v2
may now fail if this fallback protocol is not specified. 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 ## Miscellaneous