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[Question] Application metrics monitoring of Kubernetes Pods #2841
Comments
This comment has been minimized.
This comment has been minimized.
|
Usage questions are best asked at https://groups.google.com/forum/#!forum/prometheus-users Look at kubernetes service discovery. |
brian-brazil
closed this
Jun 13, 2017
This comment has been minimized.
This comment has been minimized.
|
Thanks @brian-brazil , I'll have a look. Found an example in the meanwhile:
|
This comment has been minimized.
This comment has been minimized.
bibinwilson
commented
Oct 13, 2017
•
|
Hi @boeboe , |
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.
boeboe commentedJun 13, 2017
•
edited
Hi all,
We are already using node-exporters to pull/collect docker/container metrics within our kubernetes environment. Next we would also like to be able to collect application metrics (provided by spring-actuator in our case, eg. http://pod-name:8080/prometheus). How is this typically done, keeping in mind we cannot use Kubernetes services as fixed DNS names (they are load balanced over the pods behind the service) and the fact that pods disappear and appear all the time, changing their name and hence addressability?
Our initial naive approach was the following (but this will not be sufficient since it is load-balanced by the service):
Any advice or examples would be really great.
Thanks a lot in advance,
Bart