threading integration cannot be used with NoopTracer
See original GitHub issueThe NoopTracer
does not implement sampler
, exporter
, or propagator
but the threading
integration assumes that the tracer available has those properties. This can either be fixed by adding the properties to NoopTracer
or making the threading
integration check for them explicitly.
Happy to submit a fix with some guidance on direction.
Issue Analytics
- State:
- Created 5 years ago
- Reactions:2
- Comments:11 (8 by maintainers)
Top Results From Across the Web
opentracing/opentracing-java - Gitter
Hi everyone, thanks for being here! I'm using latest Quarkusversions (2.0.0.Final and Opentracing) it looks like after calling mongo with reactive operators ...
Read more >Contexts and Dependency Injection - Quarkus
Priority is that it has @Target({ TYPE, PARAMETER }) and so it cannot be used for producer methods and fields. This problem should...
Read more >Diff - platform/external/opencensus-java - Google Git
We cannot use the + * Function from Java 1.8 because this library is Java 1.6 compatible. + * + * @since 0.5...
Read more >io.opentracing.util.GlobalTracer java code examples - Tabnine
It is using {@link TracerResolver} service loader to find * the tracer. It tracer is not resolved it will use {@link io.opentracing.noop.NoopTracer}.
Read more >Upgraded to wildfly-24.0.0.Final & deployed EAR with this error
13:47:32,547 INFO [org.jboss.as.server] (Controller Boot Thread) ... on first use with a self-signed certificate for host localhost.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
One of the confusing things to me when reading the trace code is that there are two different objects called
Tracer
.opencencus.trace.tracer.Tracer
sampler
,exporter
,propagator
,tracer
opencensus.trace.tracers.base.Tracer
context_tracer.ContextTracer
,noop_tracer.NoopTracer
inherit from itTypically the first
opencensus.trace.tracer.Tracer
is put in theexecution_context
as is done by theTracer.store_tracer()
method on that object. However by default theexecution_context
holds aNoopTracer
.Those fields are no longer part of the
Tracer
.Sampler
is part of TracerProvider.Exporter
is part of SpanProcesser which is in turn part of TracerProviderPropagator
is set globally or instantiated manually