Proof of concept: Named Tracers / TracerFactory #186
Closed
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.
This draft shows a possible implementation of the Named Tracers RFC (open-telemetry/oteps#16).
Instead of working with a single global
Tracer
object, tracers must be created using a factory-pattern approach for a given tracer name.The
LoggingTracer.Demo.AspNetCore
application already makes uses of theITracerFactory
and produces log output using the tracer name as a logging prefix: