Specify tikv status address to fix monitoring #695
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
Signed-off-by: Aylei <rayingecho@gmail.com>
weekface
pushed a commit
that referenced
this pull request
Jul 29, 2019
Signed-off-by: Aylei <rayingecho@gmail.com> (cherry picked from commit 98d367e)
Merged
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.
Signed-off-by: Aylei rayingecho@gmail.com
What problem does this PR solve?
TiKV metrics port cannot be accessed from Prometheus by default.
Also, we have to notice users to keep this configuration when they customize the
tikv.configWhat is changed and how does it work?
Specify the tikv metrics listen address as
0.0.0.0Check List
Tests
Code changes
Side effects
Related changes
Does this PR introduce a user-facing change?:
@tennix @DanielZhangQD @weekface PTAL