## TL;DR

Use the latest from the docs. DD_TRACE_ENABLED / DD_LOGS_ENABLED.

## Steps

1. What you see: the function runs, CloudWatch has logs, but Serverless Functions in Datadog shows nothing.

2. **Layer attached?** Open the function config, Layers section. The Datadog extension layer must be listed. If someone deployed without it, there is no telemetry, period.
2. **Right region in the ARN?** The layer ARN embeds the region (`arn:aws:lambda:[region]:464622532012:layer:Datadog-Extension:[version]`). Copy-pasting an ARN from another region fails silently.
3. **Current layer version?** Old versions have known issues. Use the latest from the docs.
4. **DD_API_KEY set?** The function env must have it (via Secrets Manager in prod). Empty or placeholder means the extension cannot authenticate.
5. **DD_SITE set?** Non-US1 orgs need it on the function too, same trap as everywhere.
6. **DD_TRACE_ENABLED / DD_LOGS_ENABLED.** Metrics flow by default with the extension; traces and logs need their flags.
7. **Enhanced metrics need the forwarder?** No: enhanced Lambda metrics come through the extension. But log shipping from CloudWatch log groups still needs the forwarder subscription.

3. Invoke the function, wait a minute, check Serverless, Functions. If invocations appear but not traces, the tracer library is missing from your deployment package: the extension does not instrument code by itself.

4. Attaching only the forwarder subscription and expecting metrics and traces. The forwarder ships logs; telemetry needs the extension layer.

## When to use

You are seeing this: What you see: the function runs, CloudWatch has logs, but Serverless Functions in Datadog shows nothing. Use this skill when you run into "Lambda shows no Datadog data check the layer ARN region, env vars, site".

## 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

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

## Why this happens

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