metrics: support multiple k8s and tidb in grafana dashboards

[just1900]

Signed-off-by: just1900 legendj228@gmail.com

What problem does this PR solve?

Issue Number: close #1134

What is changed and how it works?

What's Changed:

• add a tidb_cluster label in all expr
• add a k8s_cluster label in all expr
• add tidb_cluster and k8s_cluster variable in Grafana templating

How it works:

• For users with single-k8s, nothing need to be changed, just use it as before.
• For users with multi-k8s:
  • first add kubernetes label to identify k8s cluster in your prometheus' external_labels.
  • set field "hide" to '0' to show variables in grafana via sed -i s/"hide": 2/"hide": 0/g <path/to/dashboard.json>
  • load it to grafana

Check List

Tests

• Unit test
• Integration test
• Manual test (add detailed scripts or steps below)
• No code

Code changes

• Has exported function/method change
• Has exported variable/fields change
• Has interface methods change
• Has persistent data change

Side effects

• Possible performance regression
• Increased code complexity
• Breaking backward compatibility

Related changes

• Need to cherry-pick to the release branch
• Need to update the documentation
• Need to update the tidb-ansible repository
• Need to be included in the release note

Release note

• support multiple k8s and tidb in grafana dashboards

[ti-chi-bot]

[REVIEW NOTIFICATION]

This pull request has not been approved.

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.

Details

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

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[ti-chi-bot]

@just1900: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
idc-jenkins-ci-binlog/check	94eb399	link	true	/test pull-check

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.