You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is about having one single method to be able to initiate a no-op OtelJava, by calling OtelJava.noop(). The method is already available for OpenTelemetrySdk, Meter, MeterProvider and so on, but does not exists yet for OtelJava. And since its constructor is private, no chance the create one easily.
The text was updated successfully, but these errors were encountered:
@fugafree what's the use case specifically for a no-op OtelJava, rather than just using the noop implicits for Tracer and Meter? the primary issue with having a no-op OtelJava is that the LocalContext can't really be no-op.
Incidentally, you can always do: OtelJava.forAsync(JOpenTelemetry.noop())
This is about having one single method to be able to initiate a no-op
OtelJava
, by callingOtelJava.noop()
. The method is already available forOpenTelemetrySdk
,Meter
,MeterProvider
and so on, but does not exists yet forOtelJava
. And since its constructor is private, no chance the create one easily.The text was updated successfully, but these errors were encountered: