-
Notifications
You must be signed in to change notification settings - Fork 651
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
ext/jaeger - Transform resource to tags when exporting #645
Merged
toumorokoshi
merged 9 commits into
open-telemetry:master
from
nirsky:feat/jaeger/resource
May 19, 2020
Merged
Changes from 1 commit
Commits
Show all changes
9 commits
Select commit
Hold shift + click to select a range
91db3cd
ext/jaeger - Transform resource to tags when exporting
nirsky d756f58
Check for empty resource instead of None
nirsky 1d20465
Merge branch 'master' into feat/jaeger/resource
nirsky 82e103a
linting
nirsky 7d4ba99
Merge branch 'feat/jaeger/resource' of https://github.com/nirsky/open…
nirsky 12da24a
linting
nirsky 007165e
Merge branch 'master' into feat/jaeger/resource
nirsky 6559eec
Merge branch 'master' into feat/jaeger/resource
toumorokoshi 3127e73
Revert exposing resource
nirsky 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 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 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.
I'm wondering how we can make this test more efficient. It looks to me that
resource
is neverNone
but it is_EMPTY_RESOURCE
.opentelemetry-python/opentelemetry-sdk/src/opentelemetry/sdk/trace/__init__.py
Line 695 in 090b664
opentelemetry-python/opentelemetry-sdk/src/opentelemetry/sdk/resources/__init__.py
Lines 32 to 33 in 090b664
I think one solution could be to expose
_EMPTY_RESOURCE
(remove the_
) and make a comparison using theis
operator.if span.resource is not ̣̣̣resources.EMPTY_RESOURCE:
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.
I made the suggested change.
Though notice, I had to create an empty resource in all of the spans used for the jaeger tests, as it is not created by default when accessing the
trace.Span
directly.I guess that in the real flow it will always be created, but maybe it's something to consider and we should keep the
is not None
check nonetheless, just to play it safe.What do you think?
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.
Good point. TBH I'm not 100% what's the best approach here, I made that suggestion to make it more efficient, but probably it's not worthy as this check is very fast in both cases and we haven't done an optimization in other places yet. I'm fine with both solutions, let's see other people's opinions on this.