Shave 200+ms off cost to POST telemetry using proper connection str - #55127
Merged
Conversation
…ing over ikey We should not use instrumentation keys, we should use connection strings. If you want more motivation and context see #55126. Testing with SDK ('unlimited' timeout): full connString exits ~250-300ms ikey connString exits ~535-557ms
Contributor
There was a problem hiding this comment.
Pull request overview
Updates the .NET CLI’s Azure Monitor OpenTelemetry exporter configuration to use a full Application Insights connection string (including explicit ingestion endpoint) instead of relying on an instrumentation-key-only string, with the intent of avoiding redirect overhead and reducing telemetry POST latency.
Changes:
- Replace the Azure Monitor exporter
ConnectionStringvalue with a full connection string includingIngestionEndpoint,LiveEndpoint, andApplicationId.
dsplaisted
approved these changes
Jul 3, 2026
Member
|
FYI @baronfel |
dsplaisted
enabled auto-merge
July 3, 2026 20:24
This was referenced Jul 7, 2026
nagilson
added a commit
that referenced
this pull request
Jul 9, 2026
…ation key Backport of #55127. Use the proper Application Insights connection string (including IngestionEndpoint, LiveEndpoint, and ApplicationId) instead of an instrumentation-key-only connection string. Resolving the endpoints from a bare instrumentation key requires an extra network round-trip; supplying the full connection string shaves 200+ms off the cost to POST telemetry. See #55127 for motivation and measurements. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
nagilson
added a commit
that referenced
this pull request
Jul 9, 2026
…ation key Backport of #55127. Use the proper Application Insights connection string (including IngestionEndpoint, LiveEndpoint, and ApplicationId) instead of an instrumentation-key-only connection string. Resolving the endpoints from a bare instrumentation key requires an extra network round-trip; supplying the full connection string shaves 200+ms off the cost to POST telemetry. See #55127 for motivation and measurements. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> (cherry picked from commit 52c27b6)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Shave 200+ms off cost to
POSTtelemetry using proper connection string over ikeyWe should not use instrumentation keys, we should use connection strings.
If you want more motivation and context see #55126.
Testing with SDK ('unlimited' timeout):
full connString exits ~250-300ms
ikey connString exits ~535-557ms