This repository has been archived by the owner on Dec 8, 2021. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 66
grafana dashboards support multiple cluster #556
Merged
ti-srebot
merged 1 commit into
pingcap:master
from
zjj2wry:grafana_dashboard_multiple_cluster
Jan 26, 2021
Merged
grafana dashboards support multiple cluster #556
ti-srebot
merged 1 commit into
pingcap:master
from
zjj2wry:grafana_dashboard_multiple_cluster
Jan 26, 2021
Conversation
This file contains 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
/cc @tennix @breeswish @AstroProfundis @DanielZhangQD |
/label needs-cherry-pick-4.0 |
These labels are not found |
/lgtm |
/lgtm |
ti-srebot
approved these changes
Jan 26, 2021
ti-srebot
added
the
status/LGT2
Two reviewers already commented LGTM, ready for merge (LGTM2)
label
Jan 26, 2021
/merge |
/run-all-tests |
/cherrypick release-4.0 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
4.0-cherry-pick
The target branch is release-4.0
CanMerge
status/LGT2
Two reviewers already commented LGTM, ready for merge (LGTM2)
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.
What problem does this PR solve?
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?
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
Check List
Tests
Side effects
Related changes
Release note