Skip to content

Update grafana-monitor-best-practices.md (#3288) #3740

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

Merged
merged 2 commits into from
Jun 19, 2020
Merged

Update grafana-monitor-best-practices.md (#3288) #3740

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
6dcc468
cherry pick #3288 to release-3.0
kissmydb May 26, 2020
50a3ced
Merge branch 'release-3.0' into release-3.0-da61aa85103d
ti-srebot Jun 19, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion best-practices/grafana-monitor-best-practices.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,7 @@ Prometheus 是一个拥有多维度数据模型和灵活查询语句的时序数

![TiDB 监控整体架构](/media/prometheus-in-tidb.png)

从 TiDB 2.1.3 版本开始，监控采用 pull 的方式，而之前版本采用的是 push 的方式，这是一个非常好的调整，它有以下几个优点：
从 TiDB 2.1.3 版本开始，监控可以支持 pull，这是一个非常好的调整，它有以下几个优点：

- 如果 Prometheus 需要迁移，无需重启整个 TiDB 集群。调整前，因为组件要调整 push 的目标地址，迁移 Prometheus 需要重启整个集群。
- 支持部署 2 套独立的 Grafana + Prometheus 的监控平台（非 HA），防止监控的单点。方法是使用 TiDB Ansible 用不同的 IP 各执行一次部署命令。
Expand Down