Releases: microsoft/ApplicationInsights-dotnet
v2.5.0-beta1 (2.5.0-28646)
- Method
Sanitize
on classes implementingITelemetry
no longer modifies theTelemetryContext
fields. Serialized event json and ETW event will still have context tags sanitized. - Application Insights SDK supports multiple telemetry sinks. You can configure more than one channel for telemetry now.
- New method
DeepClone
onITelemetry
interface. Implemented by all supported telemetry items. - Server telemetry channel NuGet support a netstandard1.3 target with fixed rate sampling and adaptive sampling telemetry processors.
- Instrumentation key is no longer required for TelemetryClient to send data to channel(s). This makes it easier to use the SDK with channels other than native Application Insights channels.
- .NET 4.0 targets were removed. Please use the version 2.4.0 if you cannot upgrade your application to the latest framework version.
- Removed
wp8
,portable-win81+wpa81
anduap10.0
targets.
v2.4.0 (2.4.0-32153)
Includes all changes since 2.3.0 stable release.
Updated reference to System.Diagnostics.DiagnosticSource version 4.4.0
v2.4.0-beta4 (2.4.0-22343)
This release contains the following changes:
- Made Metric class private and fixed various metrics related issues.
You should also include an explicit reference to System.Diagnostics.DiagnosticSource 4.4.0-preview2-25330-01 since it contains a critical bug fix this release relies on (you can remove this reference when 2.4.0 stable ships with an updated reference).
v2.4.0-beta3 (2.4.0-16630)
- No product changes since beta2. Named changed to beta3 for consistent naming with ApplicationInsights Web SDK
v2.4.0-beta2 (2.4.0-13745)
- Removed metric aggregation functionality as there is not enough feedback on the API surface yet.
v2.4.0-beta1 (2.4.0-12817)
- Event telemetry is set to be sampled separately from all other telemetry types. It potentially can double the bill. The reason for this change is that Events are mostly used for usage analysis and should not be subject to sampling on high load of requests and dependencies. Edit
ApplicationInsights.config
file to revert to the previous behavior. - Added dependency on System.Diagnostics.DiagnosticsSource package. It is still possible to use standalone Microsoft.ApplicationInsights.dll to track telemetry.
- StartOperation starts a new System.Diagnostics.Activity and stores operation context in it. StartOperation overwrites OperationTelemetry.Id set before or during telemetry initialization for the dependency correlation purposes.
- OperationCorrelationTelemetryInitializer initializes telemetry from the Activity.Current. Please refer to https://github.com/dotnet/corefx/blob/master/src/System.Diagnostics.DiagnosticSource/src/ActivityUserGuide.md for more details about Activity and how to use it
Request.Success
field will not be populated based onResponseCode
. It needs to be set explicitly.- New "ProblemId" property on ExceptionTelemetry. It can be used to set a custom ProblemId value.
- Metric Aggregation functionality (originally added in 2.3.0-beta1 but removed in 2.3.0) is re-introduced.
- Improved exception stack trace data collection for .NET Core applications.
v2.3.0(2.3.0.41907)
Includes all changes since 2.2.0 stable release.
Removed metric aggregation functionality added in 2.3.0-beta1 release.
Fixed a bug which caused SDK to stop sending telemetry.
v2.3.0-beta3 (2.3.0.32439)
Added overloads of TelemetryClientExtensions.StartOperation.
Fire new ETW events for Operation Start/Stop.
v2.3.0-beta2 (2.3.0.24381)
Added constructor overloads for TelemetryConfiguration and added creation of a default InMemoryChannel when no channel is specified for a new instance. TelemetryClient will no longer create an InMemoryChannel on the configuration instance if TelemetryChannel is null, instead the configuration instances will always have a channel when created.
TelemetryConfiguration will no longer dispose of user provided ITelemetryChannel instances. Users must properly dispose of any channel instances which they create, the configuration will only auto-dispose of default channel instances it creates when none are specified by the user.
All issues from this list:
https://github.com/Microsoft/ApplicationInsights-dotnet/milestone/13?closed=1
v2.3.0-beta1 (2.3.0.9201)
- Added metric aggregation functionality via MetricManager and Metric classes.
- Exposed a source field on RequestTelemetry. This can be used to store a representation of the component that issued the incoming http request.