Skip to content

Fix #3211: Default unset Timestamp to UtcNow in TrackDependency/TrackRequest - #3219

Merged
Matthew Sainsbury (Microsoft) (mattsains-msft) merged 3 commits into
mainfrom
rajrang/fixTrackTimestampDefault
Sep 25, 2026
Merged

Matthew Sainsbury (Microsoft) (mattsains-msft) merged 3 commits into
mainfrom
rajrang/fixTrackTimestampDefault

Conversation

@rajkumar-rangaraj

Copy link
Copy Markdown
Member

Fixes #3211

Problem

TelemetryClient.TrackDependency(DependencyTelemetry) and TelemetryClient.TrackRequest(RequestTelemetry) copied telemetry.Timestamp straight into the backing Activity's start and end times without checking whether it had been set. Code that builds the telemetry without a timestamp (for example new DependencyTelemetry(type, target, name, data) or new RequestTelemetry { ... }) therefore emitted time = 0001-01-01T00:00:00Z. Ingestion rejects these items with a 206 partial success (error 103).

In 2.x, TelemetryClient set an unset Timestamp itself (see the CHANGELOG: "Timestamp will be added automatically by TelemetryClient"). StartOperation/StopOperation and TrackAvailability are not affected.

Fix

In both methods, if Timestamp == default, set it to DateTimeOffset.UtcNow before creating the Activity. This restores 2.x behavior, including writing the value back to the telemetry object. Timestamps set explicitly by the caller are unchanged.

Tests

  • TrackDependencyWithoutTimestampDefaultsToUtcNow / TrackRequestWithoutTimestampDefaultsToUtcNow: the start time is the time of the call, the duration is kept, and the timestamp is written back. Both tests fail without the fix.
  • TrackDependencyWithExplicitTimestampPreservesTimestamp / TrackRequestWithExplicitTimestampPreservesTimestamp: an explicit timestamp and duration come through unchanged.
  • All TelemetryClient* tests pass on net8.0 and net462 (162 on each).

Changes

  • CHANGELOG.md updated
  • Public API changes (none)

)

TrackDependency(DependencyTelemetry) and TrackRequest(RequestTelemetry) assigned Timestamp directly to Activity start/end time without checking for default, emitting 0001-01-01T00:00:00Z which ingestion rejects (error 103). Restore 2.x behavior by defaulting an unset Timestamp to DateTimeOffset.UtcNow.

Fixes #3211

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot AI lite review requested due to automatic review settings September 24, 2026 23:56
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot review overview

🟢 Approval recommended

No unresolved review issues were identified.

Review effort: Lite
Findings: None

What changed in this PR

Fixes unset request and dependency timestamps by defaulting them to DateTimeOffset.UtcNow.

Changes:

  • Added timestamp fallback in TrackRequest and TrackDependency.
  • Added regression tests for default and explicit timestamps.
  • Documented the fix in the changelog.
File Summary
CHANGELOG.md Documents the timestamp behavior fix.
BASE/​Test/​Microsoft.ApplicationInsights.Test/​Microsoft.ApplicationInsights.Tests/​TelemetryClientTest.cs Adds timestamp regression tests.
BASE/​src/​Microsoft.ApplicationInsights/​TelemetryClient.cs Applies the UTC timestamp fallback.

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

@mattsains-msft
Matthew Sainsbury (Microsoft) (mattsains-msft) merged commit 07099fc into main Sep 25, 2026
18 checks passed
@mattsains-msft
Matthew Sainsbury (Microsoft) (mattsains-msft) deleted the rajrang/fixTrackTimestampDefault branch September 25, 2026 17:28
This was referenced Oct 12, 2026
This was referenced Nov 16, 2026
Jarrett Booz (sei-jbooz) pushed a commit to cmu-sei/CITE.Api that referenced this pull request Nov 20, 2026
)

Updated
[Microsoft.ApplicationInsights.AspNetCore](https://github.com/Microsoft/ApplicationInsights-dotnet)
from 2.23.0 to 3.2.0.

<details>
<summary>Release notes</summary>

_Sourced from [Microsoft.ApplicationInsights.AspNetCore's
releases](https://github.com/Microsoft/ApplicationInsights-dotnet/releases)._

## 3.2.0

- Update OpenTelemetry core packages to 1.19.1, instrumentation packages
to 1.19.0, and Azure Monitor OpenTelemetry Exporter to 1.10.0.
- **Breaking change:** Reduce default HTTP client metric volume in
ASP.NET Core and Worker Service on .NET 8+ while retaining request
latency, count, and failure dimensions through
`http.client.request.duration`. Other `System.Net.Http` metrics are now
opt-in through OpenTelemetry `AddView`; dashboards and alerts using them
must [explicitly enable
collection](MigrationGuidance.md#enabling-additional-http-client-metrics).
HTTP dependency tracing and server metrics are unchanged. No new public
API is introduced. Addresses the HTTP metric-volume concern in
[#​3192](microsoft/ApplicationInsights-dotnet#3192).
- [Fix #​3197: `NullReferenceException` when using TelemetryClient APIs
when no connection string is
provided.](microsoft/ApplicationInsights-dotnet#3199)
- [Fix #​3211: `TelemetryClient.TrackDependency(DependencyTelemetry)`
and `TelemetryClient.TrackRequest(RequestTelemetry)` now default an
unset `Timestamp` to `DateTimeOffset.UtcNow` (restoring 2.x behavior)
instead of emitting `0001-01-01T00:00:00Z`, which ingestion
rejects.](microsoft/ApplicationInsights-dotnet#3219)
- [Fix #​3223: The WEB package's activity processors now write the tag
keys the Azure Monitor exporter maps (`enduser.pseudo.id`,
`microsoft.session.id`, `microsoft.synthetic_source`,
`microsoft.user.account_id`), so `user_Id`, `session_Id`,
`operation_SyntheticSource` and `user_AccountId` are populated again
instead of the values landing in `customDimensions` as `ai.user.id`,
`session.id`, `ai.operation.syntheticSource` and `enduser.account`.
`user_AccountId` is also no longer skipped when the authenticated user
cookie is present, and the unmapped `session.isFirst` custom dimension
is no longer
emitted.](microsoft/ApplicationInsights-dotnet#3224)
- [Fix `StartOperation`/`StopOperation` losing or misreporting telemetry
fields. Stopping an operation now exports the fields set on its
telemetry item using the same keys as `TrackDependency`/`TrackRequest`:
dependency `Type`, `Data`, `Target` and `ResultCode` (previously wrong
or empty for HTTP, SQL, `Queue Message` and custom types), request
`Url`, `Source` and `ResponseCode`, `Success`, and custom `Properties`.
The unmapped `OperationName` and `messaging.destination` tags no longer
appear as custom
dimensions.](microsoft/ApplicationInsights-dotnet#3225)



## 3.1.2

## Version 3.1.2
- [Fix `HttpException: Request is not available in this context` in the
WEB package when calling `TrackDependency` from `Application_Start` in
classic ASP.NET. The WEB activity processors now safely handle the case
where `HttpContext.Request` is not yet
available.](microsoft/ApplicationInsights-dotnet#3184)
- [Fix #​3163: `TelemetryConfiguration.CreateDefault()` on classic
ASP.NET now returns a configuration already populated from
`ApplicationInsights.config` (connection string, sampling, storage, live
metrics, request/dependency tracking, etc.). A new
`PreApplicationStartMethod` (`WebApplicationInsightsInitializer`)
materializes and populates the singleton before `Application_Start`
runs, so customer code calling `TelemetryConfiguration.CreateDefault()`
from `Global.asax.cs` no longer gets an empty configuration. The
`ApplicationInsightsHttpModule` no longer carries the config-reading
bookkeeping.
`TelemetryConfiguration.PrependOpenTelemetryBuilderConfiguration` no
longer throws if the configuration was already built — it silently
skips, so a second `TelemetryClient` constructed against an
already-built configuration no longer throws
`InvalidOperationException`.](microsoft/ApplicationInsights-dotnet#3183)


## 3.1.1

## Version 3.1.1
- Update OpenTelemetry and Azure Monitor dependencies to address known
security advisories (e.g.
[GHSA-g94r-2vxg-569j](GHSA-g94r-2vxg-569j)
in `OpenTelemetry.Api` 1.15.1):
microsoft/ApplicationInsights-dotnet#3174
  - OpenTelemetry 1.15.3
  - OpenTelemetry.Exporter.Console 1.15.3
  - OpenTelemetry.Exporter.InMemory 1.15.3
  - OpenTelemetry.Extensions.Hosting 1.15.3
  - OpenTelemetry.Instrumentation.AspNetCore 1.15.2
  - OpenTelemetry.Instrumentation.AspNet 1.15.2
  - OpenTelemetry.Instrumentation.Http 1.15.1
  - OpenTelemetry.Instrumentation.SqlClient 1.15.2
  - Azure.Monitor.OpenTelemetry.Exporter 1.8.0

## 3.1.0

## Version 3.1.0
- [Make `TelemetryContext` properties public and propagate them via
`TelemetryClient`.](microsoft/ApplicationInsights-dotnet#3137)
- [Add fallback to `APPLICATIONINSIGHTS_CONNECTION_STRING` environment
variable for Base, Web, and NLog packages when connection string is not
set via
code.](microsoft/ApplicationInsights-dotnet#3134)
- [Update Azure.Monitor.OpenTelemetry.Exporter to 1.7.0. This includes
updated mappings for telemetry
context.](microsoft/ApplicationInsights-dotnet#3154)
- [Fix `OTEL_SDK_DISABLED` not being honored when
`TelemetryConfiguration.DisableTelemetry` is set in DI
scenarios.](microsoft/ApplicationInsights-dotnet#3156),
[#​3157](microsoft/ApplicationInsights-dotnet#3157)
- [Fix `TrackAvailability` ignoring user-specified `Timestamp` on
`AvailabilityTelemetry`. The timestamp is now emitted as
`microsoft.availability.testTimestamp` so downstream exporters can use
the correct event
time.](microsoft/ApplicationInsights-dotnet#3153)
- [Added `netstandard2.0` target framework to
`Microsoft.ApplicationInsights` package to support customers with shared
libraries targeting
netstandard2.0.](microsoft/ApplicationInsights-dotnet#3142)
- [Fix `TelemetryClient.Context.Cloud.RoleName` set after construction
now applies to all
telemetry.](microsoft/ApplicationInsights-dotnet#3129)
- [Fix bug where Debug/Trace level logs from TrackTrace API were not
emitted to Application
Insights](microsoft/ApplicationInsights-dotnet#3121)
- [Fix Track API calls to not mutate the passed in dictionary if it is
readonly](microsoft/ApplicationInsights-dotnet#3119)
- [Fix `NullReferenceException` in `TelemetryClient.Flush()` and
`FlushAsync()` when called from DI
scenarios](microsoft/ApplicationInsights-dotnet#3125)
- [Fix `ApplicationVersion` ignored:
`ApplicationInsightsServiceOptions.ApplicationVersion` is now applied as
`service.version` on the OpenTelemetry Resource for both AspNetCore and
WorkerService
packages](microsoft/ApplicationInsights-dotnet#3124)
- [Fix `HttpRequestExtensions.UnvalidatedGetHeader` always returning
empty string instead of the actual header value. Restored max-length
enforcement to guard against oversized header
values.](microsoft/ApplicationInsights-dotnet#3126)

## 3.0.0

- [Replaced `netstandard2.0` with `net8.0` target framework in
`Microsoft.ApplicationInsights.NLogTarget`
package.](microsoft/ApplicationInsights-dotnet#3102)

## 3.0.0-rc1

- [Removed `netstandard2.0` target framework from
`Microsoft.ApplicationInsights`,
`Microsoft.ApplicationInsights.AspNetCore`, and
`Microsoft.ApplicationInsights.WorkerService`
packages.](microsoft/ApplicationInsights-dotnet#3091)
- [The JavaScript in `Microsoft.ApplicationInsights.AspNetCore` has been
updated to version
10.](microsoft/ApplicationInsights-dotnet#3078)
- [Centralized package version
management](microsoft/ApplicationInsights-dotnet#3080)
- [Update OpenTelemetry
dependencies](microsoft/ApplicationInsights-dotnet#3080),
[#​3092](microsoft/ApplicationInsights-dotnet#3092)
  - OpenTelemetry 1.15.0
  - OpenTelemetry.Instrumentation.AspNetCore 1.15.0
  - OpenTelemetry.Instrumentation.AspNet 1.15.1
  - OpenTelemetry.Instrumentation.Http 1.15.0
  - OpenTelemetry.Instrumentation.SqlClient 1.15.0
- [Vendored OpenTelemetry.Resources.Azure resource detectors to NETCORE
shared folder, replaced package with vendored
implementation](microsoft/ApplicationInsights-dotnet#3095),
[#​3093](microsoft/ApplicationInsights-dotnet#3093)
- [Added support to disable telemetry via
TelemetryConfiguration.DisableTelemetry](microsoft/ApplicationInsights-dotnet#3084)
- [Removed `EnabledAdaptiveSampling` and replaced with `TracesPerSecond`
and
`SamplingRatio`](microsoft/ApplicationInsights-dotnet#3085)
- [Added `EnableTraceBasedLogsSampler` property to
`ApplicationInsightsServiceOptions` for ASP.NET Core and WorkerService
packages](microsoft/ApplicationInsights-dotnet#3088)
- [Added support for `StorageDirectory` and `DisableOfflineStorage` from
`TelemetryConfiguration` in DI
scenarios](microsoft/ApplicationInsights-dotnet#3088)
- [Update Azure.Monitor.OpenTelemetry.Exporter dependency to
1.6.0](microsoft/ApplicationInsights-dotnet#3094)
 

## 3.0.0-beta2

Added
- Automatic configuration binding from "ApplicationInsights" section in
appsettings.json for both AspNetCore and WorkerService packages with
configuration precedence: environment variables > explicit configuration
> appsettings.json
- Added support for Entra ID (Azure Active Directory) authentication
using Azure.Core.TokenCredential
- Added Self Diagnostics feature
- Updated the default sampler from Fixed Rate to Rate-Limited Sampling.
- Update Azure Monitor Exporter to 1.6.0-beta.2
- Add comprehensive applicationinsights.config support
- Add properties in TelemetryConfiguration to configure underlying
exporter

Bug fix
- Fix TrackMetric(MetricTelemetry) unsupported telemetry type error

## 3.0.0-beta1

- The following Application Insights packages in this repo now use
OpenTelemetry internally. OpenTelemetry is the industry standard for
telemetry collection and provides better interoperability with other
observability tools.
  - Microsoft.ApplicationInsights
  - Microsoft.ApplicationInsights.AspNetCore
  - Microsoft.ApplicationInsights.WorkerService
  - Microsoft.ApplicationInsights.Web
  - Microsoft.ApplicationInsights.NLogTarget
- Classic APIs of the above packages are preserved; calls are translated
to OpenTelemetry telemetry.
- Other packages not listed above (such as certain auto-collectors and
logging adapters that were published from this repo previously) will not
have future versions published. See BreakingChanges.md for details.

Commits viewable in [compare
view](microsoft/ApplicationInsights-dotnet@2.23.0...v3.2.0).
</details>

[![Dependabot compatibility
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=Microsoft.ApplicationInsights.AspNetCore&package-manager=nuget&previous-version=2.23.0&new-version=3.2.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)

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-automerge-start)
[//]: # (dependabot-automerge-end)

---

<details>
<summary>Dependabot commands and options</summary>
<br />

You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits
that have been made to it
- `@dependabot show <dependency name> ignore conditions` will show all
of the ignore conditions of the specified dependency
- `@dependabot ignore this major version` will close this PR and stop
Dependabot creating any more for this major version (unless you reopen
the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop
Dependabot creating any more for this minor version (unless you reopen
the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop
Dependabot creating any more for this dependency (unless you reopen the
PR or upgrade to it yourself)


</details>

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Jarrett Booz (sei-jbooz) pushed a commit to cmu-sei/Player.Api that referenced this pull request Nov 20, 2026
)

Updated
[Microsoft.ApplicationInsights.AspNetCore](https://github.com/Microsoft/ApplicationInsights-dotnet)
from 2.23.0 to 3.2.0.

<details>
<summary>Release notes</summary>

_Sourced from [Microsoft.ApplicationInsights.AspNetCore's
releases](https://github.com/Microsoft/ApplicationInsights-dotnet/releases)._

## 3.2.0

- Update OpenTelemetry core packages to 1.19.1, instrumentation packages
to 1.19.0, and Azure Monitor OpenTelemetry Exporter to 1.10.0.
- **Breaking change:** Reduce default HTTP client metric volume in
ASP.NET Core and Worker Service on .NET 8+ while retaining request
latency, count, and failure dimensions through
`http.client.request.duration`. Other `System.Net.Http` metrics are now
opt-in through OpenTelemetry `AddView`; dashboards and alerts using them
must [explicitly enable
collection](MigrationGuidance.md#enabling-additional-http-client-metrics).
HTTP dependency tracing and server metrics are unchanged. No new public
API is introduced. Addresses the HTTP metric-volume concern in
[#​3192](microsoft/ApplicationInsights-dotnet#3192).
- [Fix #​3197: `NullReferenceException` when using TelemetryClient APIs
when no connection string is
provided.](microsoft/ApplicationInsights-dotnet#3199)
- [Fix #​3211: `TelemetryClient.TrackDependency(DependencyTelemetry)`
and `TelemetryClient.TrackRequest(RequestTelemetry)` now default an
unset `Timestamp` to `DateTimeOffset.UtcNow` (restoring 2.x behavior)
instead of emitting `0001-01-01T00:00:00Z`, which ingestion
rejects.](microsoft/ApplicationInsights-dotnet#3219)
- [Fix #​3223: The WEB package's activity processors now write the tag
keys the Azure Monitor exporter maps (`enduser.pseudo.id`,
`microsoft.session.id`, `microsoft.synthetic_source`,
`microsoft.user.account_id`), so `user_Id`, `session_Id`,
`operation_SyntheticSource` and `user_AccountId` are populated again
instead of the values landing in `customDimensions` as `ai.user.id`,
`session.id`, `ai.operation.syntheticSource` and `enduser.account`.
`user_AccountId` is also no longer skipped when the authenticated user
cookie is present, and the unmapped `session.isFirst` custom dimension
is no longer
emitted.](microsoft/ApplicationInsights-dotnet#3224)
- [Fix `StartOperation`/`StopOperation` losing or misreporting telemetry
fields. Stopping an operation now exports the fields set on its
telemetry item using the same keys as `TrackDependency`/`TrackRequest`:
dependency `Type`, `Data`, `Target` and `ResultCode` (previously wrong
or empty for HTTP, SQL, `Queue Message` and custom types), request
`Url`, `Source` and `ResponseCode`, `Success`, and custom `Properties`.
The unmapped `OperationName` and `messaging.destination` tags no longer
appear as custom
dimensions.](microsoft/ApplicationInsights-dotnet#3225)



## 3.1.2

## Version 3.1.2
- [Fix `HttpException: Request is not available in this context` in the
WEB package when calling `TrackDependency` from `Application_Start` in
classic ASP.NET. The WEB activity processors now safely handle the case
where `HttpContext.Request` is not yet
available.](microsoft/ApplicationInsights-dotnet#3184)
- [Fix #​3163: `TelemetryConfiguration.CreateDefault()` on classic
ASP.NET now returns a configuration already populated from
`ApplicationInsights.config` (connection string, sampling, storage, live
metrics, request/dependency tracking, etc.). A new
`PreApplicationStartMethod` (`WebApplicationInsightsInitializer`)
materializes and populates the singleton before `Application_Start`
runs, so customer code calling `TelemetryConfiguration.CreateDefault()`
from `Global.asax.cs` no longer gets an empty configuration. The
`ApplicationInsightsHttpModule` no longer carries the config-reading
bookkeeping.
`TelemetryConfiguration.PrependOpenTelemetryBuilderConfiguration` no
longer throws if the configuration was already built — it silently
skips, so a second `TelemetryClient` constructed against an
already-built configuration no longer throws
`InvalidOperationException`.](microsoft/ApplicationInsights-dotnet#3183)


## 3.1.1

## Version 3.1.1
- Update OpenTelemetry and Azure Monitor dependencies to address known
security advisories (e.g.
[GHSA-g94r-2vxg-569j](GHSA-g94r-2vxg-569j)
in `OpenTelemetry.Api` 1.15.1):
microsoft/ApplicationInsights-dotnet#3174
  - OpenTelemetry 1.15.3
  - OpenTelemetry.Exporter.Console 1.15.3
  - OpenTelemetry.Exporter.InMemory 1.15.3
  - OpenTelemetry.Extensions.Hosting 1.15.3
  - OpenTelemetry.Instrumentation.AspNetCore 1.15.2
  - OpenTelemetry.Instrumentation.AspNet 1.15.2
  - OpenTelemetry.Instrumentation.Http 1.15.1
  - OpenTelemetry.Instrumentation.SqlClient 1.15.2
  - Azure.Monitor.OpenTelemetry.Exporter 1.8.0

## 3.1.0

## Version 3.1.0
- [Make `TelemetryContext` properties public and propagate them via
`TelemetryClient`.](microsoft/ApplicationInsights-dotnet#3137)
- [Add fallback to `APPLICATIONINSIGHTS_CONNECTION_STRING` environment
variable for Base, Web, and NLog packages when connection string is not
set via
code.](microsoft/ApplicationInsights-dotnet#3134)
- [Update Azure.Monitor.OpenTelemetry.Exporter to 1.7.0. This includes
updated mappings for telemetry
context.](microsoft/ApplicationInsights-dotnet#3154)
- [Fix `OTEL_SDK_DISABLED` not being honored when
`TelemetryConfiguration.DisableTelemetry` is set in DI
scenarios.](microsoft/ApplicationInsights-dotnet#3156),
[#​3157](microsoft/ApplicationInsights-dotnet#3157)
- [Fix `TrackAvailability` ignoring user-specified `Timestamp` on
`AvailabilityTelemetry`. The timestamp is now emitted as
`microsoft.availability.testTimestamp` so downstream exporters can use
the correct event
time.](microsoft/ApplicationInsights-dotnet#3153)
- [Added `netstandard2.0` target framework to
`Microsoft.ApplicationInsights` package to support customers with shared
libraries targeting
netstandard2.0.](microsoft/ApplicationInsights-dotnet#3142)
- [Fix `TelemetryClient.Context.Cloud.RoleName` set after construction
now applies to all
telemetry.](microsoft/ApplicationInsights-dotnet#3129)
- [Fix bug where Debug/Trace level logs from TrackTrace API were not
emitted to Application
Insights](microsoft/ApplicationInsights-dotnet#3121)
- [Fix Track API calls to not mutate the passed in dictionary if it is
readonly](microsoft/ApplicationInsights-dotnet#3119)
- [Fix `NullReferenceException` in `TelemetryClient.Flush()` and
`FlushAsync()` when called from DI
scenarios](microsoft/ApplicationInsights-dotnet#3125)
- [Fix `ApplicationVersion` ignored:
`ApplicationInsightsServiceOptions.ApplicationVersion` is now applied as
`service.version` on the OpenTelemetry Resource for both AspNetCore and
WorkerService
packages](microsoft/ApplicationInsights-dotnet#3124)
- [Fix `HttpRequestExtensions.UnvalidatedGetHeader` always returning
empty string instead of the actual header value. Restored max-length
enforcement to guard against oversized header
values.](microsoft/ApplicationInsights-dotnet#3126)

## 3.0.0

- [Replaced `netstandard2.0` with `net8.0` target framework in
`Microsoft.ApplicationInsights.NLogTarget`
package.](microsoft/ApplicationInsights-dotnet#3102)

## 3.0.0-rc1

- [Removed `netstandard2.0` target framework from
`Microsoft.ApplicationInsights`,
`Microsoft.ApplicationInsights.AspNetCore`, and
`Microsoft.ApplicationInsights.WorkerService`
packages.](microsoft/ApplicationInsights-dotnet#3091)
- [The JavaScript in `Microsoft.ApplicationInsights.AspNetCore` has been
updated to version
10.](microsoft/ApplicationInsights-dotnet#3078)
- [Centralized package version
management](microsoft/ApplicationInsights-dotnet#3080)
- [Update OpenTelemetry
dependencies](microsoft/ApplicationInsights-dotnet#3080),
[#​3092](microsoft/ApplicationInsights-dotnet#3092)
  - OpenTelemetry 1.15.0
  - OpenTelemetry.Instrumentation.AspNetCore 1.15.0
  - OpenTelemetry.Instrumentation.AspNet 1.15.1
  - OpenTelemetry.Instrumentation.Http 1.15.0
  - OpenTelemetry.Instrumentation.SqlClient 1.15.0
- [Vendored OpenTelemetry.Resources.Azure resource detectors to NETCORE
shared folder, replaced package with vendored
implementation](microsoft/ApplicationInsights-dotnet#3095),
[#​3093](microsoft/ApplicationInsights-dotnet#3093)
- [Added support to disable telemetry via
TelemetryConfiguration.DisableTelemetry](microsoft/ApplicationInsights-dotnet#3084)
- [Removed `EnabledAdaptiveSampling` and replaced with `TracesPerSecond`
and
`SamplingRatio`](microsoft/ApplicationInsights-dotnet#3085)
- [Added `EnableTraceBasedLogsSampler` property to
`ApplicationInsightsServiceOptions` for ASP.NET Core and WorkerService
packages](microsoft/ApplicationInsights-dotnet#3088)
- [Added support for `StorageDirectory` and `DisableOfflineStorage` from
`TelemetryConfiguration` in DI
scenarios](microsoft/ApplicationInsights-dotnet#3088)
- [Update Azure.Monitor.OpenTelemetry.Exporter dependency to
1.6.0](microsoft/ApplicationInsights-dotnet#3094)
 

## 3.0.0-beta2

Added
- Automatic configuration binding from "ApplicationInsights" section in
appsettings.json for both AspNetCore and WorkerService packages with
configuration precedence: environment variables > explicit configuration
> appsettings.json
- Added support for Entra ID (Azure Active Directory) authentication
using Azure.Core.TokenCredential
- Added Self Diagnostics feature
- Updated the default sampler from Fixed Rate to Rate-Limited Sampling.
- Update Azure Monitor Exporter to 1.6.0-beta.2
- Add comprehensive applicationinsights.config support
- Add properties in TelemetryConfiguration to configure underlying
exporter

Bug fix
- Fix TrackMetric(MetricTelemetry) unsupported telemetry type error

## 3.0.0-beta1

- The following Application Insights packages in this repo now use
OpenTelemetry internally. OpenTelemetry is the industry standard for
telemetry collection and provides better interoperability with other
observability tools.
  - Microsoft.ApplicationInsights
  - Microsoft.ApplicationInsights.AspNetCore
  - Microsoft.ApplicationInsights.WorkerService
  - Microsoft.ApplicationInsights.Web
  - Microsoft.ApplicationInsights.NLogTarget
- Classic APIs of the above packages are preserved; calls are translated
to OpenTelemetry telemetry.
- Other packages not listed above (such as certain auto-collectors and
logging adapters that were published from this repo previously) will not
have future versions published. See BreakingChanges.md for details.

Commits viewable in [compare
view](microsoft/ApplicationInsights-dotnet@2.23.0...v3.2.0).
</details>

[![Dependabot compatibility
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=Microsoft.ApplicationInsights.AspNetCore&package-manager=nuget&previous-version=2.23.0&new-version=3.2.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)

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-automerge-start)
[//]: # (dependabot-automerge-end)

---

<details>
<summary>Dependabot commands and options</summary>
<br />

You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits
that have been made to it
- `@dependabot show <dependency name> ignore conditions` will show all
of the ignore conditions of the specified dependency
- `@dependabot ignore this major version` will close this PR and stop
Dependabot creating any more for this major version (unless you reopen
the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop
Dependabot creating any more for this minor version (unless you reopen
the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop
Dependabot creating any more for this dependency (unless you reopen the
PR or upgrade to it yourself)


</details>

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Jarrett Booz (sei-jbooz) pushed a commit to cmu-sei/Gallery.Api that referenced this pull request Nov 20, 2026
)

Updated
[Microsoft.ApplicationInsights.AspNetCore](https://github.com/Microsoft/ApplicationInsights-dotnet)
from 2.23.0 to 3.2.0.

<details>
<summary>Release notes</summary>

_Sourced from [Microsoft.ApplicationInsights.AspNetCore's
releases](https://github.com/Microsoft/ApplicationInsights-dotnet/releases)._

## 3.2.0

- Update OpenTelemetry core packages to 1.19.1, instrumentation packages
to 1.19.0, and Azure Monitor OpenTelemetry Exporter to 1.10.0.
- **Breaking change:** Reduce default HTTP client metric volume in
ASP.NET Core and Worker Service on .NET 8+ while retaining request
latency, count, and failure dimensions through
`http.client.request.duration`. Other `System.Net.Http` metrics are now
opt-in through OpenTelemetry `AddView`; dashboards and alerts using them
must [explicitly enable
collection](MigrationGuidance.md#enabling-additional-http-client-metrics).
HTTP dependency tracing and server metrics are unchanged. No new public
API is introduced. Addresses the HTTP metric-volume concern in
[#​3192](microsoft/ApplicationInsights-dotnet#3192).
- [Fix #​3197: `NullReferenceException` when using TelemetryClient APIs
when no connection string is
provided.](microsoft/ApplicationInsights-dotnet#3199)
- [Fix #​3211: `TelemetryClient.TrackDependency(DependencyTelemetry)`
and `TelemetryClient.TrackRequest(RequestTelemetry)` now default an
unset `Timestamp` to `DateTimeOffset.UtcNow` (restoring 2.x behavior)
instead of emitting `0001-01-01T00:00:00Z`, which ingestion
rejects.](microsoft/ApplicationInsights-dotnet#3219)
- [Fix #​3223: The WEB package's activity processors now write the tag
keys the Azure Monitor exporter maps (`enduser.pseudo.id`,
`microsoft.session.id`, `microsoft.synthetic_source`,
`microsoft.user.account_id`), so `user_Id`, `session_Id`,
`operation_SyntheticSource` and `user_AccountId` are populated again
instead of the values landing in `customDimensions` as `ai.user.id`,
`session.id`, `ai.operation.syntheticSource` and `enduser.account`.
`user_AccountId` is also no longer skipped when the authenticated user
cookie is present, and the unmapped `session.isFirst` custom dimension
is no longer
emitted.](microsoft/ApplicationInsights-dotnet#3224)
- [Fix `StartOperation`/`StopOperation` losing or misreporting telemetry
fields. Stopping an operation now exports the fields set on its
telemetry item using the same keys as `TrackDependency`/`TrackRequest`:
dependency `Type`, `Data`, `Target` and `ResultCode` (previously wrong
or empty for HTTP, SQL, `Queue Message` and custom types), request
`Url`, `Source` and `ResponseCode`, `Success`, and custom `Properties`.
The unmapped `OperationName` and `messaging.destination` tags no longer
appear as custom
dimensions.](microsoft/ApplicationInsights-dotnet#3225)



## 3.1.2

## Version 3.1.2
- [Fix `HttpException: Request is not available in this context` in the
WEB package when calling `TrackDependency` from `Application_Start` in
classic ASP.NET. The WEB activity processors now safely handle the case
where `HttpContext.Request` is not yet
available.](microsoft/ApplicationInsights-dotnet#3184)
- [Fix #​3163: `TelemetryConfiguration.CreateDefault()` on classic
ASP.NET now returns a configuration already populated from
`ApplicationInsights.config` (connection string, sampling, storage, live
metrics, request/dependency tracking, etc.). A new
`PreApplicationStartMethod` (`WebApplicationInsightsInitializer`)
materializes and populates the singleton before `Application_Start`
runs, so customer code calling `TelemetryConfiguration.CreateDefault()`
from `Global.asax.cs` no longer gets an empty configuration. The
`ApplicationInsightsHttpModule` no longer carries the config-reading
bookkeeping.
`TelemetryConfiguration.PrependOpenTelemetryBuilderConfiguration` no
longer throws if the configuration was already built — it silently
skips, so a second `TelemetryClient` constructed against an
already-built configuration no longer throws
`InvalidOperationException`.](microsoft/ApplicationInsights-dotnet#3183)


## 3.1.1

## Version 3.1.1
- Update OpenTelemetry and Azure Monitor dependencies to address known
security advisories (e.g.
[GHSA-g94r-2vxg-569j](GHSA-g94r-2vxg-569j)
in `OpenTelemetry.Api` 1.15.1):
microsoft/ApplicationInsights-dotnet#3174
  - OpenTelemetry 1.15.3
  - OpenTelemetry.Exporter.Console 1.15.3
  - OpenTelemetry.Exporter.InMemory 1.15.3
  - OpenTelemetry.Extensions.Hosting 1.15.3
  - OpenTelemetry.Instrumentation.AspNetCore 1.15.2
  - OpenTelemetry.Instrumentation.AspNet 1.15.2
  - OpenTelemetry.Instrumentation.Http 1.15.1
  - OpenTelemetry.Instrumentation.SqlClient 1.15.2
  - Azure.Monitor.OpenTelemetry.Exporter 1.8.0

## 3.1.0

## Version 3.1.0
- [Make `TelemetryContext` properties public and propagate them via
`TelemetryClient`.](microsoft/ApplicationInsights-dotnet#3137)
- [Add fallback to `APPLICATIONINSIGHTS_CONNECTION_STRING` environment
variable for Base, Web, and NLog packages when connection string is not
set via
code.](microsoft/ApplicationInsights-dotnet#3134)
- [Update Azure.Monitor.OpenTelemetry.Exporter to 1.7.0. This includes
updated mappings for telemetry
context.](microsoft/ApplicationInsights-dotnet#3154)
- [Fix `OTEL_SDK_DISABLED` not being honored when
`TelemetryConfiguration.DisableTelemetry` is set in DI
scenarios.](microsoft/ApplicationInsights-dotnet#3156),
[#​3157](microsoft/ApplicationInsights-dotnet#3157)
- [Fix `TrackAvailability` ignoring user-specified `Timestamp` on
`AvailabilityTelemetry`. The timestamp is now emitted as
`microsoft.availability.testTimestamp` so downstream exporters can use
the correct event
time.](microsoft/ApplicationInsights-dotnet#3153)
- [Added `netstandard2.0` target framework to
`Microsoft.ApplicationInsights` package to support customers with shared
libraries targeting
netstandard2.0.](microsoft/ApplicationInsights-dotnet#3142)
- [Fix `TelemetryClient.Context.Cloud.RoleName` set after construction
now applies to all
telemetry.](microsoft/ApplicationInsights-dotnet#3129)
- [Fix bug where Debug/Trace level logs from TrackTrace API were not
emitted to Application
Insights](microsoft/ApplicationInsights-dotnet#3121)
- [Fix Track API calls to not mutate the passed in dictionary if it is
readonly](microsoft/ApplicationInsights-dotnet#3119)
- [Fix `NullReferenceException` in `TelemetryClient.Flush()` and
`FlushAsync()` when called from DI
scenarios](microsoft/ApplicationInsights-dotnet#3125)
- [Fix `ApplicationVersion` ignored:
`ApplicationInsightsServiceOptions.ApplicationVersion` is now applied as
`service.version` on the OpenTelemetry Resource for both AspNetCore and
WorkerService
packages](microsoft/ApplicationInsights-dotnet#3124)
- [Fix `HttpRequestExtensions.UnvalidatedGetHeader` always returning
empty string instead of the actual header value. Restored max-length
enforcement to guard against oversized header
values.](microsoft/ApplicationInsights-dotnet#3126)

## 3.0.0

- [Replaced `netstandard2.0` with `net8.0` target framework in
`Microsoft.ApplicationInsights.NLogTarget`
package.](microsoft/ApplicationInsights-dotnet#3102)

## 3.0.0-rc1

- [Removed `netstandard2.0` target framework from
`Microsoft.ApplicationInsights`,
`Microsoft.ApplicationInsights.AspNetCore`, and
`Microsoft.ApplicationInsights.WorkerService`
packages.](microsoft/ApplicationInsights-dotnet#3091)
- [The JavaScript in `Microsoft.ApplicationInsights.AspNetCore` has been
updated to version
10.](microsoft/ApplicationInsights-dotnet#3078)
- [Centralized package version
management](microsoft/ApplicationInsights-dotnet#3080)
- [Update OpenTelemetry
dependencies](microsoft/ApplicationInsights-dotnet#3080),
[#​3092](microsoft/ApplicationInsights-dotnet#3092)
  - OpenTelemetry 1.15.0
  - OpenTelemetry.Instrumentation.AspNetCore 1.15.0
  - OpenTelemetry.Instrumentation.AspNet 1.15.1
  - OpenTelemetry.Instrumentation.Http 1.15.0
  - OpenTelemetry.Instrumentation.SqlClient 1.15.0
- [Vendored OpenTelemetry.Resources.Azure resource detectors to NETCORE
shared folder, replaced package with vendored
implementation](microsoft/ApplicationInsights-dotnet#3095),
[#​3093](microsoft/ApplicationInsights-dotnet#3093)
- [Added support to disable telemetry via
TelemetryConfiguration.DisableTelemetry](microsoft/ApplicationInsights-dotnet#3084)
- [Removed `EnabledAdaptiveSampling` and replaced with `TracesPerSecond`
and
`SamplingRatio`](microsoft/ApplicationInsights-dotnet#3085)
- [Added `EnableTraceBasedLogsSampler` property to
`ApplicationInsightsServiceOptions` for ASP.NET Core and WorkerService
packages](microsoft/ApplicationInsights-dotnet#3088)
- [Added support for `StorageDirectory` and `DisableOfflineStorage` from
`TelemetryConfiguration` in DI
scenarios](microsoft/ApplicationInsights-dotnet#3088)
- [Update Azure.Monitor.OpenTelemetry.Exporter dependency to
1.6.0](microsoft/ApplicationInsights-dotnet#3094)
 

## 3.0.0-beta2

Added
- Automatic configuration binding from "ApplicationInsights" section in
appsettings.json for both AspNetCore and WorkerService packages with
configuration precedence: environment variables > explicit configuration
> appsettings.json
- Added support for Entra ID (Azure Active Directory) authentication
using Azure.Core.TokenCredential
- Added Self Diagnostics feature
- Updated the default sampler from Fixed Rate to Rate-Limited Sampling.
- Update Azure Monitor Exporter to 1.6.0-beta.2
- Add comprehensive applicationinsights.config support
- Add properties in TelemetryConfiguration to configure underlying
exporter

Bug fix
- Fix TrackMetric(MetricTelemetry) unsupported telemetry type error

## 3.0.0-beta1

- The following Application Insights packages in this repo now use
OpenTelemetry internally. OpenTelemetry is the industry standard for
telemetry collection and provides better interoperability with other
observability tools.
  - Microsoft.ApplicationInsights
  - Microsoft.ApplicationInsights.AspNetCore
  - Microsoft.ApplicationInsights.WorkerService
  - Microsoft.ApplicationInsights.Web
  - Microsoft.ApplicationInsights.NLogTarget
- Classic APIs of the above packages are preserved; calls are translated
to OpenTelemetry telemetry.
- Other packages not listed above (such as certain auto-collectors and
logging adapters that were published from this repo previously) will not
have future versions published. See BreakingChanges.md for details.

Commits viewable in [compare
view](microsoft/ApplicationInsights-dotnet@2.23.0...v3.2.0).
</details>

[![Dependabot compatibility
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=Microsoft.ApplicationInsights.AspNetCore&package-manager=nuget&previous-version=2.23.0&new-version=3.2.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)

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-automerge-start)
[//]: # (dependabot-automerge-end)

---

<details>
<summary>Dependabot commands and options</summary>
<br />

You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits
that have been made to it
- `@dependabot show <dependency name> ignore conditions` will show all
of the ignore conditions of the specified dependency
- `@dependabot ignore this major version` will close this PR and stop
Dependabot creating any more for this major version (unless you reopen
the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop
Dependabot creating any more for this minor version (unless you reopen
the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop
Dependabot creating any more for this dependency (unless you reopen the
PR or upgrade to it yourself)


</details>

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Jarrett Booz (sei-jbooz) pushed a commit to cmu-sei/Steamfitter.Api that referenced this pull request Nov 20, 2026
)

Updated
[Microsoft.ApplicationInsights.AspNetCore](https://github.com/Microsoft/ApplicationInsights-dotnet)
from 2.23.0 to 3.2.0.

<details>
<summary>Release notes</summary>

_Sourced from [Microsoft.ApplicationInsights.AspNetCore's
releases](https://github.com/Microsoft/ApplicationInsights-dotnet/releases)._

## 3.2.0

- Update OpenTelemetry core packages to 1.19.1, instrumentation packages
to 1.19.0, and Azure Monitor OpenTelemetry Exporter to 1.10.0.
- **Breaking change:** Reduce default HTTP client metric volume in
ASP.NET Core and Worker Service on .NET 8+ while retaining request
latency, count, and failure dimensions through
`http.client.request.duration`. Other `System.Net.Http` metrics are now
opt-in through OpenTelemetry `AddView`; dashboards and alerts using them
must [explicitly enable
collection](MigrationGuidance.md#enabling-additional-http-client-metrics).
HTTP dependency tracing and server metrics are unchanged. No new public
API is introduced. Addresses the HTTP metric-volume concern in
[#​3192](microsoft/ApplicationInsights-dotnet#3192).
- [Fix #​3197: `NullReferenceException` when using TelemetryClient APIs
when no connection string is
provided.](microsoft/ApplicationInsights-dotnet#3199)
- [Fix #​3211: `TelemetryClient.TrackDependency(DependencyTelemetry)`
and `TelemetryClient.TrackRequest(RequestTelemetry)` now default an
unset `Timestamp` to `DateTimeOffset.UtcNow` (restoring 2.x behavior)
instead of emitting `0001-01-01T00:00:00Z`, which ingestion
rejects.](microsoft/ApplicationInsights-dotnet#3219)
- [Fix #​3223: The WEB package's activity processors now write the tag
keys the Azure Monitor exporter maps (`enduser.pseudo.id`,
`microsoft.session.id`, `microsoft.synthetic_source`,
`microsoft.user.account_id`), so `user_Id`, `session_Id`,
`operation_SyntheticSource` and `user_AccountId` are populated again
instead of the values landing in `customDimensions` as `ai.user.id`,
`session.id`, `ai.operation.syntheticSource` and `enduser.account`.
`user_AccountId` is also no longer skipped when the authenticated user
cookie is present, and the unmapped `session.isFirst` custom dimension
is no longer
emitted.](microsoft/ApplicationInsights-dotnet#3224)
- [Fix `StartOperation`/`StopOperation` losing or misreporting telemetry
fields. Stopping an operation now exports the fields set on its
telemetry item using the same keys as `TrackDependency`/`TrackRequest`:
dependency `Type`, `Data`, `Target` and `ResultCode` (previously wrong
or empty for HTTP, SQL, `Queue Message` and custom types), request
`Url`, `Source` and `ResponseCode`, `Success`, and custom `Properties`.
The unmapped `OperationName` and `messaging.destination` tags no longer
appear as custom
dimensions.](microsoft/ApplicationInsights-dotnet#3225)



## 3.1.2

## Version 3.1.2
- [Fix `HttpException: Request is not available in this context` in the
WEB package when calling `TrackDependency` from `Application_Start` in
classic ASP.NET. The WEB activity processors now safely handle the case
where `HttpContext.Request` is not yet
available.](microsoft/ApplicationInsights-dotnet#3184)
- [Fix #​3163: `TelemetryConfiguration.CreateDefault()` on classic
ASP.NET now returns a configuration already populated from
`ApplicationInsights.config` (connection string, sampling, storage, live
metrics, request/dependency tracking, etc.). A new
`PreApplicationStartMethod` (`WebApplicationInsightsInitializer`)
materializes and populates the singleton before `Application_Start`
runs, so customer code calling `TelemetryConfiguration.CreateDefault()`
from `Global.asax.cs` no longer gets an empty configuration. The
`ApplicationInsightsHttpModule` no longer carries the config-reading
bookkeeping.
`TelemetryConfiguration.PrependOpenTelemetryBuilderConfiguration` no
longer throws if the configuration was already built — it silently
skips, so a second `TelemetryClient` constructed against an
already-built configuration no longer throws
`InvalidOperationException`.](microsoft/ApplicationInsights-dotnet#3183)


## 3.1.1

## Version 3.1.1
- Update OpenTelemetry and Azure Monitor dependencies to address known
security advisories (e.g.
[GHSA-g94r-2vxg-569j](GHSA-g94r-2vxg-569j)
in `OpenTelemetry.Api` 1.15.1):
microsoft/ApplicationInsights-dotnet#3174
  - OpenTelemetry 1.15.3
  - OpenTelemetry.Exporter.Console 1.15.3
  - OpenTelemetry.Exporter.InMemory 1.15.3
  - OpenTelemetry.Extensions.Hosting 1.15.3
  - OpenTelemetry.Instrumentation.AspNetCore 1.15.2
  - OpenTelemetry.Instrumentation.AspNet 1.15.2
  - OpenTelemetry.Instrumentation.Http 1.15.1
  - OpenTelemetry.Instrumentation.SqlClient 1.15.2
  - Azure.Monitor.OpenTelemetry.Exporter 1.8.0

## 3.1.0

## Version 3.1.0
- [Make `TelemetryContext` properties public and propagate them via
`TelemetryClient`.](microsoft/ApplicationInsights-dotnet#3137)
- [Add fallback to `APPLICATIONINSIGHTS_CONNECTION_STRING` environment
variable for Base, Web, and NLog packages when connection string is not
set via
code.](microsoft/ApplicationInsights-dotnet#3134)
- [Update Azure.Monitor.OpenTelemetry.Exporter to 1.7.0. This includes
updated mappings for telemetry
context.](microsoft/ApplicationInsights-dotnet#3154)
- [Fix `OTEL_SDK_DISABLED` not being honored when
`TelemetryConfiguration.DisableTelemetry` is set in DI
scenarios.](microsoft/ApplicationInsights-dotnet#3156),
[#​3157](microsoft/ApplicationInsights-dotnet#3157)
- [Fix `TrackAvailability` ignoring user-specified `Timestamp` on
`AvailabilityTelemetry`. The timestamp is now emitted as
`microsoft.availability.testTimestamp` so downstream exporters can use
the correct event
time.](microsoft/ApplicationInsights-dotnet#3153)
- [Added `netstandard2.0` target framework to
`Microsoft.ApplicationInsights` package to support customers with shared
libraries targeting
netstandard2.0.](microsoft/ApplicationInsights-dotnet#3142)
- [Fix `TelemetryClient.Context.Cloud.RoleName` set after construction
now applies to all
telemetry.](microsoft/ApplicationInsights-dotnet#3129)
- [Fix bug where Debug/Trace level logs from TrackTrace API were not
emitted to Application
Insights](microsoft/ApplicationInsights-dotnet#3121)
- [Fix Track API calls to not mutate the passed in dictionary if it is
readonly](microsoft/ApplicationInsights-dotnet#3119)
- [Fix `NullReferenceException` in `TelemetryClient.Flush()` and
`FlushAsync()` when called from DI
scenarios](microsoft/ApplicationInsights-dotnet#3125)
- [Fix `ApplicationVersion` ignored:
`ApplicationInsightsServiceOptions.ApplicationVersion` is now applied as
`service.version` on the OpenTelemetry Resource for both AspNetCore and
WorkerService
packages](microsoft/ApplicationInsights-dotnet#3124)
- [Fix `HttpRequestExtensions.UnvalidatedGetHeader` always returning
empty string instead of the actual header value. Restored max-length
enforcement to guard against oversized header
values.](microsoft/ApplicationInsights-dotnet#3126)

## 3.0.0

- [Replaced `netstandard2.0` with `net8.0` target framework in
`Microsoft.ApplicationInsights.NLogTarget`
package.](microsoft/ApplicationInsights-dotnet#3102)

## 3.0.0-rc1

- [Removed `netstandard2.0` target framework from
`Microsoft.ApplicationInsights`,
`Microsoft.ApplicationInsights.AspNetCore`, and
`Microsoft.ApplicationInsights.WorkerService`
packages.](microsoft/ApplicationInsights-dotnet#3091)
- [The JavaScript in `Microsoft.ApplicationInsights.AspNetCore` has been
updated to version
10.](microsoft/ApplicationInsights-dotnet#3078)
- [Centralized package version
management](microsoft/ApplicationInsights-dotnet#3080)
- [Update OpenTelemetry
dependencies](microsoft/ApplicationInsights-dotnet#3080),
[#​3092](microsoft/ApplicationInsights-dotnet#3092)
  - OpenTelemetry 1.15.0
  - OpenTelemetry.Instrumentation.AspNetCore 1.15.0
  - OpenTelemetry.Instrumentation.AspNet 1.15.1
  - OpenTelemetry.Instrumentation.Http 1.15.0
  - OpenTelemetry.Instrumentation.SqlClient 1.15.0
- [Vendored OpenTelemetry.Resources.Azure resource detectors to NETCORE
shared folder, replaced package with vendored
implementation](microsoft/ApplicationInsights-dotnet#3095),
[#​3093](microsoft/ApplicationInsights-dotnet#3093)
- [Added support to disable telemetry via
TelemetryConfiguration.DisableTelemetry](microsoft/ApplicationInsights-dotnet#3084)
- [Removed `EnabledAdaptiveSampling` and replaced with `TracesPerSecond`
and
`SamplingRatio`](microsoft/ApplicationInsights-dotnet#3085)
- [Added `EnableTraceBasedLogsSampler` property to
`ApplicationInsightsServiceOptions` for ASP.NET Core and WorkerService
packages](microsoft/ApplicationInsights-dotnet#3088)
- [Added support for `StorageDirectory` and `DisableOfflineStorage` from
`TelemetryConfiguration` in DI
scenarios](microsoft/ApplicationInsights-dotnet#3088)
- [Update Azure.Monitor.OpenTelemetry.Exporter dependency to
1.6.0](microsoft/ApplicationInsights-dotnet#3094)
 

## 3.0.0-beta2

Added
- Automatic configuration binding from "ApplicationInsights" section in
appsettings.json for both AspNetCore and WorkerService packages with
configuration precedence: environment variables > explicit configuration
> appsettings.json
- Added support for Entra ID (Azure Active Directory) authentication
using Azure.Core.TokenCredential
- Added Self Diagnostics feature
- Updated the default sampler from Fixed Rate to Rate-Limited Sampling.
- Update Azure Monitor Exporter to 1.6.0-beta.2
- Add comprehensive applicationinsights.config support
- Add properties in TelemetryConfiguration to configure underlying
exporter

Bug fix
- Fix TrackMetric(MetricTelemetry) unsupported telemetry type error

## 3.0.0-beta1

- The following Application Insights packages in this repo now use
OpenTelemetry internally. OpenTelemetry is the industry standard for
telemetry collection and provides better interoperability with other
observability tools.
  - Microsoft.ApplicationInsights
  - Microsoft.ApplicationInsights.AspNetCore
  - Microsoft.ApplicationInsights.WorkerService
  - Microsoft.ApplicationInsights.Web
  - Microsoft.ApplicationInsights.NLogTarget
- Classic APIs of the above packages are preserved; calls are translated
to OpenTelemetry telemetry.
- Other packages not listed above (such as certain auto-collectors and
logging adapters that were published from this repo previously) will not
have future versions published. See BreakingChanges.md for details.

Commits viewable in [compare
view](microsoft/ApplicationInsights-dotnet@2.23.0...v3.2.0).
</details>

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

TelemetryClient.TrackDependency no longer default an uninitialized ITelemetry.Timestamp to UtcNow when creating the backing Activity

4 participants