The Monitor of TiDB has an invalid metric about store0.

[superlzs0476]

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)

2. What did you expect to see? (Required)

3. What did you see instead (Required)

This cluster need not store that name is 'store0‘, so I don't want to see an invalid metric.

4. What is your TiDB version? (Required)

v4.0.4

[ZenoTan]

Is it store-0 a valid store in your cluster? You should be more clear about how to reproduce it.

[sre-bot]

Integrity check:
component RCA symptom trigger_condition affect_version fix_version fields are empty

Please comment /info to get template

[ti-srebot]

Please edit this comment to complete the following information

Bug

1. Root Cause Analysis (RCA)

RPC send by the GC module does not have store id in the RPC context, so the default value 0 will be used.

2. Symptom

Periodically, store-0 related metrics appears on the monitoring panel.

3. All Trigger Conditions

na

4. Workaround (optional)

5. Affected versions

[v4.0.0:v4.0.7]

6. Fixed versions

v4.0.8

[seiya-annie]

add component/metrics based on labels in PR