1.5.0 / 1.5.0-beta.1 #4546
utpilla
announced in
Announcements
Replies: 1 comment 2 replies
-
Looking over the changes, it seems like 1.5 is primarily a bug-fix version over 1.4. Do I have that right? Is there anything that is new? |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
OpenTelemetry
Fixed a bug introduced by
#4508 in
1.5.0-rc.1 which caused the "Build" extension to return
null
when performingchained/fluent calls.
(#4529)
Marked
Exemplars
and related APIsinternal
as the spec forExemplars
isnot stable yet. This would be added back in the
1.6.*
prerelease versionsright after
1.5.0
stable version is released.(#4533)
OpenTelemetry.Api.ProviderBuilderExtensions
IServiceCollection.ConfigureOpenTelemetryMeterProvider
overloadwhich may be used to configure
MeterProviderBuilder
s while theIServiceCollection
is modifiable (before theIServiceProvider
has beencreated).
(#4517)
OpenTelemetry.Exporter.Console
Exemplars
. This would be added back in the1.6.*
prerelease versions right after1.5.0
stable version is released.(#4533)
OpenTelemetry.Exporter.OpenTelemetryProtocol
Exemplars
. This would be added back in the1.6.*
prerelease versions right after1.5.0
stable version is released.(#4533)
OpenTelemetry.Instrumentation.AspNetCore
Fix issue where baggage gets cleared when the ASP.NET Core Activity
is stopped. The instrumentation no longer clears baggage. One problem
this caused was that it prevented Activity processors from accessing baggage
during their
OnEnd
call.(#4274)
Added direct reference to
System.Text.Encodings.Web
with minimum version of4.7.2
due to CVE-2021-26701.This impacts target frameworks
netstandard2.0
andnetstandard2.1
which has areference to
Microsoft.AspNetCore.Http.Abstractions
that depends onSystem.Text.Encodings.Web
>= 4.5.0.(#4399)
Improve perf by avoiding boxing of common status codes values.
(#4360,
#4363)
OpenTelemetry.Instrumentation.Http
Fixed an issue of missing
http.client.duration
metric data in case ofnetwork failures (when response is not available).
(#4098)
Improve perf by avoiding boxing of common status codes values.
(#4361,
#4363)
This discussion was created from the release 1.5.0 / 1.5.0-beta.1.
Beta Was this translation helpful? Give feedback.
All reactions