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 upAdopt .well-known/metrics/${APPLICATION} as defacto endpoint for metrics #2523
Comments
This comment has been minimized.
This comment has been minimized.
Different ports usually.
That would be a new service discovery mechanism, which we don't wish to establish. What happens if there's multiple mysql or apache exporters per machine for example? |
This comment has been minimized.
This comment has been minimized.
|
Seems reasonable. I'll close this issue; Cheers! |
andrewhowdencom
closed this
Mar 24, 2017
andrewhowdencom
referenced this issue
Nov 6, 2017
Closed
Expose metrics about kube-state-metrics itself #296
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. |
andrewhowdencom commentedMar 24, 2017
•
edited
What did you do?
Used Prometheus for a while. Noticed that were multiple services are exposed on the same interface, it's not clear how to separate them (virtual hosts? different URLs? and so on)
What did you expect to see?
Nothing much. This is an idea.
What did you see instead? Under which circumstances?
I'm picking this for my own standard, where I control such endpoints. So, this is just up-streaming a suggestion.
Dropped environment specific notes, as they're not relevant. Honestly, this is just a "oh I have a crazy idea".
Many applications appear to be picking their own ad-hoc places to put metrics (quite often at /metrics where possible, or under /admin/metrics etc). IANA have a standard at which they expose "well-known" artifacts such as the Lets Encrypt nonce/hash/things, keybase use it for verification etc. Ref: http://www.iana.org/assignments/well-known-uris/well-known-uris.xhtml
Instead, I suggest that
This would require minimal changes to the Prometheus codebase, rather just changes to the examples / documentation.
Perhaps this is not an issue that other people have run into, but it's one I have.
Thanks for your time / building such an awesome thing!