Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.
Sign upFetch etcd members list using only one etcd endpoint/proxy address #2076
Comments
This comment has been minimized.
This comment has been minimized.
|
I don't think this is something we'd add to Prometheus, as like in #2036 you're proposing an SD mechanism that only discovers the cluster itself. In reality you should have some other service/machine database with this information which would make a better SD choice. |
brian-brazil
closed this
Oct 26, 2016
brian-brazil
added
the
kind/enhancement
label
Oct 26, 2016
This comment has been minimized.
This comment has been minimized.
lock
bot
commented
Mar 24, 2019
|
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
lock
bot
locked and limited conversation to collaborators
Mar 24, 2019
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
kayrus commentedOct 11, 2016
My goal is to configure only one or two etcd proxy/endpoints and Prometheus will get the whole cluster information from "https://172.16.0.1:2379/v2/members"
This will allow dynamically monitor etcd cluster independently on etcd members IP addresses.