Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Update dashboard-metrics-relation.md #12385

Merged
merged 7 commits into from
Dec 27, 2022
Merged

Update dashboard-metrics-relation.md #12385

merged 7 commits into from
Dec 27, 2022

Conversation

lilyjazz
Copy link
Member

@lilyjazz lilyjazz commented Dec 22, 2022 •
edited
Loading

First-time contributors' checklist

What is changed, added or deleted? (Required)

Which TiDB version(s) do your changes apply to? (Required)

Tips for choosing the affected version(s):

By default, CHOOSE MASTER ONLY so your changes will be applied to the next TiDB major or minor releases. If your PR involves a product feature behavior change or a compatibility change, CHOOSE THE AFFECTED RELEASE BRANCH(ES) AND MASTER.

For details, see tips for choosing the affected versions (in Chinese).

  • master (the latest development version)
  • v6.6 (TiDB 6.6 versions)
  • v6.5 (TiDB 6.5 versions)
  • v6.4 (TiDB 6.4 versions)
  • v6.1 (TiDB 6.1 versions)
  • v5.4 (TiDB 5.4 versions)
  • v5.3 (TiDB 5.3 versions)
  • v5.2 (TiDB 5.2 versions)
  • v5.1 (TiDB 5.1 versions)
  • v5.0 (TiDB 5.0 versions)

What is the related PR or file link(s)?

  • This PR is translated from:
  • Other reference link(s):

Do your changes match any of the following descriptions?

  • Delete files
  • Change aliases
  • Need modification after applied to another branch
  • Might cause conflicts after applied to another branch

@ti-chi-bot
Copy link
Member

ti-chi-bot commented Dec 22, 2022 •
edited
Loading

[REVIEW NOTIFICATION]

This pull request has been approved by:

  • Oreoxmt
  • shichun-0415

To complete the pull request process, please ask the reviewers in the list to review by filling /cc @reviewer in the comment.
After your PR has acquired the required number of LGTMs, you can assign this pull request to the committer in the list by filling /assign @committer in the comment to help you merge this pull request.

The full list of commands accepted by this bot can be found here.

Reviewer can indicate their review by submitting an approval review.
Reviewer can cancel approval by submitting a request changes review.

@ti-chi-bot ti-chi-bot added missing-translation-status This PR does not have translation status info. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Dec 22, 2022
@ti-chi-bot ti-chi-bot added size/S Denotes a PR that changes 10-29 lines, ignoring generated files. and removed size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Dec 22, 2022
@Oreoxmt Oreoxmt requested review from Oreoxmt and removed request for shichun-0415 December 22, 2022 14:36
@Oreoxmt Oreoxmt self-assigned this Dec 22, 2022
@Oreoxmt Oreoxmt added type/enhancement The issue or PR belongs to an enhancement. translation/doing This PR’s assignee is translating this PR. area/diagnosis Indicates that the Issue or PR belongs to the area of diagnosis and monitoring. and removed missing-translation-status This PR does not have translation status info. labels Dec 22, 2022
@ti-chi-bot ti-chi-bot added size/L Denotes a PR that changes 100-499 lines, ignoring generated files. and removed size/S Denotes a PR that changes 10-29 lines, ignoring generated files. labels Dec 26, 2022
Oreoxmt
Oreoxmt approved these changes Dec 26, 2022
View reviewed changes
Copy link
Collaborator

@Oreoxmt Oreoxmt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@ti-chi-bot ti-chi-bot added the status/LGT1 Indicates that a PR has LGTM 1. label Dec 26, 2022
@Oreoxmt Oreoxmt requested a review from shichun-0415 December 26, 2022 09:51
shichun-0415
shichun-0415 approved these changes Dec 27, 2022
View reviewed changes
Copy link
Contributor

@shichun-0415 shichun-0415 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Rest LGTM

dashboard/dashboard-cluster-info.md Show resolved Hide resolved
dashboard/dashboard-diagnostics-access.md Outdated
4. 设置基线开始时间，即想要对比的系统正常时段的开始时间，如 2020-05-21 14:30:00。
5. 点击开始。
1. 设置区间的开始时间，即异常时间段的开始时间，如 2022-05-21 14:40:00。
2. 设置区间长度 (Range Duration)。一般只系统异常的持续时间，例如 5 min。
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
2. 设置区间长度 (Range Duration)。一般只系统异常的持续时间，例如 5 min。
2. 设置区间长度 (Range Duration)。一般指系统异常的持续时间，例如 5 min。

dashboard/dashboard-key-visualizer.md Outdated
@@ -63,7 +63,7 @@ aliases: ['/docs-cn/dev/dashboard/dashboard-key-visualizer/','/docs-cn/dev/how-t

### 设置

首次使用流量可视化页面需要先通过**设置**页面手动开启此功能。参考页面指引，点击 **Open Settings**（打开设置）即可打开设置页面：
首次使用流量可视化页面需要先通过**设置**页面手动开启此功能。参考页面指引，点击 **打开设置** (Open Settings) 即可打开设置页面：
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
首次使用流量可视化页面需要先通过**设置**页面手动开启此功能。参考页面指引，点击 **打开设置** (Open Settings) 即可打开设置页面：
首次使用流量可视化页面需要先通过**设置**页面手动开启此功能。参考页面指引，点击**打开设置** (Open Settings) 即可打开设置页面：

dashboard/dashboard-key-visualizer.md Outdated
@@ -11,9 +11,9 @@ aliases: ['/docs-cn/dev/dashboard/dashboard-key-visualizer/','/docs-cn/dev/how-t

可以通过以下两种方法访问 Key Visualizer 流量可视化页面：

* 登录 TiDB Dashboard 后，点击左侧导航条的 **Key Visualizer**（流量可视化）：
* 登录 TiDB Dashboard 后，点击左侧导航条的 **流量可视化** (Key Visualizer)：
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
* 登录 TiDB Dashboard 后，点击左侧导航条的 **流量可视化** (Key Visualizer)：
* 登录 TiDB Dashboard 后，点击左侧导航条的**流量可视化** (Key Visualizer)：

dashboard/dashboard-key-visualizer.md Outdated
@@ -75,7 +75,7 @@ aliases: ['/docs-cn/dev/dashboard/dashboard-key-visualizer/','/docs-cn/dev/how-t

![设置页面](/media/dashboard/dashboard-keyviz-settings.png)

通过开关设定好是否开启收集，并点击 **Save**（保存）后生效。开启后，在界面上观察到工具栏已经可以使用：
通过开关设定好是否开启收集，并点击 **保存** (Save) 后生效。开启后，在界面上观察到工具栏已经可以使用：
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
通过开关设定好是否开启收集，并点击 **保存** (Save) 后生效。开启后，在界面上观察到工具栏已经可以使用：
通过开关设定好是否开启收集，并点击**保存** (Save) 后生效。开启后，在界面上观察到工具栏已经可以使用：

dashboard/dashboard-key-visualizer.md Outdated
@@ -86,12 +86,12 @@ aliases: ['/docs-cn/dev/dashboard/dashboard-key-visualizer/','/docs-cn/dev/how-t
打开流量可视化页面时，默认会显示最近六小时整个数据库内的热力图。其中，越靠近右侧（当前时间）时，每列 Bucket 对应的时间间隔会越小。如果你想观察某个特定时间段或者特定的 Region 范围，则可以通过放大来获得更多细节。具体操作描述如下：

* 在热力图中向上或向下滚动。
* 点击 **Select & Zoom**（框选）按钮，然后点击并拖动以选择要放大的区域。
* 点击 **框选** (Select & Zoom) 按钮，然后点击并拖动以选择要放大的区域。
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
* 点击 **框选** (Select & Zoom) 按钮，然后点击并拖动以选择要放大的区域。
* 点击**框选** (Select & Zoom) 按钮，然后点击并拖动以选择要放大的区域。

dashboard/dashboard-key-visualizer.md Outdated

![框选](/media/dashboard/dashboard-keyviz-select-zoom.gif)

* 点击 **Reset**（重置）按钮，将 Region 范围重置为整个数据库。
* 点击「时间选择框」（界面的 **6 hours** 处），重新选择观察时间段。
* 点击 **重置** (Reset) 按钮，将 Region 范围重置为整个数据库。
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
* 点击 **重置** (Reset) 按钮，将 Region 范围重置为整个数据库。
* 点击**重置** (Reset) 按钮，将 Region 范围重置为整个数据库。

dashboard/dashboard-key-visualizer.md Outdated
@@ -101,7 +101,7 @@ aliases: ['/docs-cn/dev/dashboard/dashboard-key-visualizer/','/docs-cn/dev/how-t

### 调整亮度

热力图使用颜色的明暗来表达一个 Bucket 的流量高低，颜色越暗 (cold) 表示该区域的 Region 在这个时间段上读写流量较低，颜色越亮 (hot) 表示读写流量越高，即越热。如果热力图中的颜色太亮或太暗，则可能很难观察到细节。此时，可以点击 **Brightness**（调整亮度）按钮，然后通过滑块来调节页面的亮度。
热力图使用颜色的明暗来表达一个 Bucket 的流量高低，颜色越暗 (cold) 表示该区域的 Region 在这个时间段上读写流量较低，颜色越亮 (hot) 表示读写流量越高，即越热。如果热力图中的颜色太亮或太暗，则可能很难观察到细节。此时，可以点击 **调整亮度** (Brightness) 按钮，然后通过滑块来调节页面的亮度。
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
热力图使用颜色的明暗来表达一个 Bucket 的流量高低，颜色越暗 (cold) 表示该区域的 Region 在这个时间段上读写流量较低，颜色越亮 (hot) 表示读写流量越高，即越热。如果热力图中的颜色太亮或太暗，则可能很难观察到细节。此时，可以点击 **调整亮度** (Brightness) 按钮，然后通过滑块来调节页面的亮度。
热力图使用颜色的明暗来表达一个 Bucket 的流量高低，颜色越暗 (cold) 表示该区域的 Region 在这个时间段上读写流量较低，颜色越亮 (hot) 表示读写流量越高，即越热。如果热力图中的颜色太亮或太暗，则可能很难观察到细节。此时，可以点击**调整亮度** (Brightness) 按钮，然后通过滑块来调节页面的亮度。

dashboard/dashboard-key-visualizer.md Outdated
@@ -121,7 +121,7 @@ aliases: ['/docs-cn/dev/dashboard/dashboard-key-visualizer/','/docs-cn/dev/how-t

### 刷新与自动刷新

可以通过点击 **Refresh**（刷新）按钮来重新获得基于当前时间的热力图。当需要实时观察数据库的流量分布情况时，可以点击按钮右侧的向下箭头，选择一个固定的时间间隔让热力图按此间隔自动刷新。
可以通过点击 **刷新** (Refresh) 按钮来重新获得基于当前时间的热力图。当需要实时观察数据库的流量分布情况时，可以点击按钮右侧的向下箭头，选择一个固定的时间间隔让热力图按此间隔自动刷新。
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
可以通过点击 **刷新** (Refresh) 按钮来重新获得基于当前时间的热力图。当需要实时观察数据库的流量分布情况时，可以点击按钮右侧的向下箭头，选择一个固定的时间间隔让热力图按此间隔自动刷新。
可以通过点击**刷新** (Refresh) 按钮来重新获得基于当前时间的热力图。当需要实时观察数据库的流量分布情况时，可以点击按钮右侧的向下箭头，选择一个固定的时间间隔让热力图按此间隔自动刷新。

@ti-chi-bot ti-chi-bot added status/LGT2 Indicates that a PR has LGTM 2. and removed status/LGT1 Indicates that a PR has LGTM 1. labels Dec 27, 2022
shichun-0415
shichun-0415 approved these changes Dec 27, 2022
View reviewed changes
Copy link
Contributor

@shichun-0415 shichun-0415 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@Oreoxmt
Copy link
Collaborator

Oreoxmt commented Dec 27, 2022

/merge

@ti-chi-bot
Copy link
Member

This pull request has been accepted and is ready to merge.

Commit hash: b4c3078

@ti-chi-bot ti-chi-bot added the status/can-merge Indicates a PR has been approved by a committer. label Dec 27, 2022
@ti-chi-bot ti-chi-bot merged commit 93f6931 into pingcap:master Dec 27, 2022
@Oreoxmt Oreoxmt mentioned this pull request Jan 17, 2023
Merged
14 tasks
@Oreoxmt Oreoxmt removed the translation/doing This PR’s assignee is translating this PR. label Jan 17, 2023
@ti-chi-bot ti-chi-bot added the missing-translation-status This PR does not have translation status info. label Jan 17, 2023
@Oreoxmt Oreoxmt added the translation/done This PR has been translated from English into Chinese and updated to pingcap/docs-cn in a PR. label Jan 17, 2023
@ti-chi-bot ti-chi-bot removed the missing-translation-status This PR does not have translation status info. label Jan 17, 2023
@ti-chi-bot ti-chi-bot mentioned this pull request Jan 18, 2023
Merged
14 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@Oreoxmt Oreoxmt Oreoxmt approved these changes

@shichun-0415 shichun-0415 shichun-0415 approved these changes

Assignees

@Oreoxmt Oreoxmt

Labels
area/diagnosis Indicates that the Issue or PR belongs to the area of diagnosis and monitoring. size/L Denotes a PR that changes 100-499 lines, ignoring generated files. status/can-merge Indicates a PR has been approved by a committer. status/LGT2 Indicates that a PR has LGTM 2. translation/done This PR has been translated from English into Chinese and updated to pingcap/docs-cn in a PR. type/enhancement The issue or PR belongs to an enhancement.
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
4 participants
@lilyjazz @ti-chi-bot @Oreoxmt @shichun-0415