On 19/07/2022 14:51, Shi Yan wrote:
Thanks, Brian for helping look into it.

Yes, in our setup, `another_prom_server` is deployed on the k8s cluster and it is behind an F5 ingress proxy, which terminates the TLS protocol. So we use HTTPS here. And I've tried to add port 443 explicitly in the targets config, but the error is still the same.

msg="Scrape failed" err="Get \"https://example.com:443/federate?match%5B%5D=%7Bjob%3D%22jobname%22%7D\": read tcp x.x.x.x:58342->y.y.y.y:443: read: connection reset by peer"

While I can manually curl it with either
 > curl https://example.com
 <a href="/graph">Found</a>

or the one with the exact URL parameters from the error msg.
 > curl 'https://example.com:443/federate?match%5B%5D=%7Bjob%3D%22jobname%22%7D'
 .....# can get all the metrics correctly

How long does it take curl to respond with all the metrics?

Could it be that it takes a while and your load balancer is configured with a shorter timeout?

--
Stuart Clark

--
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/e0c701db-9c73-becb-c9a6-743f6c7384b3%40Jahingo.com.

Reply via email to