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 upMarathon SD: How to configure when docker network is bridge #2867
Comments
This comment has been minimized.
This comment has been minimized.
|
Prometheus adds 2 different label. I solved my problem joining this 2 labels
|
gianluca-sabena
closed this
Jun 21, 2017
gianluca-sabena
changed the title
Marathon SD: Doesn't work when docker network is bridge
Marathon SD: How to configure when docker network is bridge
Jun 21, 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.
gianluca-sabena commentedJun 21, 2017
•
edited
What did you do?
Deploy an app on DCOS/marathon with network bridge and random ports (I tried all possible combinations between container, host and service set to 0)
What did you expect to see?
Prometheus discovers app
What did you see instead? Under which circumstances?
Nothing, app is not present in target list
Environment
System information:
insert output of
uname -srmherePrometheus version:
1.7.0
Description
App deployed with network = bridge and a random port has this behaviors:
Since there are no labels in embedded task section marathon sd is not working because I can't use a relabel to filter the correct ports
Example marathon.json used to deploy app:
Example marathon api output: