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 up[Config] Switch whitelist of Consul services to blacklist #2402
Comments
This comment has been minimized.
This comment has been minimized.
|
You can use a drop relabel action to do this. |
brian-brazil
added
the
kind/question
label
Feb 7, 2017
This comment has been minimized.
This comment has been minimized.
|
Nice! That looks like some powerful stuff. (Just setting up the stack now so wasn't aware of this). Thanks man. |
This comment has been minimized.
This comment has been minimized.
|
You're welcome. |
brian-brazil
closed this
Feb 7, 2017
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.
yannispanousis commentedFeb 7, 2017
•
edited
What did you expect to see?
I'm integrating Prometheus with Consul for service discovery and following this config
What did you see instead? Under which circumstances?
I expected to be able to rule out services I don't care to discover. Instead the configuration file only allows a whitelist. That effectively neutralises the usefulness of the service discovery, because now I have to keep the Prometheus scrape list up-to-date, whereas if it was a blacklist then I would only have to change that list for services I don't care about.