Scenario
One namespace begins double-counting metrics after a Grafana Agent Flow cleanup merged pod and service discovery blocks.
A Grafana Agent Flow pipeline duplicates one namespace because pod and service discovery now feed the same remote-write branch
Metrics arrive twice after a Flow refactor merged discovery branches that used to stay separate.
What to check first
- Identify the primary failure signal in the The Namespace Was Scraped Once and Walked Twice Into the Same Remote-Write Door 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 discovery fanout before changing downstream dedupe rules.
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