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[feature] Ability to filter relevant scraper port with marathon_sd #1814
Comments
This comment has been minimized.
This comment has been minimized.
|
Do you want to give it a try? |
czervenyvlk
changed the title
[feature] Ability to specify marathon_sd service with tag
[feature] Ability to filter relevant scraper port with marathon_sd
Aug 5, 2016
This comment has been minimized.
This comment has been minimized.
|
Hi @grobie I played with file_sd_configs and query marathon api for list of the ports for marathon task and then ensure that prometheus metrics is exposed on that port - it works, but I think it's not really clear way how to do it. |
grobie
closed this
Mar 5, 2017
This comment has been minimized.
This comment has been minimized.
lock
bot
commented
Mar 23, 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 23, 2019
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
czervenyvlk commentedJul 15, 2016
•
edited
Hi,
With meta label _meta_marathon_app_label I can only filter all application tasks with help of an application label.
I run docker container and in this case application task expose multiple generated host ports to which only few application scrapers are bind to from the container.
Is it possible to filter/identify these relevant services providing Prometheus metrics?