← Problem Library
K8s L5 K8S 1552 · 10 min

A Prometheus rule fires and the HPA still idles because the custom metrics API rounds one sparse series below the adapter floor

The metric exists, but the adapter still treats the low sparse series as zero after query downsampling.

K8sPlatform ReliabilityLevel 5Pro10 min
Scenario

Autoscaling stops only for low-volume workloads after recording rule tuning.

What to check first
  • Identify the primary failure signal in the The Alarm Rang Loudly and the Autoscaler Measured the Sound With a Ruler That Could Not Register Small Steps 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

Inspect adapter query resolution before raising thresholds.

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.