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 running behind a reverse proxy or ingress
proxy, or configured with web.config to serve TLS?)
On Tuesday, 19 July 2022 at 06:13:38 UTC+1 [email protected] wrote:
> I am trying to configure the prometheus federation, but the target is not
> up and the only error I can see is `read: connection reset by peer`
>
> The scrape_config I've added is as follows:
>
> - job_name: federate
> scrape_interval: 30s
> scrape_timeout: 15s
> scheme: https
> honor_labels: true
> metrics_path: "/federate"
> params:
> match[]:
> - '{job="jobname"}'
> static_configs:
> - targets:
> - another_prom_server
>
> But if I use `curl` command from this central prometheus server, it works
> and can return the metrics correctly.
>
> another_prom_server is the one deployed by kube-prometheus-stack helm
> chart. Not sure what is the issue here? Could anyone help advise, thanks!
>
--
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/29251b7e-d75e-46d9-b2a7-0cfd07010040n%40googlegroups.com.
