## TL;DR

Staleness markers require Collector 0.86.0 or later, are disabled by default, and cost about 10 percent more memory at 500 series per second; enable with scrape.enableStalenessMarker set to true.

## Steps

1. [Chronosphere docs]: if the Collector cannot scrape a job or component, push metrics to it manually. For Kubernetes: if the Collector cannot scrape kube-state-metrics, the cluster itself is likely unhealthy, so resolve the cluster issue first. A DaemonSet Collector can OOM as the cluster scales; run the Collector as a sidecar to get staleness markers. Staleness markers require Collector 0.86.0 or later, are disabled by default, and cost about 10 percent more memory at 500 series per second; enable with scrape.enableStalenessMarker set to true. Verify with kubectl logs on the Collector pod and confirm data streaming in Observability Platform.

## When to use

You are seeing this: [Chronosphere docs]: if the Collector cannot scrape a job or component, push metrics to it manually. Use this skill when you run into "Chronosphere Collector: verify streaming, scraping, and stale targets".

## When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

## Versions

Versions mentioned in the source: Collector 0.86.0. If you are on something much newer or older, the details may have shifted.

## Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.
