customize aws lambda instrumentation to span kind always be SERVER #286
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.
Issue #, if available:
In OpenTelemetry Python contrib, datadog set the Lambda handler span kind to be CONSUMER if the Lambda invocation is triggered by SNS/SQS/DDB, but actually that logic should be applied to Lambda Service span. The Lambda handler span should be always SERVER since it is triggered by Lambda Service.
Description of changes:
Update the span kind of Lambda handler span to be SERVER from ADOT SDK repo.
After this change, the Lambda handler segment name looks normal
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.