opentelemetry-instrumentation-aws-lambda: Fix aws lambda span creation #3966
+94
−68
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.
Description
Fixes bug where the Lambda invocation
Spanname would be incorrectly set to the name of the Python handler function instead of the function name. Also fixes an issue where the Lambda invocationSpankind would occasionally not be set toSERVERwhich violates the OpenTelemetry FaaS semantic conventions.Fixes #3963
Type of change
Please delete options that are not relevant.
How Has This Been Tested?
Unit tests have been updated to reflect changing the invocation
Spanname to the Lambda function name and changing theSpankind to always beSERVER.Does This PR Require a Core Repo Change?
Checklist:
See contributing.md for styleguide, changelog guidelines, and more.