oh, sorry, you mean all the metrics. It's about several seconds
real0m7.361s
user0m0.130s
sys0m0.999s
On Wednesday, July 20, 2022 at 1:03:36 AM UTC+10 Stuart Clark wrote:
> On 19/07/2022 14:51, Shi Yan wrote:
> > Thanks, Brian for helping look into it.
> >
> > Yes, in our setup,
Hi Stuart
The curl actually gets a response immediately, as we only need to get a
small set of metrics.
The curl command time is as follows
real0m0.077s
user0m0.016s
sys0m0.018s
On Wednesday, July 20, 2022 at 1:03:36 AM UTC+10 Stuart Clark wrote:
> On 19/07/2022 14:51, Shi Yan
Thanks Julien, but adding enable_http2: false doesn't help. Still same
error.
On Wednesday, July 20, 2022 at 12:20:50 AM UTC+10 Julien Pivotto wrote:
> Could you try adding http2_enable: false and see if there is an
> improvement?
>
> Le mar. 19 juil. 2022, 15:51, Shi Yan a écrit :
>
>>
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
Could you try adding http2_enable: false and see if there is an improvement?
Le mar. 19 juil. 2022, 15:51, Shi Yan a écrit :
> 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
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
Can you show the exact curl command line, with just the hostname replaced
with "example.com" ?
Try:
- targets:
- another_prom_server:9090
or
- targets:
- another_prom_server:443
or whatever is appropriate. (I note you set "scheme: https" - is that
correct? Is this prometheus
7 matches
Mail list logo
