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 upAbility to drop ports from the instance dynamic label. #653
Comments
This comment has been minimized.
This comment has been minimized.
|
This will be possible in the near future through relabelling. It will be part of the groundwork for more advanced service discovery than we have now. There is a design doc going into more detail - all comments and suggestions are welcome. |
fabxc
closed this
Apr 24, 2015
simonpasquier
pushed a commit
to simonpasquier/prometheus
that referenced
this issue
Oct 12, 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.
AmandaCameron commentedApr 24, 2015
I'd like it if it was possible to configure Prometheus to drop the port from the instance label.
My use-case:
My web-apps are exposed using a random docker port, however the tooling I have in place generates a web-app/host unique CNAME entry in our internal DNS, and since DOcker is assigning the external port "randomly" it's a bit bothersome to have it in there, as not only is it redundent, but it's going to be different beween launches of my web-apps.
I'm AmandaC in #prometheus, feel free to highlight me for further info / questions.
I'd be happy to come up with a simple PR for this, if there's interest. I just don't want to end up with the burden of maintaining a fork.