Bump the production-dependencies group with 2 updates #32
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.
Updated Microsoft.ApplicationInsights.AspNetCore from 2.1.1 to 2.23.0.
Release notes
Sourced from Microsoft.ApplicationInsights.AspNetCore's releases.
2.23.0
2.23.0-beta1
2.22.0
2.22.0-beta4
2.22.0-beta3
ActivityRecorded flags were modified externally, when enabled side-by-side with OpenTelemetry or other solutions.2.22.0-beta2
2.22.0-beta1
2.21.0
2.21.0-beta3
Newtonsoft.Json(GHSA-5crp-9r3c-p9vr).Mitigation is to upgrade dependencies in
Microsoft.ApplicationInsights.AspNetCore(#2615)Microsoft.Extensions.Configuration.Jsonfrom v2.1.0 to v3.1.0.System.Text.Encodings.Webfrom 4.5.1 to 4.7.2.2.21.0-beta2
SharedtoMicrosoftnamespaceMitigation for TelemetryClient.Flush deadlocks (#1186)
2.21.0-beta1
2.20.0
2.20.0-beta1
2.19.0
{OriginalFormat}field in ILogger Scope will be emitted asOriginalFormatwith the braces removed2.19.0-beta1
{OriginalFormat}field in ILogger Scope will be emitted asOriginalFormatwith the braces removed2.18.0
2.18.0-beta3
2.18.0-beta2
2.18.0-beta1
2.17.0
2.17.0-beta1
2.16.0
2.16.0-beta1
ExceptionStackTracewhenTrackExceptionsAsExceptionTelemetryflag is set tofalse{OriginalFormat}field in ILogger will be emitted asOriginalFormatwith the braces removed2.15.0
2.15.0-beta3
2.15.0-beta2
2.15.0-beta1
2.14.0
2.14.0-beta5
2.14.0-beta3
2.14.0-beta2
2.14.0-beta1
Collecting SQL Command Text will now be opt-in, so this value will default to false. This is a change from the current behavior on .NET Core. To see how to collect SQL Command Text see here for details: https://docs.microsoft.com/azure/azure-monitor/app/asp-net-dependencies#advanced-sql-tracking-to-get-full-sql-query
2.13.1
2.13.0
2.13.0-beta2
2.13.0-beta1
2.12.2
2.12.1
2.12.0
2.12.0-beta4
2.12.0-beta3
2.12.0-beta2
2.12.0-beta1
2.11.0
2.11.0-beta2
2.11.0-beta1
2.10.0
2.10.0-beta4
2.10.0-beta3
2.10.0-beta2
2.9.1
2.9.0
2.9.0-beta3
2.9.0-beta2
Important: The 2.9.0-beta2 has a known issue - Installing this package will create ApplicationInsights.config file, but it'll not set it to be copied to output directory. Users are advised to set this file to 'Copy if newer' so that build output will have the ApplicationInsights.config file.
This is expected to be fixed in next beta.
Perf Improvements.
2.8.1
Patch release addressing perf regression.
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
2.8.0-beta2
If you are upgrading, and have added/modified TelemetryProcessors/TelemetryChannel, make sure to copy them to the default sink section.
2.8.0-beta1
(continuation of Strong typed extensibility for Telemetry types microsoft/ApplicationInsights-dotnet#871)
ExceptionDetailsInfoListonExceptionTelemetryclass that gives control to user to update exceptionmessage and exception type of underlying
System.Exceptionobject that user wants to send to telemetry. Related discussion is here.2.7.2
2.7.1
2.7.0-beta4
2.7.0-beta3
Related: (CPU usage slowly increases over time microsoft/ApplicationInsights-aspnetcore#690)
2.7.0-beta2
2.7.0-beta1
2.6.4
SamplingPercentageEstimatorSettings,AdaptiveSamplingPercentageEvaluatedCallback2.6.1
Extend the Beta period for Metrics Pre-Aggregation features shipped in 2.6.0-beta3.
2.6.0-beta4
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.)2.6.0-beta2
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
2.5.0
2.5.0-beta2
[Details on fix and workaround #654] (ServerTelemetryChannel for .Net Core Apps microsoft/ApplicationInsights-dotnet#654)
Original issue (TelemetryChannel for Linux microsoft/ApplicationInsights-aspnetcore#551)
AdaptiveSamplingTelemetryProcessorthat would cause starvation over time. Issue #756 (dotnet-server)2.5.0-beta1
Sanitizeon classes implementingITelemetryno longer modifies theTelemetryContextfields. Serialized event json and ETW event will still have context tags sanitized.DeepCloneonITelemetryinterface. Implemented by all supported telemetry items.wp8,portable-win81+wpa81anduap10.0targets.2.4.0
Includes all changes since 2.3.0 stable release.
Updated reference to System.Diagnostics.DiagnosticSource version 4.4.0
2.4.0-beta4
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).
2.4.0-beta3
2.4.0-beta2
2.4.0-beta1
ApplicationInsights.configfile to revert to the previous behavior.Request.Successfield will not be populated based onResponseCode. It needs to be set explicitly.2.3.0
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.
2.3.0-beta3
Added overloads of TelemetryClientExtensions.StartOperation.
Fire new ETW events for Operation Start/Stop.
2.3.0-beta2
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
2.3.0-beta1
2.2.0
2.2.0-beta6
2.2.0-beta4
NetworkType,ScreenResolutionandLanguagemarked 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.CommandNamewas renamed toDatafor consistancy with the Application Analytics schema.DependencyKindwill never be send any more and will not be set to "Other" by default. Also there are two more constructors forDependencyTelemetryitem.SessionStateTelemetrywas marked obsolete. UseIsFirstflag inSessionContextto indicate that the session is just started.PerformanceCounterTelemetrywas marked obsolete. UseMetricTelemetryinstead.RequestTelemetry.HttpMethodas 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.StartTimeas obsolete. UseTimeStampinstead.2.2.0-beta2
2.2.0-beta1
Commits viewable in compare view.
Updated System.Text.Encodings.Web from 4.5.1 to 4.7.2.
Release notes
Sourced from System.Text.Encodings.Web's releases.
No release notes found for this version range.
Commits viewable in compare view.
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore <dependency name> major versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)@dependabot ignore <dependency name> minor versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)@dependabot ignore <dependency name>will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)@dependabot unignore <dependency name>will remove all of the ignore conditions of the specified dependency@dependabot unignore <dependency name> <ignore condition>will remove the ignore condition of the specified dependency and ignore conditions