how-to/monitor: add key-visualizer documentation#2432
Merged
Conversation
Signed-off-by: Zheng Xiangsheng <hundundm@gmail.com>
|
|
TomShawn
added
translation/doing
TomShawn
reviewed
Mar 16, 2020
Contributor
|
@HunDunDM Please also involve a technical review, thanks! |
Co-Authored-By: TomShawn <41534398+TomShawn@users.noreply.github.com>
TomShawn
reviewed
Apr 22, 2020
Co-Authored-By: TomShawn <41534398+TomShawn@users.noreply.github.com>
Signed-off-by: Zheng Xiangsheng <hundundm@gmail.com>
Contributor
Author
|
PTAL @TomShawn |
Contributor
|
@HunDunDM 请添加到 TOC 目录。Rest LGTM. |
kissmydb
reviewed
Apr 22, 2020
kissmydb
reviewed
Apr 22, 2020
| > | ||
| > 默认情况下 `PDPort` 是 `2379`。若部署时修改过 PD 相应参数，则需要填写对应的端口。 | ||
| > | ||
| > 登录 TiDB Dashboard 需要使用 TiDB 的 `root` 账号。 |
Contributor
There was a problem hiding this comment.
默认使用 root。后期不用 root 是不是也可以，比如单独创建一个 dashboard 的访问用户，需要什么权限？
Member
There was a problem hiding this comment.
4.0 GA 版本上只能 root，非 root 视需求可以在后续版本实现（实现了的话需要 SUPER 权限）（具体什么权限可以讨论）
kissmydb
reviewed
Apr 22, 2020
| > | ||
| > 这里只是列出了几种常见的热力图模式。Key Visualizer 中实际展示的是整个集群上所有数据库、数据表的热力图，因此非常有可能在不同的区域观察到不同的热力图模式，也可能观察到多种热力图模式的混合结果。使用的时候应当视实际情况灵活判断。 | ||
|
|
||
| ### 解决热点问题 |
Contributor
There was a problem hiding this comment.
这里感觉有问题，key vis 是用来发现和排查热点工具，这里反而引导到老版本上。建议增加更多描绘如何用 key vis 来分析热点问题
Contributor
Author
There was a problem hiding this comment.
如何理解“引导到老版本上”？keyviz 只是帮助更直观地观察流量模式和发现热点。至于分析热点的成因和排除，keyviz 暂时是无能为力的，还是需要使用以前的方法。
Contributor
|
@HunDunDM, please update your pull request. |
1 similar comment
Contributor
|
@HunDunDM, please update your pull request. |
Co-Authored-By: kissmydb <likun@pingcap.com>
rleungx
reviewed
Apr 29, 2020
Co-Authored-By: Ryan Leung <rleungx@gmail.com>
lhy1024
approved these changes
Apr 29, 2020
rleungx
approved these changes
Apr 29, 2020
TomShawn
added
status/can-merge
Contributor
|
/run-all-tests |
Contributor
|
cherry pick to release-4.0 in PR #2926 |
TomShawn
pushed a commit
that referenced
this pull request
Apr 29, 2020
5 tasks
5 tasks
TomShawn
added
translation/done
5 tasks
rleungx
pushed a commit
to rleungx/docs-cn
that referenced
this pull request
May 22, 2020
5 tasks
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
10 participants
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: Zheng Xiangsheng hundundm@gmail.com
What is changed, added or deleted? (Required)
Added document for using Key Visualizer under v4.0.0-beta.1.
Note: This document is out of date for the master branch.
Which TiDB version(s) do your changes apply to? (Required)
If you select two or more versions from above, to trigger the bot to cherry-pick this PR to your desired release version branch(es), you must add corresponding labels such as needs-cherry-pick-3.1, needs-cherry-pick-3.0, and needs-cherry-pick-2.1.
What is the related PR or file link(s)?