-
Notifications
You must be signed in to change notification settings - Fork 650
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
Named tracers #301
Merged
c24t
merged 28 commits into
open-telemetry:master
from
dynatrace-oss-contrib:named-tracers
Dec 14, 2019
Merged
Named tracers #301
Changes from 16 commits
Commits
Show all changes
28 commits
Select commit
Hold shift + click to select a range
d5c1da1
Named tracer.
Oberon00 94c72f8
Adapt all the things to named tracers.
Oberon00 f1a23c1
Fix examples, move add_span_processor to source.
Oberon00 d91e5dd
Fix examples for add_span_processor move.
Oberon00 2f95b61
Fix examples for good.
Oberon00 8014e52
Add unit tests.
Oberon00 fbf4a1e
Fix W3C tests, lint, docs.
Oberon00 716ead7
Increase test coverage.
Oberon00 ac5dc8b
Merge branch 'master' into named-tracers
Oberon00 7e9dad7
Adapt flask extension for named tracers.
Oberon00 009418a
Fix mismerge of da8b8d907c29fc358ca635114dac2967b6501563.
Oberon00 e69f102
Merge branch 'master' into named-tracers
Oberon00 9163c9b
Fix tracer -> tracer source in comments/doc.
Oberon00 ab805d2
Update opentelemetry-api/src/opentelemetry/trace/__init__.py
Oberon00 c987246
Merge branch 'master' into named-tracers
Oberon00 2aa258a
Adjust new tests to named tracers.
Oberon00 f05eaaf
Rewrap comments
c24t a6a2670
Fix stray examples
c24t e28713e
Merge remote-tracking branch 'upstream/master' into named-tracers
Oberon00 0cbdccb
Adapt new tests.
Oberon00 9236606
Fix docstrings.
Oberon00 725bb16
Rename creator_info to instrumentation_info.
Oberon00 4de385e
Merge branch 'master' into named-tracers-merge
c24t 7907133
Merge branch 'master' into named-tracers
Oberon00 b7c688c
Fix tests.
Oberon00 e4db217
libname -> module name
Oberon00 239a18d
Lint.
Oberon00 b48e708
Fix docs build.
Oberon00 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
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
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
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
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
Oops, something went wrong.
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.
Out of curiosity: why use the package name instead of the dotted namespace? E.g.
opentelemetry.ext.flask
? The later is closer to the__file__
convention for logger names, and you can have multiple unique names per package.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.
That would be another possibility. There should probably a unique mapping
full module name -> package
anyway.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.
+1 on the suggestion to use the name. Most loggers are configured that way as well, and having parity of the logging namespace and tracer namespace could be very useful.
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 changed it to the module name in e4db217. But note that once we have a registry pattern, we will be creating a tracer per module instead of per library with the most naive implementation at least.
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.
Yeah, one risk of copying
logging
here is that users might reasonably assume these names are meant to be hierarchical too.