registry expose the metrics port #32
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
DawnGuoDev
force-pushed
the
feat/add-registry-metrics
branch
from
d5b4d34 to
c5c1a95
Compare
Signed-off-by: muze.dawn <[email protected]>
DawnGuoDev
force-pushed
the
feat/add-registry-metrics
branch
from
c5c1a95 to
d248610
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Describe what this PR does / why we need it
Registry will expose the metrics port. Users can get metrics from the port. It will not affect the use of registry.
Does this pull request fix one issue?
No.
Describe how you did it
Add some envs.
Describe how to verify it
curl http://${registryIP}:5001/metrics
Special notes for reviews