Prometheus from version 3 expects a Content-Type header
Source
Prometheus v3 is more strict concerning the Content-Type header received when scraping. Prometheus v2 would default to the standard Prometheus text protocol if the target being scraped did not specify a Content-Type header or if the header was unparsable or unrecognised. This could lead to incorrect data being parsed in the scrape. Prometheus v3 will now fail the scrape in such cases.
log:
time=2025-01-28T00:59:20.293Z level=ERROR source=scrape.go:1590 msg="Failed to determine correct type of scrape target." component="scrape manager" scrape_pool=serviceMonitor/bee-testnet/bee-3/1 target=http://10.233.127.159:8633/metrics content_type="" fallback_media_type="" err="non-compliant scrape target sending blank Content-Type and no fallback_scrape_protocol specified for target"
Prometheus from version 3 expects a Content-Type header
Source
log: