FAQ and troubleshooting
How do I know a function was actually instrumented?
It shows an Instrumented status in Datadog, and in the AWS Console you should see two Datadog layers attached — the extension layer and the runtime-specific tracing layer. See Function Targeting.
Will this overwrite a function I already instrumented by hand?
No. If a function already carries Datadog layers or Datadog environment variables that the remote instrumenter didn't put there, it's marked already-manually-instrumented and skipped, specifically to avoid layer conflicts. See the skip reasons in Function Targeting.
How quickly does a new function get instrumented?
Two paths cover it: an EventBridge rule reacts to CreateFunction, UpdateFunctionConfiguration, TagResource, and UntagResource calls fairly quickly, and a scheduled run every 5 minutes acts as a backstop that also retries anything that failed before. See How It Works.
What runtimes are supported?
Node.js, Python, Ruby, Java, .NET, and the custom provided.al2 / provided.al2023 runtimes. Anything else is skipped with reason unsupported-runtime. Full mapping in Configuration Reference.
How do I change which functions get targeted?
Targeting rules are delivered as Remote Configuration from Datadog, not as CloudFormation parameters — change them from the Remote Instrumentation section in Datadog and the instrumenter picks up the change on its next scheduled run (or sooner, via retry logic in config.ts). See How It Works.
How do I remove remote instrumentation entirely?
Delete the CloudFormation stack. On stack deletion the instrumenter empties its S3 state bucket and un-instruments every function it had touched in the region, per the stack-delete behavior described in How It Works.
Can I use a Datadog site other than datadoghq.com?
Yes — the DdSite parameter accepts datadoghq.com, datadoghq.eu, us3.datadoghq.com, us5.datadoghq.com, ap1.datadoghq.com, ap2.datadoghq.com, or uk1.datadoghq.com. See Configuration Reference.
Where do I report a bug or request a change?
The project is open source at DataDog/serverless-remote-instrumentation — issues and releases are tracked there.
For account-specific issues (API key permissions, Remote Configuration access, or the Datadog-AWS integration itself), Datadog support is the fastest path.