Version 1.22.0 #5095
Unanswered
Version 1.22.0
#5095
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
API
GlobalOpenTelemetry.get
triggered autoconfiguration ifopentelemetry-sdk-extension-autoconfigure
was detected on the classpath. That behavior is now opt-in by setting environment variableOTEL_JAVA_GLOBAL_AUTOCONFIGURE_ENABLED=true
. (#5010)Context
SDK
ConfigUtil
for reading environment variables and system properties (#5048)Metrics
Exporter
OtlpGrpcSpanExporter
,OtlpHttpSpanExporter
,OtlpGrpcLogRecordExporter
,OtlpHttpLogRecordExporter
,ZipkinSpanExporter
, andJaegerGrpcSpanExporter
are now instrumented withGlobalOpenTelemetry
by default. Instrumentation initializes lazily to prevent ordering issue of accessingGlobalOpenTelemetry.get
beforeGlobalOpenTelemetry.set
is called. (#4993)ConfigurableSpanExporterProvider
implementation forJaegerGrpcSpanExporter
(#5002)ConfigurableSpanExporterProvider
,ConfigurableMetricExporterProvider
,ConfigurableLogRecordExporterProvider
forOtlpGrpc{Signal}Exporter
s andOtlpHttp{SignalExporter
s (#5003)AutoConfigurationCustomizerProvider
implementation forPrometheusHttpServer
(#5053)target_info
and scopetarget_info
metrics toPrometheusHttpServer
in compliance with spec (#5039)PrometheusHttpServer
(#5062)SDK Extensions
none
,all
,with_sampled_trace
are deprecated. Usealways_off
,always_on
,trace_based
instead. (#5063)OpenTracing Shim
🙇 Thank you
This release was possible thanks to the following contributors who shared their brilliant ideas and awesome pull requests:
@amouhadi
@brunobat
@carlosalberto
@cuichenli
@dashpole
@deejgregor
@jack-berg
@jkwatson
@lmolkova
@mateuszrzeszutek
@Oberon00
@RajatArora08
@trask
@vasireddy99
@yangtaoran
This discussion was created from the release Version 1.22.0.
Beta Was this translation helpful? Give feedback.
All reactions