This repository has been archived by the owner on Nov 27, 2022. It is now read-only.
Update dependency Microsoft.ApplicationInsights.AspNetCore to v2.19.0 #50
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
2.6.1
->2.19.0
Release Notes
Microsoft/ApplicationInsights-dotnet
v2.19.0
Compare Source
v2.18.0
Compare Source
v2.17.0
Compare Source
v2.16.0
Compare Source
v2.15.0
Compare Source
v2.14.0
Compare Source
v2.13.1
Compare Source
v2.13.0
Compare Source
v2.12.2
Compare Source
v2.12.1
Compare Source
v2.12.0
Version 2.11.0
Version 2.11.0-beta2
Version 2.11.0-beta1
Version 2.10.0
Version 2.10.0-beta4
Version 2.10.0-beta3
Version 2.10.0-beta2
Version 2.9.1
Version 2.9.0
Version 2.9.0-beta3
Version 2.9.0-beta2
Perf Improvements.
Version 2.8.1
Patch release addressing perf regression.
Version 2.8.0
Change Duration from string to TimeSpan in autogenerated internal class. microsoft/ApplicationInsights-dotnet#927
Store Metric Aggregation metadata into a field rather than properties dictionary to improve performance microsoft/ApplicationInsights-dotnet#930
Lazily Instantiate ConcurrentDictionaries to improve performance microsoft/ApplicationInsights-dotnet#934
Version 2.8.0-beta2
If you are upgrading, and have added/modified TelemetryProcessors/TelemetryChannel, make sure to copy them to the default sink section.
Version 2.8.0-beta1
(continuation of Strong typed extensibility for Telemetry types microsoft/ApplicationInsights-dotnet#871)
ExceptionDetailsInfoList
onExceptionTelemetry
class that gives control to user to update exceptionmessage and exception type of underlying
System.Exception
object that user wants to send to telemetry. Related discussion is here.Version 2.7.2
Version 2.7.0-beta3
Related: (CPU usage slowly increases over time microsoft/ApplicationInsights-aspnetcore#690)
Version 2.7.0-beta2
Version 2.7.0-beta1
version 2.6.4
SamplingPercentageEstimatorSettings
,AdaptiveSamplingPercentageEvaluatedCallback
Version 2.6.1
Version 2.6.0-beta4
Version 2.6.0-beta3
TelemetryClient.GetMetric(..).TrackValue(..)
and related APIs always locally pre-aggregate metrics before sending. They are replacing the legacyTelemetryClient.TrackMetric(..)
APIs. (More info.)Version 2.6.0-beta2
Version 2.5.1
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
Version 2.5.0-beta2
Details on fix and workaround #654
Original issue (TelemetryChannel for Linux microsoft/ApplicationInsights-aspnetcore#551)
AdaptiveSamplingTelemetryProcessor
that would cause starvation over time. Issue #756 (dotnet-server)Version 2.5.0-beta1
Sanitize
on classes implementingITelemetry
no longer modifies theTelemetryContext
fields. Serialized event json and ETW event will still have context tags sanitized.DeepClone
onITelemetry
interface. Implemented by all supported telemetry items.wp8
,portable-win81+wpa81
anduap10.0
targets.Version 2.4.0
Version 2.4.0-beta5
Version 2.4.0-beta4
Version 2.4.0-beta3
Version 2.4.0-beta2
Version 2.4.0-beta1
ApplicationInsights.config
file to revert to the previous behavior.Request.Success
field will not be populated based onResponseCode
. It needs to be set explicitly.Version 2.3.0
Version 2.3.0-beta3
Version 2.3.0-beta2
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.
Version 2.3.0-beta1
Version 2.2.0
Version 2.2.0-beta6
Version 2.2.0-beta5
Version 2.2.0-beta4
Version 2.2.0-beta3
NetworkType
,ScreenResolution
andLanguage
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 toData
for consistency 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 forDependencyTelemetry
item.SessionStateTelemetry
was marked obsolete. UseIsFirst
flag inSessionContext
to indicate that the session is just started.PerformanceCounterTelemetry
was marked obsolete. UseMetricTelemetry
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. UseTimeStamp
instead.Version 2.2.0-beta2
Version 2.2.0-beta1
Version 2.1.0-beta4
Version 2.1.0-beta3
Version 2.1.0-beta1
Version 2.0.1
Version 2.0.0
Version 2.0.0-rc1
IsTracingDisabled
property onTelemetryDebugWriter
.Telemetry items that were filtered out by sampling are now indicated in debug output. Custom telemetry processors can now invoke
method
WriteTelemetry
onTelemetryDebugWriter
withfilteredBy
parameter to indicate in debug output that anitem is being filtered out.
SyntheticSource
equals to 'SDKTelemetry'.Version 2.0.0-beta4
DependencyTelemetry
to have new propertiesResultCode
andId
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).ServerTelemetryChannel
has new propertyStorageFolder
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
andUseAdaptiveSampling
preserves TelemetryProcessors loaded from configuration.Version 2.0.0-beta3
UseSampling
to allow chaining with other calls toUse
of telemetry processors.Request.ID
returned back.OperationContext
now has a propertyParentId
for end-to-end correlation.TimestampTelemetryInitializer
is removed. Timestamp will be added automatically byTelemetryClient
.OperationCorrelationTelemetryInitializer
is added by default to enable operaitons correlation.Version 2.0.0-beta2
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 ofEventTelemetry
was set to 512.Name
ofOperationContext
was renamed toRootName
Id
ofRequestTelemetry
was removed.Id
andContext.Operation.Id
ofRequestTelemetry
would not be initialized when creating newRequestTelemetry
.OperationContext
:CorrelationVector
,ParentId
andRootId
to support end-to-end telemetry items correlation.Version 2.0.0-beta1
RequestTelemetry.ID
is now just a proxy forRequestTelemetry.Operation.Id
.ISupportSampling
and explicit implementation of it by most of data item types.Count
property on DependencyTelemetry marked as Obsolete. UseSamplingPercentage
instead.CloudContext
introduced and propertiesRoleName
andRoleInstance
moved to it fromDeviceContext
.AuthenticatedUserId
onUserContext
to specify authenticated user identity.Version 1.2.3
Version 1.2
Version 1.1
DependencyTelemetry
which contains information about dependency call from applicationTelemetryClient.TrackDependency
allows to send information about dependency calls from applicationVersion 0.17
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.Version 0.16
TelemetryClient
do not cache Instrumentation Key anymore. Now if instrumentation key wasn't set toTelemetryClient
explicitlyInstrumentationKey
will return null. It fixes an issue when you setTelemetryConfiguration.Active.InstrumentationKey
after some telemetry was already collected, telemetry modules like dependency collector, web requests data collection and performance counters collector will use new instrumentation key.Version 0.15
Operation.SyntheticSource
now available onTelemetryContext
. Now you can mark your telemetry items as �not a real user traffic� and specify how this traffic was generated. As an example by setting this property you can distinguish traffic from your test automation from load test traffic.TelemetryClient.Flush
allows to flush telemetry items from the buffer synchronouslyVersion 0.13
No release notes for older versions available.
Version 2.11.2
Version 2.11.1
Version 2.11.0
Version 2.11.0-beta2
Version 2.11.0-beta1
Version 2.10.0
Version 2.10.0-beta4
Version 2.10.0-beta3
Version 2.10.0-beta2
Version 2.9.1
Version 2.9.0
Version 2.9.0-beta3
DependencyTrackingTelemetryModule.EnableLegacyCorrelationHeadersInjection
and run app locally with Azure Storage Emulator, make sure you manually exclude localhost from correlation headers injection in theExcludeComponentCorrelationHttpHeadersOnDomains
underDependencyCollector
Version 2.9.0-beta1
Version 2.8.0-beta2
If you are upgrading, and have added/modified TelemetryProcessors, make sure to copy them to the default sink section.
Version 2.8.0-beta1
Version 2.7.2
Version 2.7.0-beta4
Version 2.7.0-beta3
Version 2.7.0-beta1
Version 2.6.0-beta4
Version 2.6.0-beta3
AzureInstanceMetadataTelemetryModule
(used in heartbeats)AzureWebAppRoleEnvironmentTelemetryInitializer
BuildInfoConfigComponentVersionTelemetryInitializer
DeveloperModeWithDebuggerAttachedTelemetryModule
UnobservedExceptionTelemetryModule
Version 2.6.0-beta2
Version 2.5.0
Version 2.5.0-beta2
Project
Version 2.5.0-beta1
net40
targets from all packages. Use the version 2.4 of SDK if your application is still compiled with the framework 4.0.Project
Version 2.4.1
Version 2.4.0
Version 2.4.0-beta5
Version 2.4.0-beta4
Version 2.4.0-beta3
DisableDiagnosticSourceInstrumentation
configuration flag was added toDependencyTrackingTelemetryModule
.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)Version 2.4.0-beta2
.Context.Operation.Name
instead of custom propertyoperationName
Version 2.4.0-beta1
Configuration
📅 Schedule: At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by WhiteSource Renovate. View repository job log here.