cizara commented on issue #555: URL: https://github.com/apache/pulsar-helm-chart/issues/555#issuecomment-2553632946
Hi, I'm experiencing the same behavior. Seems to be related to Prometheus v3 being rolled out in latest `kube-prometheus-stack`, as it has a breaking change to fail to scrape if Content-Type is not valid or missing, as stated in https://prometheus.io/docs/prometheus/3.0/migration/#scrape-protocols: > 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. The Content-Type seems to be missing: ```bash pulsar-bookie-0:/pulsar$ curl -X GET -v -I http://127.0.0.1:8000/metrics * Trying 127.0.0.1:8000... * Connected to 127.0.0.1 (127.0.0.1) port 8000 * using HTTP/1.x > GET /metrics HTTP/1.1 > Host: 127.0.0.1:8000 > User-Agent: curl/8.11.0 > Accept: */* > * Request completely sent off < HTTP/1.1 200 OK HTTP/1.1 200 OK < content-length: 264341 content-length: 264341 < * shutting down connection #0 ``` -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
