fix: omit creating cold start on LMI by duncanista · Pull Request #717

fix: omit creating cold start on LMI by duncanista · Pull Request #717 · DataDog/datadog-lambda-js

duncanista deleted the jordan.gonzalez/lambda-managed-instances/avoid-cold-start-tracing branch

February 5, 2026 19:01

litianningdatadog added a commit that referenced this pull request

Feb 25, 2026

With provisioned concurrency, containers are pre-warmed before
invocations, causing module load timestamps to be captured minutes
(or hours) before the first invocation. This inflates aws.lambda.load
span durations to the full pre-warm gap rather than the actual load time.

Skip cold start span creation for provisioned-concurrency, consistent
with the existing fix for lambda-managed-instances (PR #717).
Fixes #723.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

litianningdatadog added a commit that referenced this pull request

Feb 25, 2026

With provisioned concurrency, containers are pre-warmed before
invocations, causing module load timestamps to be captured minutes
(or hours) before the first invocation. This inflates aws.lambda.load
span durations to the full pre-warm gap rather than the actual load time.

Skip cold start span creation for provisioned-concurrency, consistent
with the existing fix for lambda-managed-instances (PR #717).
Fixes #723.

litianningdatadog added a commit that referenced this pull request

Feb 26, 2026

With provisioned concurrency, containers are pre-warmed before
invocations, causing module load timestamps to be captured minutes
(or hours) before the first invocation. This inflates aws.lambda.load
span durations to the full pre-warm gap rather than the actual load time.

Skip cold start span creation for provisioned-concurrency, consistent
with the existing fix for lambda-managed-instances (PR #717).
Fixes #723.