Migrate to custom OTel Exporter in `dotnetup` to prevent perf delay and data loss#55421

Open

nagilson wants to merge 26 commits into

dotnet:release/dnupfrom

nagilson:nagilson-new-otel-exporter

Commits on Jul 22, 2026

Telemetry Client uses shutdown in `dotnetup` over flush and uses new local lib
nagilson
committed
allow toggling the drain in persistent storage exporter
nagilson
committed
reference custom otel exporter
nagilson
committed
Document flush control env var
nagilson
committed
add dotnet cli telemetry timeout constant to dotnetup constants
nagilson
committed
test that it uses custom flush / shutdown budgets - even if shutdown is no longer tied to data being POST'ed it is still tied to the overall correct deconstruction of the telemetry services (might …
nagilson
committed
add backoff to POST requests in custom exporter lib
nagilson
committed
Add backoff retry to the http upload transport
nagilson
committed
Add reference to dotnet's sdk telemetry path
nagilson
committed
include the cli path folder calculator for consumption to get sdk storage dir
nagilson
committed
Add a sub process to drain telemetry at the end for non one and done environments.
nagilson
committed
Add detached process upload for telemetry
nagilson
committed
Add basic test for http retry on post
nagilson
committed
Add tests to ensure it backs off if the transport throws to prevent trying to send data if its throttled
nagilson
committed
Merge branch 'release/dnup' into nagilson-new-otel-exporter
nagilson
authored
try to avoid exceptions from async tasks throwing due to a new thread releasing a mutex
nagilson
committed
Merge branch 'nagilson-new-otel-exporter' of https://github.com/nagilson/sdk into nagilson-new-otel-exporter
nagilson
committed
Fix usings
nagilson
committed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Migrate to custom OTel Exporter in `dotnetup` to prevent perf delay and data loss#55421

Migrate to custom OTel Exporter in `dotnetup` to prevent perf delay and data loss#55421
nagilson wants to merge 26 commits into
dotnet:release/dnupfrom
nagilson:nagilson-new-otel-exporter

Commits on Jul 22, 2026

Telemetry Client uses shutdown in `dotnetup` over flush and uses new local lib

allow toggling the drain in persistent storage exporter

reference custom otel exporter

Document flush control env var

add dotnet cli telemetry timeout constant to dotnetup constants

test that it uses custom flush / shutdown budgets - even if shutdown is no longer tied to data being POST'ed it is still tied to the overall correct deconstruction of the telemetry services (might …

add backoff to POST requests in custom exporter lib

Add backoff retry to the http upload transport

Add reference to dotnet's sdk telemetry path

include the cli path folder calculator for consumption to get sdk storage dir

Add a sub process to drain telemetry at the end for non one and done environments.

Add detached process upload for telemetry

Add basic test for http retry on post

Add tests to ensure it backs off if the transport throws to prevent trying to send data if its throttled

Merge branch 'release/dnup' into nagilson-new-otel-exporter

try to avoid exceptions from async tasks throwing due to a new thread releasing a mutex

Merge branch 'nagilson-new-otel-exporter' of https://github.com/nagilson/sdk into nagilson-new-otel-exporter

Fix usings

Commits on Jul 23, 2026

add tests for telemetry drainer for blob retry delays

consider framework conditional for using better .net core methods

Add full depth e2e tests for detached draining, post, telemetry retention + fix for env script

Merge branch 'release/dnup' into nagilson-new-otel-exporter

deduplicate exporters and telemetry path calculation

dont continue to try to upload data that will never succeed to POST

dont allow telemetry blobs that will never succeed to persist indefinitely

test rejected blobs that are retrieable can be retried