Microsoft.ApplicationInsights

• BASE: Metrics: Renamed TryTrackValue(..) into TrackValue(..).
• BASE: Metrics: Removed some superfluous public constants.

• NETCORE: Fix - ApplicationInsights StartupFilter should not swallow exceptions from downstream ApplicationBuilder.

• WEB: When there is no parent operation, generate W3C compatible operation Id

• BASE: Allow to set flags on event. It will be used in conjunction with the feature that will allow to keep IP addresses.
• BASE: Fix: SerializationException resolving Activity in cross app-domain calls
• BASE: Make HttpClient instance static to avoid re-creating with every transmission. This had caused connection/memory leaks in .net core 2.1 Related: (https://github.com/Microsoft/ApplicationInsights-aspnetcore/issues/690)

• BASE: Fix: NullReferenceException if telemetry is tracked after TelemetryConfiguration is disposed
• BASE: Move the implementation of the extraction of auto-collected (aka standard) metrics from internal legacy APIs to the recently shipped metric aggregation APIs.
• BASE: Fix: NullReferenceException in ExceptionConverter.GetStackFrame if StackFrame.GetMethod() is null

• BASE: Extend the Beta period for Metrics Pre-Aggregation features shipped in 2.6.0-beta3.
• BASE: New: Added TryGetOperationDetail to DependencyTelemetry to facilitate advanced ITelemetryInitializer scenarios. Allows ITelemetryInitializer implementations to specify fields that would otherwise not be sent automatically to the backend.

• BASE: Revert changed namespace: SamplingPercentageEstimatorSettings, AdaptiveSamplingPercentageEvaluatedCallback
• BASE: Add netstandard2.0 target for TelemetryChannel which doesn't have a dependency on Newtonsoft.Json

• BASE: Extend the Beta period for Metrics Pre-Aggregation features shipped in 2.6.0-beta3.
• BASE: Fix: changed namespace SamplingPercentageEstimatorSettings

• BASE: New: Enable ExceptionTelemetry.SetParsedStack for .Net Standard
• BASE: Fix: TelemetryClient throws NullReferenceException on Flush if the underlying configuration was disposed

• BASE: Report internal errors from Microsoft.AspNet.TelemteryCorrelation module
• BASE: Fix: Telemetry tracked with StartOperation is tracked outside of corresponding activity's scope
• BASE: Fix: TelemetryProcessor chain building should also initialize Modules.
• BASE: Fix: Wrong error message in AutocollectedMetricsExtractor.
• BASE: NEW: Interface and Configuration: IApplicationIdProvider.
• BASE: NEW: Metrics Pre-Aggregation: New TelemetryClient.GetMetric(..).TrackValue(..) and related APIs always locally pre-aggregate metrics before sending. They are replacing the legacy TelemetryClient.TrackMetric(..) APIs. (More info.)

• BASE: Changed signature of TelemetryClient.TrackDependency
• BASE: Added overload of TelemetryClientExtensions.StartOperation(Activity activity).
• BASE: Finalize the architecture for adding default heartbeat properties (supporting proposal from Issue #636)..

• BASE: Fix for missing TelemetryContext. Thank you to our community for discovering and reporting this issue! Logic bug within Initialize() in TelemetryContext, Dependency correlation is broken after upgrade to .NET SDK 2.5, Lost many context fields in 2.5.0

• WEB: Fix: System.InvalidCastException for SQL Dependency

• BASE: Remove calculation of sampling-score based on Context.User.Id Issue #625
• BASE: New sdk-driven "heartbeat" functionality added which sends health status at pre-configured intervals. See extending heartbeat properties doc for more information
• BASE: Fixes a bug in ServerTelemetryChannel which caused application to crash on non-windows platforms. Details on fix and workaround #654 Original issue (https://github.com/Microsoft/ApplicationInsights-aspnetcore/issues/551)
• BASE: Fixed a bug with the AdaptiveSamplingTelemetryProcessor that would cause starvation over time. Issue #756 (dotnet-server)
• BASE: Updated solution to build on Mac!

• BASE: Method Sanitize on classes implementing ITelemetry no longer modifies the TelemetryContext fields. Serialized event json and ETW event will still have context tags sanitized.
• BASE: Application Insights SDK supports multiple telemetry sinks. You can configure more than one channel for telemetry now.
• BASE: New method DeepClone on ITelemetry interface. Implemented by all supported telemetry items.
• BASE: Server telemetry channel NuGet support a netstandard1.3 target with fixed rate sampling and adaptive sampling telemetry processors.
• BASE: 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.
• BASE: .NET 4.0 targets were removed. Please use the version 2.4.0 if you cannot upgrade your application to the latest framework version.
• BASE: Removed wp8, portable-win81+wpa81 and uap10.0 targets.

• BASE: Updated version of DiagnosticSource to 4.4.0 stable

• BASE: Updated version of DiagnosticSource referenced.

• BASE: Made Metric class private and fixed various metrics related issues.

• WEB: Exceptions statistics feature is not enabled by default
• WEB: Parse AppId from HTTP response headers when dependency collection is facilitated with Http Desktop DiagnosticSource
• WEB: Fix double correlation header injection with latest DiagnosticSource
• WEB: DisableDiagnosticSourceInstrumentation configuration flag was added to DependencyTrackingTelemetryModule.
  • By default DisableDiagnosticSourceInstrumentation is set to false, this enables correlation of telemetry items and application map in multi-tier applications.
  • When DisableDiagnosticSourceInstrumentation is set to true (so that the instrumentation is off)
    • correlation between requests, dependencies, and other telemetry items is limited,
    • telemetry correlation between multiple services involved in the operation processing is not possible,
    • and the cross-component correlation feature and application map experience is limited.
  • Note: this configuration option has no effect for applications that run in an Azure Web Application with the ApplicationInsights site extension or have runtime instrumentation.
• WEB: Fix memory leak in Dependency collector

• BASE: Removed metric aggregation functionality as there is not enough feedback on the API surface yet.

• BASE: 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.
• BASE: Added dependency on System.Diagnostics.DiagnosticsSource package. It is still possible to use standalone Microsoft.ApplicationInsights.dll to track telemetry.
• BASE: 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.
• BASE: 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
• BASE: Request.Success field will not be populated based on ResponseCode. It needs to be set explicitly.
• BASE: New "ProblemId" property on ExceptionTelemetry. It can be used to set a custom ProblemId value.
• BASE: Metric Aggregation functionality (originally added in 2.3.0-beta1 but removed in 2.3.0) is re-introduced.
• BASE: Improved exception stack trace data collection for .NET Core applications.

• BASE: Includes all changes since 2.2.0 stable release.
• BASE: Removed metric aggregation functionality added in 2.3.0-beta1 release.
• BASE: Fixed a bug which caused SDK to stop sending telemetry.

• BASE: Added overloads of TelemetryClientExtensions.StartOperation.
• BASE: Fire new ETW events for Operation Start/Stop.

• BASE: 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.
• BASE: 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.

• BASE: Added metric aggregation functionality via MetricManager and Metric classes.
• BASE: Exposed a source field on RequestTelemetry. This can be used to store a representation of the component that issued the incoming http request.

• BASE: Includes all changes since 2.1.0 stable release.

• BASE: Added serialization of the "source" property.
• BASE: Downgraded package dependencies to Microsoft.NETCore.App 1.0.1 level.
• BASE: Fixed the priority of getting an iKey from an environment variable

• BASE: Payload sanitization for RichPayloadEventSource.
• BASE: Fix to fallback to an environment variable for instrumentation key when not specified when initializing TelemetryConfiguration.
• BASE: RoleInstance and NodeName are initialized with the machine name by default.

• BASE: InMemoryChannel has a new override for Flush method that accepts timeout.
• BASE: Local storage folder name was changed. That means that when the application stopped, and the application was updated to the new SDK, then the telemetry from the old local folder will not be send.
• BASE: Allow all characters in property names and measurements names.
• BASE: AdaptiveTelemetryProcessor has a new property IncludedTypes. It gets or sets a semicolon separated list of telemetry types that should be sampled. If left empty all types are included implicitly. Types are not included if they are set in ExcludedTypes.
• BASE: Richpayload event source event is generated for all framework versions of SDK (before it was supported in 4.6 only)
• BASE: TelemetryClient has a new method TrackAvailability. Data posted using this method would be available in AppAnalitics only, Azure portal UI is not available at this moment.

• BASE: Add ExceptionTelemetry.Message property. If it is provided it is used instead of Exception.Message property for the outer-most exception.
• BASE: Telemetry types can be excluded from sampling by specifing ExcludedTypes property.
• BASE: ServerTelemetryChannel: changed backoff logic to be less aggressive, added diagnostics event when backoff logic kicks in and added more tracing. (Done to address issues when data stops flowing till application gets restarted)

• NETCORE: Updated SDK version dependency to 2.4.0.
• NETCORE: Fixed a minor logging message issue.
• NETCORE: Fixed unit test reliability issues.

• BASE: Bug fix

• BASE: Support partial success (206) from the Application Insights backend. Before this change SDK may have lost data because some items of the batch were accepted and some items of the batch were asked to be retried (because of burst throttling or intermittent issues).
• BASE: Bug fixes

• BASE: Upgraded to depend on EventSource.Redist nuget version 1.1.28
• BASE: Upgraded to depend on Microsoft.Bcl nuget version 1.1.10

• BASE: Add Win Phone, Win Store and UWP targets that include 1.2.3 version of ApplicationInsights.dll. It is included to prevent applications that upgrade to 2.0.0 from crashing. In any case using this nuget for Win Phone, Win Store and UWP targets is not recommended and not supported.

• BASE: Disallow Nan, +-Infinity measurements. Value will be replaced on 0.
• BASE: Disallow Nan, +-Infinity metrics (Value, Min, Max and StandardDeviation). Values will be replaced on 0.

• BASE: 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.
• BASE: DependencyTelemetry.Async property was removed.
• BASE: DependencyTelemetry.Count property was removed.
• BASE: When configuration is loaded from ApplicationInsights.config incorrect and broken elements are skipped. That includes both high level elements like TelemetryInitializers as well as individual properties.
• BASE: Internal Application Insights SDK traces will be marked as synthetic and have SyntheticSource equals to 'SDKTelemetry'.
• BASE: UserContext.AcquisitionDate property was removed.
• BASE: UserContext.StoreRegion property was removed.
• BASE: InMemoryChannel.DataUploadIntervalInSeconds was removed. Use SendingInterval instead.
• BASE: DeviceContext.RoleName was removed. Use DeviceContext.Cloud.RoleName instead.
• BASE: DeviceContext.RoleInstance was removed. Use DeviceContext.Cloud.RoleInstance instead.

• BASE: UseSampling and UseAdaptiveSampling extensions were moved to Microsoft.ApplicationInsights.Extensibility
• BASE: Cut Phone and Store support
• BASE: Updated DependencyTelemetry to have new properties ResultCode and Id
• BASE: If ServerTelemetryChannel 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).
• BASE: 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.
• BASE: TelemetryConfiguration.GetTelemetryProcessorChainBuilder extension method is removed. Instead of this method use TelemetryConfiguration.TelemetryProcessorChainBuilder instance method.
• BASE: TelemetryConfiguration has a new property TelemetryProcessors that gives readonly access to TelemetryProcessors collection.
• BASE: Use, UseSampling and UseAdaptiveSampling preserves TelemetryProcessors loaded from configuration.

• BASE: Adaptive sampling turned on by default in server telemetry channel. Details can be found in #80.
• BASE: Fixed signature of UseSampling to allow chaining with other calls to Use of telemetry processors.
• BASE: Property Request.ID returned back. OperationContext now has a property ParentId for end-to-end correlation.
• BASE: TimestampTelemetryInitializer is removed. Timestamp will be added automatically by TelemetryClient.
• BASE: OperationCorrelationTelemetryInitializer is added by default to enable operaitons correlation.

• BASE: Fix UI thread locking when initializing InMemoryChannel (default channel) from UI thread.
• BASE: Added support for ITelemetryProcessor and ability to construct chain of TelemetryProcessors via code or config.
• BASE: Version of Microsoft.ApplicationInsights.dll for the framework 4.6 is now part of the package.
• BASE: IContextInitializer interface is not supported any longer. ContextInitializers collection was removed from TelemetryConfiguration object.
• BASE: The max length limit for the Name property of EventTelemetry was set to 512.
• BASE: Property Name of OperationContext was renamed to RootName
• BASE: Property Id of RequestTelemetry was removed.
• BASE: Property Id and Context.Operation.Id of RequestTelemetry would not be initialized when creating new RequestTelemetry.
• BASE: New properties of OperationContext: CorrelationVector, ParentId and RootId to support end-to-end telemetry items correlation.

• BASE: TrackDependency will produce valid JSON when not all required fields were specified.
• BASE: Redundant property RequestTelemetry.ID is now just a proxy for RequestTelemetry.Operation.Id.
• BASE: New interface ISupportSampling and explicit implementation of it by most of data item types.
• BASE: Count property on DependencyTelemetry marked as Obsolete. Use SamplingPercentage instead.
• BASE: New CloudContext introduced and properties RoleName and RoleInstance moved to it from DeviceContext.
• BASE: New property AuthenticatedUserId on UserContext to specify authenticated user identity.

• BASE: Bug fixes.
• BASE: Telemetry item will be serialized to Debug Output even when Instrumentation Key was not set.

Web:

• WEB: Telemetry initializers that do not have dependencies on ASP.NET libraries were moved to the new dependency nuget "Microsoft.ApplicationInsights.WindowsServer"
• WEB: Microsoft.ApplicationInsights.Web.dll was renamed on Microsoft.AI.Web.dll
• WEB: Microsoft.Web.TelemetryChannel nuget was renamed on Microsoft.WindowsServer.TelemetryChannel. TelemetryChannel assembly was also renamed.
• WEB: All namespaces that are part of Web SDK were changed to exlude "Extensibility" part. That incudes all telemetry initializers in applicationinsights.config and ApplicationInsightsWebTracking module in web.config.

Dependencies:

• WEB: Dependencies collected using runtime instrumentaiton agent (enabled via Status Monitor or Azure WebSite extension) will not be marked as asynchronous if there are no HttpContext.Current on the thread.
• WEB: Property SamplingRatio of DependencyTrackingTelemetryModule does nothing and marked as obsolete.

Performance Counters

• WEB: Microsoft.ApplicationInsights.Extensibility.PerfCounterCollector assembly was renamed on Microsoft.AI.PerfCounterCollector

WindowsServer

• WEB: First version of the package. The package has common logic that will be shared between Web and Non-Web Windows applications.

Web:

• WEB: Moved telemetry initializers and telemetry modules from separate sub-namespaces to the root Microsoft.ApplicationInsights.Extensibility.Web namespace.
• WEB: Removed "Web" prefix from names of telemetry initializers and telemetry modules because it is already included in the Microsoft.ApplicationInsights.Extensibility.Web namespace name.
• WEB: Moved DeviceContextInitializer from the Microsoft.ApplicationInsights assembly to the Microsoft.ApplicationInsights.Extensibility.Web assembly and converted it to an ITelemetryInitializer.

Dependencies:

• WEB: Change namespace and assembly names from Microsoft.ApplicationInsights.Extensibility.RuntimeTelemetry to Microsoft.ApplicationInsights.Extensibility.DependencyCollector for consistency with the name of the NuGet package.
• WEB: Rename RemoteDependencyModule to DependencyTrackingTelemetryModule.

Performance Counters

• WEB: Rename 'CustomPerformanceCounterCollectionRequest' to 'PerformanceCounterCollectionRequest'.