-
Notifications
You must be signed in to change notification settings - Fork 63
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rename "metrics" port to "management" port #867
Comments
I'd like to work on this. Changing "metrics" to "management" port makes sense given its broader functionality. I'm ready to implement the change and update the docs. Thank you! |
Thanks @Saurabhkr952 . Once #863 is merged, I think it should be a matter of:
I think that'll about cover it. |
Please also document this as a new page on the website (in Saying that, I don't think we have documentation on this piece yet at all... |
Signed-off-by: Saurabhkr952 <saurabhkr952@gmail.com>
It seems that work on the issue has gotten a bit stale. Does anyone mind if I pick this task up? @Saurabhkr952? |
Hey @craigpastro, that would be great! I've reassigned the issue to you. Thank you 🙇 |
Thanks @beeme1mr! I'll try to get to it soon. |
Currently, the "metrics" port configuration controls the port the HTTP readyz/healthz checks, gRPC health check, and metrics.
We should change the name to "management" port to make clear it exposes more than just metrics.
Relates to: #863
Be sure to update any related doc.
The text was updated successfully, but these errors were encountered: