Repository navigation
Releases
Instrumentation.Kusto-0.1.0-alpha.10
-
NuGet: OpenTelemetry.Instrumentation.Kusto v0.1.0-alpha.10
- Fix query summarization taking quadratic time relative to the nesting depth
of queries with syntax errors, such as deeply nested unterminated calls.
(#6068)
See CHANGELOG for details.
- Fix query summarization taking quadratic time relative to the nesting depth
Resources.AWS-1.21.0
-
NuGet: OpenTelemetry.Resources.AWS v1.21.0
-
Add
SemanticConventionVersion.V1_45_0, which
SemanticConventionVersion.Latestnow maps to. There are no changes to the
attributes emitted by the resource detectors.
(#5832) -
Breaking Change Dropped support for
net8.0andnet9.0.
(#3867) -
Add support for .NET 11.0.
(#3867) -
Updated OpenTelemetry core component version(s) to
1.21.0.
(#5969)
See CHANGELOG for details.
-
PersistentStorage-1.2.0
-
NuGet: OpenTelemetry.PersistentStorage.Abstractions v1.2.0
See CHANGELOG for details.
-
NuGet: OpenTelemetry.PersistentStorage.FileSystem v1.2.0
-
Hardened
FileBlobProvider.- Breaking: When running on .NET on non-Windows platforms, creating a
FileBlobProvidernow throws anUnauthorizedAccessExceptionif its
storage directory could be changed by another user. The directory must be
owned by the current user and must not be writable by its group or by
other users. Each directory and symbolic link in its path must be owned by
the current user or by root, and those directories must not be writable
by their group or by other users unless they have the sticky bit set (such
as/tmp). The directory is verified again before blobs are listed,
created or removed, and no blobs are returned or read from it if it can
no longer be trusted. These checks can be disabled by using the new
FileBlobProvider(string path, bool checkPermissions)constructor with
checkPermissionsset tofalse. - A relative storage path is now resolved when the
FileBlobProvideris
created, so that the directory that is verified is always the directory
that is used, even if the current directory of the process is changed. - Blobs that are empty or that are larger than the maximum size of the
storage are no longer read. When running on .NET, blobs that are symbolic
links are also no longer read. - Fixed a blob write being accepted when it would cause the storage to exceed
its maximum size. - Writing content that is larger than the maximum size of the storage to a
FileBlobis now rejected, instead of replacing its existing content with
content that cannot be read.
(#5949)
- Breaking: When running on .NET on non-Windows platforms, creating a
-
Breaking Change Dropped support for
net8.0andnet9.0.
(#3867) -
Add support for .NET 11.0.
(#3867)
See CHANGELOG for details.
-
Instrumentation.SqlClient-1.21.0
-
NuGet: OpenTelemetry.Instrumentation.SqlClient v1.21.0
-
Breaking Change Dropped support for
net8.0andnet9.0.
(#3867) -
Add support for .NET 11.0.
(#3867) -
Updated OpenTelemetry core component version(s) to
1.21.0.
(#5969)
See CHANGELOG for details.
-
Instrumentation.Runtime-1.21.0
-
NuGet: OpenTelemetry.Instrumentation.Runtime v1.21.0
-
Breaking Change Dropped support for
net8.0andnet9.0.
(#3867) -
Add support for .NET 11.0.
(#3867) -
Updated OpenTelemetry core component version(s) to
1.21.0.
(#5969)
See CHANGELOG for details.
-
Instrumentation.Http-1.21.0
-
NuGet: OpenTelemetry.Instrumentation.Http v1.21.0
-
Breaking Change Dropped support for
net8.0andnet9.0.
(#3867) -
Add support for .NET 11.0.
(#3867) -
Updated OpenTelemetry core component version(s) to
1.21.0.
(#5969)
See CHANGELOG for details.
-
Instrumentation.AspNetCore-1.21.0
-
NuGet: OpenTelemetry.Instrumentation.AspNetCore v1.21.0
-
Breaking Change Dropped support for
net8.0andnet9.0.
(#3867) -
Add support for .NET 11.0.
(#3867) -
Updated OpenTelemetry core component version(s) to
1.21.0.
(#5969)
See CHANGELOG for details.
-
Instrumentation.AspNet-1.21.0
-
NuGet: OpenTelemetry.Instrumentation.AspNet v1.21.0
-
Breaking Change Dropped support for
net8.0andnet9.0.
(#3867) -
Add support for .NET 11.0.
(#3867) -
Updated OpenTelemetry core component version(s) to
1.21.0.
(#5969)
See CHANGELOG for details.
-
-
NuGet: OpenTelemetry.Instrumentation.AspNet.TelemetryHttpModule v1.21.0
-
Preserve baggage updates between request steps when the execution context is
lost.
(#5948) -
Breaking Change Dropped support for
net8.0andnet9.0.
(#3867) -
Add support for .NET 11.0.
(#3867) -
Updated OpenTelemetry core component version(s) to
1.21.0.
(#5969)
See CHANGELOG for details.
-
Instrumentation.AWS-1.21.0
-
NuGet: OpenTelemetry.Extensions.AWS v1.21.0
-
Breaking Change Dropped support for
net8.0andnet9.0.
(#3867) -
Add support for .NET 11.0.
(#3867) -
Updated OpenTelemetry core component version(s) to
1.21.0.
(#5969)
See CHANGELOG for details.
-
-
NuGet: OpenTelemetry.Instrumentation.AWS v1.21.0
-
Fixed SQS and SNS
MessageAttributesthat are reused across sends carrying
the trace context and baggage of the first send. The instrumentation no longer
modifies the application'sMessageAttributesdictionary, and the request's
MessageAttributesis now a different instance after a send.
(#5867) -
Breaking Change: Update latest AWS Semantic Conventions to 1.45.0
(SemanticConventionVersion.V1_45_0). SNS and SQS spans now use
messaging.system.nameinstead ofmessaging.system, and SQS spans use the
valueaws.sqsinstead ofaws_sqs. Spans for sending a single message
(SQS.SendMessageandSNS.Publish) now useActivityKind.Producerwhen
their context is injected into the message. Messages with an existing creation
context retainActivityKind.Clientand link to that context. Messages that
the context cannot be injected into, such as those that already have the
maximum number of message attributes or an attribute with the same name as one
that would be injected, also useActivityKind.Client, with no link. Spans for
SendMessageBatchandPublishBatchnow setmessaging.batch.message_count,
as do spans forReceiveMessagewith the number of messages received.
(#5832) -
Breaking Change Dropped support for
net8.0andnet9.0.
(#3867) -
Add support for .NET 11.0.
(#3867)
See CHANGELOG for details.
-
-
NuGet: OpenTelemetry.Instrumentation.AWSLambda v1.21.0
-
Breaking Change: Update latest AWS Semantic Conventions to 1.45.0
(SemanticConventionVersion.V1_45_0). Spans now usefaas.invocation.id
instead offaas.invocation_id.
(#5832) -
Breaking Change Dropped support for
net8.0andnet9.0.
(#3867) -
Add support for .NET 11.0.
(#3867)
See CHANGELOG for details.
-
Exporter.OneCollector-1.21.0
-
NuGet: OpenTelemetry.Exporter.OneCollector v1.21.0
-
Fixed an issue where validating a logger category name (event namespace)
that is not a valid OneCollector event namespace could take an extremely long
time (growing exponentially with the length of the name), blocking log export.
For example, category names containing a-,_,`, or<after a
long run of letters.
(#5917) -
Fixed an issue where event names and logger category names that are replaced
by a default or anEventFullNameMappingsrule (and preserved in the
namespace/namedata fields), or supplied via{EventFullName}, were
written to the JSON payload without encoding. Names containing quotes,
backslashes, control characters, or non-ASCII characters produced malformed
or invalid UTF-8 JSON, and names longer than 126 characters caused the whole
batch to fail to export. Event namespace and event name validation no longer
accepts a trailing newline. Also fixed an issue where an original event name
could be attached to unrelated log records which resolved to the default
event name, or to records whose original name differed only by case.
(#5916) -
Breaking Change Dropped support for
net8.0andnet9.0.
(#3867) -
Add support for .NET 11.0.
(#3867) -
Updated OpenTelemetry core component version(s) to
1.21.0.
(#5969)
See CHANGELOG for details.
-