OpenTelemetry Semantic Conventions for AWS Lambda #30
Conversation
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
lbeschastny
force-pushed
the
fix/lambda-semconv
branch
from
558efbf to
9cb2b89
Compare
lbeschastny
force-pushed
the
fix/lambda-semconv
branch
from
dd2770e to
12df0a5
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
I tried following OpenTelemetry Semantic Conventions for Function-as-a-Service:
But though SignalFX supports Inferred publisher/subscriber (pub/sub) queues, it looks like it can only infer destination queries and not the source ones:
The span metadata looks correct with this PR (see this sample trace):
I'll pause working on this until I get some support from our Observability Guild, or from Splunk.