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 upAlso use consul tags as filter for service discovery #2285
Comments
This comment has been minimized.
This comment has been minimized.
|
You can do this via relabelling, see https://www.robustperception.io/finding-consul-services-to-monitor-with-prometheus/ |
brian-brazil
added
the
kind/question
label
Dec 15, 2016
This comment has been minimized.
This comment has been minimized.
|
oh cool :) . in that case thanks! (although it would be way more convenient the other way ;) ) |
flypenguin
closed this
Dec 15, 2016
iksaif
referenced this issue
Jan 19, 2018
Closed
consul: more efficient tag and service filtering #3711
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.
flypenguin commentedDec 15, 2016
Currently you can either scrape all services, or a list of certain services given by service name.
It would be really nice if you could also specify a tag filter, e.g. "prometheus_target", to use.
Current situation:
See Docs. Only consul service name is available for filtering.
Proposal for configuration:
Effect:
Should either scrape all services, or ...
Rationale:
We have much more services registered in consul than we want to scrape (most of them don't even have scraping endpoints for prometheus available). So prometheus should not try to scrape them, and possibly list them as failed if it can't reach the scraping endpoint.