metrics: fix memory metrics (#11656)#12814
metrics: fix memory metrics (#11656)#12814ti-srebot wants to merge 1 commit intotikv:release-4.0from
Conversation
Signed-off-by: ti-srebot <ti-srebot@pingcap.com>
|
[REVIEW NOTIFICATION] This pull request has been approved by:
To complete the pull request process, please ask the reviewers in the list to review by filling The full list of commands accepted by this bot can be found here. DetailsReviewer can indicate their review by submitting an approval review. |
|
@ti-srebot: This cherry pick PR is for a release branch and has not yet been approved by release team. To merge this cherry pick, it must first be approved by the collaborators. AFTER it has been approved by collaborators, please ping the release team in a comment to request a cherry pick review. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
/run-all-tests |
|
This pull request is closed because it's related version has closed automatic cherry-picking. You can find more details at: |
cherry-pick #11656 to release-4.0
You can switch your code base to this Pull Request by using git-extras:
# In tikv repo: git pr https://github.com/tikv/tikv/pull/12814After apply modifications, you can push your change to this PR via:
Signed-off-by: Shuaipeng Yu jackysp@gmail.com
What is changed and how it works?
Close #11662
What's Changed:
, fix it.

TiKV dashboard on Grafana gets all memory usage jobs from Prometheus, which makes user confused.
Related changes
pingcap/docs/pingcap/docs-cn:pingcap/tidb-ansible:Check List
Tests
Side effects
Release note