Scenario
One tenant's metrics vanish after exemplars were enabled while overall remote write still reports healthy.
A remote-write path looks healthy and one tenant disappears because exemplars for that tenant exceed the relabel budget and the Grafana Agent queue quietly drops that branch first
Remote write remains green overall, but one tenant branch starves after exemplar-heavy samples overflow the filtered queue path.
What to check first
- Identify the primary failure signal in the The Queue Stayed Green and One Tenant's Exemplars Quietly Spent the Whole Budget 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 tenant-level queue pressure before blaming storage or scrapes.
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