Switch to Python Profiling v2 from v1 #674
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do?
Includes
./python/lib/$runtime/site-packages/ddtrace/internal/datadog/profiling/stack_v2/_stack_v2.*.soin Python Lambda layer to enable python profiling v2.Motivation
The profiling team is planning on deprecating profiling v1 in the dd-trace-py 4.x release. We want to move lambdas to v2 before this happens.
Testing Guidelines
Tested profiling on a API Gateway -> Lambda -> SQS -> Lambda setup using custom lambda layer
arn:aws:lambda:us-west-2:425362996713:layer:Python313-profilingv2-rithika:1.Invoked producer lambda repeatedly in a short timespan to generate profiles. Inspected profiles in the Datadog UI and checked logs to ensure that "failing back to v1 stack sampler" warning log no longer appears. Profiles for producer lambdaAdditional Notes
Types of Changes
Check all that apply