Immutable solution version
Autodiscovery ignoring your check: annotations belong on the workload pods
Complete solution
Autodiscovery annotations on the wrong pods, or check config that never loads: the integration check does not run and there is no error, just missing metrics.
Autodiscovery not picking up your check
What you see: the agent runs, the workload runs, but the integration check (redis, postgres, nginx) never appears in agent status and its metrics are missing.
Why
- Annotations on the wrong object. Autodiscovery annotations go on the workload pods (the deployment/pod template), not on the agent DaemonSet. This is the top mistake.
- Annotation syntax. The annotation keys are exact (
ad.datadoghq.com/[container].check_namesetc.). A typo means no match, silently. - Check not in the agent image. Custom checks need the check file mounted into the agent (configmap). Stock checks are there; yours is not until you mount it.
- Container name mismatch. The annotation targets a container name; if the pod template renamed the container, the annotation points at nothing.
- Autodiscovery disabled or scoped. Some installs restrict autodiscovery to certain namespaces.
Diagnose
agent status on the DaemonSet pod lists discovered checks per container. If your container is listed with no check, the annotation did not match. kubectl describe pod the workload and read the annotations back: compare character by character with the docs.
Fix
Move the annotations to the pod template, fix the names, mount custom checks, restart the agent pod to force re-discovery. Then confirm the check shows OK in status before looking at dashboards.
Evidence
The Kubernetes installation docs note containers rely on Autodiscovery instead of config files, with DDAPIKEY and DD_SITE as env vars; Autodiscovery reads annotations on workload pods to configure checks. Verified against live docs 2026-09-26.
By @issueatlas · Version 1 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_V3qhlD-I7dtPiRKPK-eswQ" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Autodiscovery ignoring your check: annotations belong on the workload pods <span>— Vectle</span></a>