← Problem Library
K8s L5 K8S 1532 · 10 min

A metrics adapter reports healthy and HPA still stays flat because one query path rounds low rates to zero after scrape tuning

Metrics exist, but the adapter still calculates with the old resolution and truncates small values away.

K8sPlatform ReliabilityLevel 5Pro10 min
Scenario

Autoscaling stops only after metrics scrape interval tuning.

What to check first
  • Identify the primary failure signal in the The Adapter Heard the Signal and Rounded It Down to Silence Because It Was Still Measuring With Yesterday's Ruler scenario.
  • Separate visible symptoms from the underlying technical dependency.
  • Describe the safest recovery path and the follow-up prevention work.
Checking checklist
  1. Summarize the current impact and the last known change.
  2. Collect direct evidence from logs, runtime state, and configuration before changing anything.
  3. Separate immediate recovery from permanent prevention work.
Recovery and prevention

Compare adapter resolution and scrape interval before changing targets.

Questions worth viewing together
Should I translate commands, logs, or product names?

No. Keep commands, logs, file names, APIs, and product names unchanged, then explain the reasoning in the selected UI language.

What should the answer focus on?

State the root cause, the evidence that supports it, and the safest recovery direction.

Why can the scenario remain in the original language?

The source scenario is treated as an incident artifact. Guidance, checklist, hints, and explanations can be localized around it.