HPA scaling breaks after two ServiceMonitor definitions are consolidated even though Prometheus still shows the target as healthy.
A Prometheus scrape stays green while custom metrics disappear because a merged ServiceMonitor drops the port label the adapter needs
The endpoint is up, but relabeling removes the label used to identify the metric series.
Scenario
What to check first
- Identify the primary failure signal in the The Scrape Survived the Merge and the Label the Adapter Needed Did Not 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
Compare relabel output before rebuilding the adapter or retuning thresholds.
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