NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
NuGet, #37 most downloaded on NuGet
Application Insights Base API. This package provides core functionality for transmission of all Application Insights Telemetry Types and is a dependent package for all other Application Insights packages. Please install the platform specific package for the best experience. Privacy statement: https://go.microsoft.com/fwlink/?LinkId=512156
Latest stable
3.2.0
Last release 1 months ago
09 Oct 2026
Release timing varies
gaps range from 3 weeks to 1.4 years
Nearly every release is documented
notes for 43 of 43 stable releases
88 versions withdrawn
withdrawn after publishing
127 years old
132 releases · first in 1900
Drag across the ruler to compare, or tap a release to open it.
TelemetryProcessors (sampling, autocollectedmetricaggregator), TelemetryChannel (ServerTelemetryChannel) added automatically to the default Applicatio
Your coding agent can read these notes before it upgrades. Set up the MCP server →
Add a new distict properties collection, GlobalProperties, on TelemetryContext, and obsolete the Properties on TelemetryContext.
ExceptionDetailsInfoList on ExceptionTelemetry class that gives control to user to update exception
message and exception type of underlying System.Exception object that user wants to send to telemetry. Related discussion is here.ExceptionDetailsInfoList on ExceptionTelemetry class that gives control to user to update exception
message and exception type of underlying System.Exception object that user wants to send to telemetry. Related discussion is here.BASE: Metrics: Renamed TryTrackValue(..) into TrackValue(..).
NETCORE: Fix - ApplicationInsights StartupFilter should not swallow exceptions from downstream ApplicationBuilder.
WEB: When there is no parent operation, generate W3C compatible operation Id
Allow to set flags on event. It will be used in conjunction with the feature that will allow to keep IP addresses.
Fix: NullReferenceException if telemtery is tracked after TelemetryConfiguration is disposed
Extend the Beta period for Metrics Pre-Aggregation features shipped in 2.6.0-beta3.
Revert changed namespace: `SamplingPercentageEstimatorSettings`, `AdaptiveSamplingPercentageEvaluatedCallback`
Nothing published for this version
Extend the Beta period for Metrics Pre-Aggregation features shipped in 2.6.0-beta3.
Extend the Beta period for Metrics Pre-Aggregation features shipped in 2.6.0-beta3.
New: Enable ExceptionTelemetry.SetParsedStack for .Net Standard
Report internal errors from Microsoft.AspNet.TelemteryCorrelation module
TelemetryClient.GetMetric(..).TrackValue(..) and related APIs always locally pre-aggregate metrics before sending. They are replacing the legacy TelemetryClient.TrackMetric(..) APIs. (More info.)TelemetryClient.GetMetric(..).TrackValue(..) and related APIs always locally pre-aggregate metrics before sending. They are replacing the legacy TelemetryClient.TrackMetric(..) APIs. (More info.)Changed signature of TelemetryClient.TrackDependency
Fix for missing TelemetryContext. Thank you to our community for discovering and reporting this issue! Logic bug within Initialize() in TelemetryConte
WEB: Fix: System.InvalidCastException for SQL Dependency
Remove calculation of sampling-score based on Context.User.Id Issue #625
AdaptiveSamplingTelemetryProcessor that would cause starvation over time. Issue #756 (dotnet-server)AdaptiveSamplingTelemetryProcessor that would cause starvation over time. Issue #756 (dotnet-server)Method Sanitize on classes implementing ITelemetry no longer modifies the TelemetryContext fields. Serialized event json and ETW event will still have
Sanitize on classes implementing ITelemetry no longer modifies the TelemetryContext fields. Serialized event json and ETW event will still have context tags sanitized.DeepClone on ITelemetry interface. Implemented by all supported telemetry items.wp8, portable-win81+wpa81 and uap10.0 targets.Sanitize on classes implementing ITelemetry no longer modifies the TelemetryContext fields. Serialized event json and ETW event will still have context tags sanitized.DeepClone on ITelemetry interface. Implemented by all supported telemetry items.wp8, portable-win81+wpa81 and uap10.0 targets.Includes all changes since 2.3.0 stable release. Updated reference to System.Diagnostics.DiagnosticSource version 4.4.0
Includes all changes since 2.3.0 stable release. Updated reference to System.Diagnostics.DiagnosticSource version 4.4.0
BASE: Updated version of DiagnosticSource referenced.
This release contains the following changes:
This release contains the following changes:
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).
No product changes since beta2. Named changed to beta3 for consistent naming with ApplicationInsights Web SDK
DisableDiagnosticSourceInstrumentation configuration flag was added to DependencyTrackingTelemetryModule.
DisableDiagnosticSourceInstrumentation is set to false, this enables correlation of telemetry items and application map in multi-tier applications.DisableDiagnosticSourceInstrumentation is set to true (so that the instrumentation is off)
Removed metric aggregation functionality as there is not enough feedback on the API surface yet.
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
ApplicationInsights.config file to revert to the previous behavior.Request.Success field will not be populated based on ResponseCode. It needs to be set explicitly.ApplicationInsights.config file to revert to the previous behavior.Request.Success field will not be populated based on ResponseCode. It needs to be set explicitly.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 t
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.
Added overloads of TelemetryClientExtensions.StartOperation. Fire new ETW events for Operation Start/Stop.
Added overloads of TelemetryClientExtensions.StartOperation. Fire new ETW events for Operation Start/Stop.
Added constructor overloads for TelemetryConfiguration and added creation of a default InMemoryChannel when no channel is specified for a new instance
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
Added metric aggregation functionality via MetricManager and Metric classes.
Includes all changes since 2.1.0 stable release.
Added serialization of the "source" property.
Payload sanitization for RichPayloadEventSource.
NetworkType, ScreenResolution and Language marked as obsolete. Please use custom properties to report network type, screen resolution and language. Values stored in these properties will be send as custom properties.Target. CommandName was renamed to Data for consistancy with the Application Analytics schema. DependencyKind will never be send any more and will not be set to "Other" by default. Also there are two more constructors for DependencyTelemetry item.SessionStateTelemetry was marked obsolete. Use IsFirst flag in SessionContext to indicate that the session is just started.PerformanceCounterTelemetry was marked obsolete. Use MetricTelemetry instead.RequestTelemetry.HttpMethod as obsolete. Put http verb as part of the name for the better grouping by name and use custom properties to report http verb as a dimension.RequestTelemetry.StartTime as obsolete. Use TimeStamp instead.InMemoryChannel has a new override for Flush method that accepts timeout.
Add ExceptionTelemetry.Message property. If it is provided it is used instead of Exception.Message property for the outer-most exception.
NETCORE: Updated SDK version dependency to 2.4.0.
- Bug fix
Support partial success (206) from the Application Insights backend. Before this change SDK may have lost data because some items of the batch were ac
Upgraded to depend on EventSource.Redist nuget version 1.1.28
No code changes. Added Win Phone, Win Store and UWP targets that include 1.2.3 version of ApplicationInsights.dll. It is included to prevent applicati
Disallow Nan, +-Infinity measurements. Value will be replaced on 0.
•Writing telemetry items to debug output can be disabled with IsTracingDisabled property on TelemetryDebugWriter . Telemetry items that were filtered
•Writing telemetry items to debug output can be disabled with IsTracingDisabled property on TelemetryDebugWriter . Telemetry items that were filtered out by sampling are now indicated in debug output. Custom telemetry processors can now invoke method WriteTelemetry on TelemetryDebugWriter with filteredBy parameter to indicate in debug output that an item is being filtered out. •DependencyTelemetry.Async property was removed. •DependencyTelemetry.Count property was removed. •When configuration is loaded from ApplicationInsights.config incorrect and broken elements are skiped. That includes both high level evelemts like TelemetryInitializers as well as individual properties. •Internal Application Insights SDK traces will be marked as synthetic and have SyntheticSource equals to 'SDKTelemetry'. •UserContext.AcquisitionDate property was removed. •UserContext.StoreRegion property was removed. •InMemoryChannel.DataUploadIntervalInSeconds was removed. Use SendingInterval instead. •DeviceContext.RoleName was removed. Use DeviceContext.Cloud.RoleName instead. •DeviceContext.RoleInstance was removed. Use DeviceContext.Cloud.RoleInstance instead.
Known Issue: https://github.com/Microsoft/ApplicationInsights-dotnet/issues/200
IsTracingDisabled property on TelemetryDebugWriter.
Telemetry items that were filtered out by sampling are now indicated in debug output. Custom telemetry processors can now invoke
method WriteTelemetry on TelemetryDebugWriter with filteredBy parameter to indicate in debug output that an
item is being filtered out.SyntheticSource equals to 'SDKTelemetry'.•Removed support for Universal Windows Phone and Store applications •Updated DependencyTelemetry to have new properties ResultCode and Id. ResultCode
•Removed support for Universal Windows Phone and Store applications •Updated DependencyTelemetry to have new properties ResultCode and Id. ResultCode will be used to provide HTTP response code for HTTP dependencies and error code for SQL dependencies. Id will be used for cross-component correlation. •If ServerTelemetryChannel is initialized programmatically it is now required to call ServerTelemetryChannel.Initialize() method. Otherwise persistent storage will not be initialized (that means that if telemetry cannot be sent in the event of temporary connectivity issues, it will be dropped). •ServerTelemetryChannel has new property StorageFolder that can be set either through code or through configuration. If this property is set, ApplicationInsights uses provided location to store telemetry that was not sent in the event of temporary connectivity issues. If property is not set, or provided folder is inaccessible, ApplicationInsights will try to use LocalAppData or Temp folders as it was done before. •TelemetryConfiguration.GetTelemetryProcessorChainBuilder extension method is removed. Instead of this method use TelemetryConfiguration.TelemetryProcessorChainBuilder instance method. •TelemetryConfiguration class has a new property TelemetryProcessors that gives readonly access to TelemetryProcessors collection.
DependencyTelemetry to have new properties ResultCode and IdServerTelemetryChannel is initialized programmatically it is required to call ServerTelemetryChannel.Initialize() method. Otherwise persistent storage will not be initialized (that means that if telemetry cannot be sent because of temporary connectivity issues it will be dropped).ServerTelemetryChannel has new property StorageFolder that can be set either through code or though configuration. If this property is set ApplicationInsights uses provided location to store telemetry that was not sent because of temporary connectivity issues. If property is not set or provided folder is inaccessible ApplicationInsights will try to use LocalAppData or Temp as it was done before.Use, UseSampling and UseAdaptiveSampling preserves TelemetryProcessors loaded from configuration.Property Request.ID returned back. OperationContext now has a property ParentId for end-to-end coorrelation. •TimestampTelemetryInitializer is removed
UseSampling to allow chaining with other calls to Use of telemetry processors.Request.ID returned back. OperationContext now has a property ParentId for end-to-end correlation.TimestampTelemetryInitializer is removed. Timestamp will be added automatically by TelemetryClient.OperationCorrelationTelemetryInitializer is added by default to enable operaitons correlation.BASE: Fix UI thread locking when initializing InMemoryChannel (default channel) from UI thread.
ITelemetryProcessor and ability to construct chain of TelemetryProcessors via code or config.Microsoft.ApplicationInsights.dll for the framework 4.6 is now part of the package.Name property of EventTelemetry was set to 512.Name of OperationContext was renamed to RootNameId of RequestTelemetry was removed.Id and Context.Operation.Id of RequestTelemetry would not be initialized when creating new RequestTelemetry.OperationContext: CorrelationVector, ParentId and RootId to support end-to-end telemetry items correlation.https://www.nuget.org/packages/Microsoft.ApplicationInsights/2.0.0-beta1
https://www.nuget.org/packages/Microsoft.ApplicationInsights/2.0.0-beta1
RequestTelemetry.ID is now just a proxy for RequestTelemetry.Operation.Id.ISupportSampling and explicit implementation of it by most of data item types.Count property on DependencyTelemetry marked as Obsolete. Use SamplingPercentage instead.CloudContext introduced and properties RoleName and RoleInstance moved to it from DeviceContext.AuthenticatedUserId on UserContext to specify authenticated user identity.Nothing published for this version
BASE: Telemetry item will be serialized to Debug Output even when Instrumentation Key was not set.
Nothing published for this version
BASE: First version shipped from github
Nothing published for this version
BASE: SDK now introduces new telemetry type `DependencyTelemetry` which contains information about dependency call from application
DependencyTelemetry which contains information about dependency call from applicationTelemetryClient.TrackDependency allows to send information about dependency calls from applicationNothing published for this version
WEB: Moved telemetry initializers and telemetry modules from separate sub-namespaces to the root Microsoft.ApplicationInsights.Extensibility.Web names
Web:
Microsoft.ApplicationInsights.Extensibility.Web namespace.Microsoft.ApplicationInsights.Extensibility.Web namespace name.DeviceContextInitializer from the Microsoft.ApplicationInsights assembly to the
Microsoft.ApplicationInsights.Extensibility.Web assembly and converted it to an ITelemetryInitializer.Dependencies:
Microsoft.ApplicationInsights.Extensibility.RuntimeTelemetry to
Microsoft.ApplicationInsights.Extensibility.DependencyCollector for consistency with the name of the NuGet package.RemoteDependencyModule to DependencyTrackingTelemetryModule.Performance Counters
Nothing published for this version
Nothing published for this version
BASE: Application Insights now distributes separate binaries for framework 4.0 and 4.5. Library for the framework 4.5 will not require EventSource and
packages.config. It should be <package id="Microsoft.ApplicationInsights" version="0.17.*" targetFramework="net45" /><Add Type="Microsoft.ApplicationInsights.Extensibility.Implementation.Tracing.DiagnosticsTelemetryModule, Microsoft.ApplicationInsights" /> to <TelemetryModules> node to get SDK self-diagnostics messages from your application.ITelemetryChannel interface became a nullable bool.Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
One column per quarter.