I have set a silent-drop on c.c.c.42, then after a while prometheus
falls back on a different ip, on which it is allowed to get the metrics.
But strange thing is that if it successfully polls on this ip. It stop
and tries the bad ip again.
-----Original Message-----
To: prometheus-users
Subject: [prometheus-users] Multiple ip addresses returned via srv,
prometheus only trying one
My prometheus is stuck trying to get metrics from the last ip address
c.c.c.42, which is not reachable for prometheus.
My dns is configured like this
# dig srv +short _metrics._haproxy.dev._tcp.marathon.mesos
0 1 31912 haproxy.dev-e5dqo-s3.marathon.mesos.
# dig +short haproxy.dev-e5dqo-s3.marathon.mesos.
a.a.a.234
b.b.b.53
c.c.c.42
I have this haproxy config:
- job_name: 'haproxy'
scheme: http
dns_sd_configs:
- names:
- '_metrics._haproxy.dev._tcp.marathon.mesos'
Is there something I can configure so prometheus is trying the other ip
addresses?
--
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/%22H000007100178908.1597327404.sx.f1-outsourcing.eu*%22%40MHS.
--
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/%22H000007100178910.1597330245.sx.f1-outsourcing.eu*%22%40MHS.
