Newer versions of Prometheus are compiled with newer versions of go:
https://stackoverflow.com/questions/72046302/go-how-to-solve-transport-connection-broken-too-many-transfer-encodings-ch
It looks like your exporter has a bug and is setting multiple
Transfer-Encoding headers, and newer versions of go reject this.
You should be able to demonstrate with curl:
curl -vfsS -o /dev/null http://192.168.113.125:8080/metrics # or
/metric; I wasn't sure if you had made a typo.
or with tcpdump:
tcpdump -i eth0 -nn -s0 -A host 192.168.113.125 and tcp port 8080
(Run the tcpdump command on the prometheus server while prometheus is
running and scraping. Change eth0 to your appropriate ethernet interface,
or use "lo" if the prometheus server itself is 192.168.113.125)
Then take the problem up with the author of the exporter you are using.
On Thursday, 15 June 2023 at 12:53:56 UTC+1 Rayala Rajashekar wrote:
> Hi All,
>
> Can some one help me on below Prometheus issue.
>
> we are using Prometheus standalone V2.19.2 and planning to upgrade it to
> latest version V2.43.0.
> We are getting below issue with latest version, as per my observation it
> working fine until V.20.0 getting same issue from V2..21.0 till latest
> version.
>
> *Get "http://192.168.113.125:8080/metric
> <http://192.168.113.125:8080/metric>*
>
> *s": net/http: HTTP/1. transport connecti on broken: too many transfer
> encodings: ["chunked" "chunked"]*
>
>
>
>
>
--
You received this message because you are subscribed to the Google Groups
"Prometheus Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/prometheus-users/34194122-bc96-43bb-8774-646b2fbf9aeen%40googlegroups.com.
