-
Notifications
You must be signed in to change notification settings - Fork 5.9k
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.
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
metrics: grafana dashboards support multiple clusters (#22503) #22534
metrics: grafana dashboards support multiple clusters (#22503) #22534
Conversation
/run-all-tests |
@zjj2wry please accept the invitation then you can push to the cherry-pick pull requests. |
/run-all-tests |
Signed-off-by: 郑佳金 <zhengjiajin@pingcap.com>
1e8812a
to
3518679
Compare
/assign @zhongzc |
/lgtm |
/merge |
Sorry @zhongzc, this branch cannot be merged without an approval of release maintainers. |
/merge |
Sorry @breeswish, this branch cannot be merged without an approval of release maintainers. |
/merge |
/run-all-tests |
/merge |
cherry-pick #22503 to release-4.0
You can switch your code base to this Pull Request by using git-extras:
# In tidb repo: git pr https://github.com/pingcap/tidb/pull/22534
After apply modifications, you can push your change to this PR via:
What problem does this PR solve?
Issue Number: close #xxx
Problem Summary:
Many users(come from DBaaS、operator、tiup) monitor multiple TiDB clusters in one Grafana, this PR make Grafana dashboards support multiple clusters and not affect single cluster usage. Cluster variable is hidden by default.
What is changed and how it works?
What's Changed:
How it Works:
load it to your Grafana :))
Single Cluster:
No change
Multiple Cluster:
Construct a label that can uniquely identify the cluster. in tidb_operator, you can use {namespace}-{cluster_name} as your {tidb_cluster} variable.
add this configuration to your prometheus config
Related changes
Check List
Tests
Side effects
Release note