AWS Lambda Runtime legacy internal handlers need to be ignored from being instrumented and so traced … #10942
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.
... Otherwise, there might be double root spans.
Fixes #10931
In Java 8 and Java 11 runtimes, AWS Lambda runtime is packaged under
lambdainternal
package (it iscom.amazonaws.services.lambda.runtime.api.client
for new runtime likes Java 17 and Java 21)I have
/var/runtime/
folder in the AWS Lambda environment for Java 8 and Java 11 runtimes,Here are the existing files:
Then I have decompiled classes from
LambdaSandboxJava-byol.jar
andLambdaJavaRTEntry-byol.jar
.And as you can see below, AWS Lambda runtime internal classes are packaged under
lambdainternal
package and the internal handler (lambdainternal.EventHandlerLoader
) we need to ignore is there.