Skip to content

[Lambda Java v2.11.x] Merge All Code Changes from v1.33.x Branch into v2.11.x #1114

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: release/v2.11.x
Choose a base branch
from

Conversation

lukeina2z
Copy link

This change merges all private Lambda Java updates from the v1.33 branch into the v2.11.x branch. I performed a 'git rebase v2.11' on the v1.33 branch, reviewed all changes, and completed the build and testing process. The resulting Lambda layer generated trace data identical to the version built directly from the v2.11.x branch (excluding this PR).

Here is the list of all migrated PRs:

Build layer during CI/CD workflows + some minor refactoring #989

support java11 runtime for lambda #1001

Unique artifact names for upload and merge for download #1014

Bug fixes] Lambda - duplicate lambda spans + appsignals from unsampled spans #1000

Fix: Lambda Topology Issue (#1016)

Fix: Lambda Topology Issue (#1016) #1085

feat: Support microservice span in Lambda Java environment. #1053

Test
Tested Java11, 17, and 21 Lambda functions. Manually tested PR-1000 and PR-1053. Both work as expected in the v2.11 branch. MicroService (SpringBoot) support works well. I verified attribute Trace.lambda.multiple server can be found in the Lambda server span, once we have Servlet instrumentation enabled with OTEL_INSTRUMENTATION_SERVLET_ENABLED.

Note: The changes in the patch files are not included in this PR. They should have been reviewed and incorporated as part of this migration:

Upgrade Java Lambda Layer to 2.x #1076

Lambda with SpringBoot MicroService:
lambda

Service Map and added microservice attribute 'Trace.lambda.multiple server'.
traceMap

AppSignals
appSignals

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

… v2.11.x

This change merges all private Lambda Java updates from the v1.33 branch into the v2.11.x branch.  I performed a 'git rebase v2.11' on the v1.33 branch, reviewed all changes, and completed the build and testing process. The resulting Lambda layer generated trace data identical to the version built directly from the v2.11.x branch (excluding this PR).

Here is the list of all migrated PRs:

Build layer during CI/CD workflows + some minor refactoring aws-observability#989
aws-observability#989

support java11 runtime for lambda aws-observability#1001
aws-observability#1001

Unique artifact names for upload and merge for download aws-observability#1014
aws-observability#1014

Bug fixes] Lambda - duplicate lambda spans + appsignals from unsampled spans aws-observability#1000
aws-observability#1000

Fix: Lambda Topology Issue (aws-observability#1016)
aws-observability#1016
Fix: Lambda Topology Issue (aws-observability#1016) aws-observability#1085
aws-observability#1085

feat: Support microservice span in Lambda Java environment. aws-observability#1053
aws-observability#1053

Test
Tested Java11, 17, and 21 Lambda functions. Manually tested PR-1000 and PR-1053. Both work as expected in the v2.11 branch. MicroService (SpringBoot) support works well. I verified attribute Trace.lambda.multiple server can be found in the Lambda server span, once we have Servlet instrumentation enabled with OTEL_INSTRUMENTATION_SERVLET_ENABLED.

Note: The changes in the patch files are not included in this PR. They should have been reviewed and incorporated as part of this migration:

    Upgrade Java Lambda Layer to 2.x aws-observability#1076
    aws-observability#1076
@lukeina2z lukeina2z requested a review from a team as a code owner July 8, 2025 22:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant