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

docs(exposition): clarify required Content-type header for scrapes (#2772)

Browse Source 
Signed-off-by: Lukas Juozas Janušaitis <lukas.janusaitis@hostinger.com>
This commit is contained in:
Lukas Juozas Janusaitis
2025-12-03 15:02:09 +07:00
committed by GitHub
parent 9bd3a6832f
commit 61ce601d19
1 changed files with 12 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
docs/instrumenting/exposition_formats.md
View File

@@ -167,6 +167,18 @@ When such features are enabled either by feature flag
appropriate configuration option (`scrape_native_histograms: true`) then
Protobuf will be favored over other exposition formats.
## HTTP Content-Type requirements
Starting with Prometheus 3.0, scrape targets **must** return a valid `Content-Type` header for the metrics endpoint. If the `Content-Type` is missing, unparsable, or not a supported media type, **the scrape will fail**. See changes in [scrape protocols](https://prometheus.io/docs/prometheus/latest/migration/#scrape-protocols) in the migration guide for details.
See each of the exposition format sections for the accurate HTTP content types.
### ScrapeProtocols vs Content-Type
Prometheus scrape config offers scrape protocol negotiation based on the content-type using the [`scrape_protocols`](https://prometheus.io/docs/prometheus/latest/configuration/configuration/#scrape_config) config. For the Prometheus user convenience the scrape protocols are referenced by a unique name that maps to the concrete content-type. See [Protocol Headers](./content_negotiation.md#protocol-headers) for details.
However, the targets should expose metrics in the exposition format with the absolute, response content-type (e.g. `application/openmetrics-text;version=1.0.0`) and only one.
## Historical versions
For details on historical format versions, see the legacy