metrics: deduplicate TiDB Server Status panel by instance (#66680)#67037
metrics: deduplicate TiDB Server Status panel by instance (#66680)#67037ti-chi-bot wants to merge 4 commits intopingcap:release-8.1from
Conversation
Signed-off-by: ti-chi-bot <ti-community-prow-bot@tidb.io>
|
This cherry pick PR is for a release branch and has not yet been approved by triage owners. To merge this cherry pick:
DetailsInstructions 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. |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (3)
📝 WalkthroughWalkthroughModified Prometheus metric expressions in the TiDB Grafana dashboard to deduplicate instances. The Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~8 minutes Possibly related PRs
Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
📝 Coding Plan
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## release-8.1 #67037 +/- ##
================================================
Coverage ? 71.2789%
================================================
Files ? 1472
Lines ? 424908
Branches ? 0
================================================
Hits ? 302870
Misses ? 101504
Partials ? 20534
Flags with carried forward coverage won't be shown. Click here to find out more.
🚀 New features to boost your workflow:
|
|
/cherry-pick-invite |
|
@jiong-nba you're already a collaborator in repo |
|
/retest |
|
@yibin87: adding LGTM is restricted to approvers and reviewers in OWNERS files. DetailsIn response to this:
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. |
|
/retest |
|
/test check_dev_2 |
|
@jiong-nba: The specified target(s) for The following commands are available to trigger optional jobs: Use DetailsIn response to this:
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. |
|
@jiong-nba: No presubmit jobs available for pingcap/tidb@release-8.1 DetailsIn response to this:
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. |
|
/test check-dev2 |
|
@jiong-nba: No presubmit jobs available for pingcap/tidb@release-8.1 DetailsIn response to this:
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. |
|
/retest-required |
|
/test check-dev2 |
|
@jiong-nba: No presubmit jobs available for pingcap/tidb@release-8.1 DetailsIn response to this:
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. |
|
/retest |
|
/test all |
|
@jiong-nba: No presubmit jobs available for pingcap/tidb@release-8.1 DetailsIn response to this:
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. |
|
/retest |
2 similar comments
|
/retest |
|
/retest |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: XuHuaiyu, yibin87, zimulala The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
LGTM |
This is an automated cherry-pick of #66680
What problem does this PR solve?
Issue Number: close #66193
Problem Summary:
On the TiDB Cluster panel in Clinic, TiDB Server Status directly counts the up metric. When multiple job levels scrape simultaneously, the same instance may be counted repeatedly, resulting in redundant node display.
What changed and how does it work?
Updated
TiDB Server Statuspanel PromQL to deduplicate byinstancebefore counting:count(up{...} == 1/0)count(avg(up{...}) by (instance) == 1/0)This removes duplicate counting caused by multiple jobs exposing the same
upseries for one instance.Check List
Tests
Side effects
Documentation
Release note
Please refer to Release Notes Language Style Guide to write a quality release note.
Summary by CodeRabbit
Bug Fixes