PD: fix alert description by removing incorrect type label

[max-melentyev]

What problem does this PR solve?

Fixes incorrect alert description

PD: fix alert description by removing incorrect `type` label

Check List

Tests

[X] No code

Release note

PD: fix alert description by removing incorrect `type` label

Summary by CodeRabbit

• Bug Fixes
  • Improved alert descriptions by removing an outdated label reference and standardizing value formatting.
  • Updated alert configuration formatting while preserving the existing displayed summary.

[ti-chi-bot]

Hi @max-melentyev. Thanks for your PR.

I'm waiting for a tikv member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

[ti-chi-bot]

Welcome @max-melentyev!

It looks like this is your first PR to tikv/pd 🎉.

I'm the bot to help you request reviewers, add labels and more, See available commands.

We want to make sure your contribution gets all the attention it needs!



Thank you, and welcome to tikv/pd. 😃

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: d3a4ea10-2e04-4cc4-b0f8-d169cc8bf869

📥 Commits

Reviewing files that changed from the base of the PR and between 0087e3b and b4d217e.

📒 Files selected for processing (1)

• metrics/alertmanager/pd.rules.yml

🚧 Files skipped from review as they are similar to previous changes (1)

• metrics/alertmanager/pd.rules.yml

---

📝 Walkthrough

Walkthrough

Two alert annotations in metrics/alertmanager/pd.rules.yml were updated: one removes a label reference and adjusts interpolation spacing, while the other changes YAML formatting without changing displayed text.

Changes

Alert rule annotations

Layer / File(s)	Summary
Annotation formatting updates metrics/alertmanager/pd.rules.yml	The store space alert description no longer references the type label and adjusts values spacing; the etcd quota summary line was reformatted while retaining its text.

Estimated code review effort: 1 (Trivial) | ~2 minutes

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description is missing required template sections, including Issue Number and the 'What is changed and how does it work?' section.	Add the missing template sections, especially an Issue Number line, a change summary, side effects, related changes, and a complete release note if needed.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly matches the change: fixing an alert description by removing the incorrect type label.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: rleungx

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [rleungx]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2026-07-24 02:53:50.546171022 +0000 UTC m=+1546216.582266079: ☑️ agreed by rleungx.

[rleungx]

/retest

[max-melentyev]

force-pushed a commit with Signed-off-by

[ti-chi-bot]

[FORMAT CHECKER NOTIFICATION]

Notice: To remove the do-not-merge/needs-linked-issue label, please provide the linked issue number on one line in the PR body, for example: Issue Number: close #123 or Issue Number: ref #456, multiple issues should use full syntax for each issue and be separated by a comma, like: Issue Number: close #123, ref #456.

_{📖 For more info, you can check the "Linking issues" section in the CONTRIBUTING.md.}

[max-melentyev]

Hi @rleungx , thanks for the review. I've re-pushed the commit with sign-off added. Could you please unblock tests?

[rleungx]

/retest

[rleungx]

/ok-to-test

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 79.23%. Comparing base (39b6220) to head (b4d217e).
⚠️ Report is 2 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master   #11046      +/-   ##
==========================================
- Coverage   79.25%   79.23%   -0.02%     
==========================================
  Files         541      540       -1     
  Lines       76037    76010      -27     
==========================================
- Hits        60262    60229      -33     
+ Misses      11534    11527       -7     
- Partials     4241     4254      +13     

Flag	Coverage Δ
unittests	79.23% <ø> (-0.02%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[rleungx]

/retest

[ti-chi-bot]

@max-melentyev: 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
pull-unit-test-next-gen-3	b4d217e	link	true	/test pull-unit-test-next-gen-3

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.