-
Notifications
You must be signed in to change notification settings - Fork 822
opentelemetry-instrumentation-aws-lambda: Fix aws lambda span creation #3966
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
herin049
wants to merge
6
commits into
open-telemetry:main
Choose a base branch
from
herin049:fix/aws-lambda-span-creation
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+94
−68
Open
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
92fc2f2
update invocation span to have kind SERVER and have name equal to the…
herin049 27907f1
update Lambda invocation span name and kind
herin049 f20d687
update CHANGELOG.md
herin049 8d1a1e4
Merge branch 'main' into fix/aws-lambda-span-creation
herin049 44e6291
add type checking check
herin049 27c5dd6
Merge branch 'main' into fix/aws-lambda-span-creation
herin049 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There are cases where span can be of other kinds:
"The span kind for both types of SQS spans SHOULD be CONSUMER"
https://opentelemetry.io/docs/specs/semconv/faas/aws-lambda/#sqs
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@xrmx I saw the documentation for SQS events too and I find it a bit ambiguous, but to me it still appears that the parent invocation span type should be
SERVERbased on the following statement in the spec:The key phrase being "The parent SHOULD be the
SERVERspan corresponding to the function invocation."From what I can tell, both the Java and JavaScript instrumentation libraries always have the initial Span be the
SERVERspan corresponding to the function invocation, and create additional childSpans for the SQS events.