Scenario
One HPA still reads zero after adapter query corrections.
A metrics adapter query is corrected and one HPA still reads zero because the recording rule keeps the retired metric label
The adapter query is right, but one recording rule still emits the previous label set and never matches the HPA selector.
What to check first
- Identify the primary failure signal in the The New Scoreboard Was Wired Properly and One Announcer Kept Calling the Team by the Name Printed on the Old Program scenario.
- Separate visible symptoms from the underlying technical dependency.
- Describe the safest recovery path and the follow-up prevention work.
Checking checklist
- Summarize the current impact and the last known change.
- Collect direct evidence from logs, runtime state, and configuration before changing anything.
- Separate immediate recovery from permanent prevention work.
Recovery and prevention
Inspect recording rule labels before changing scale targets.
Questions worth viewing together
No. Keep commands, logs, file names, APIs, and product names unchanged, then explain the reasoning in the selected UI language.
State the root cause, the evidence that supports it, and the safest recovery direction.
The source scenario is treated as an incident artifact. Guidance, checklist, hints, and explanations can be localized around it.
Similar cases seen in the field