Report client connection events to the tunnel service #546
Conversation
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
jasongin
force-pushed
the
dev/jasongin/tunnelevent
branch
from
d61ced1 to
f869e51
Compare
JacobRoberts
previously approved these changes
Aug 11, 2025
JacobRoberts
approved these changes
Aug 11, 2025
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.
TunnelEventcontract (all languages)ReportEvent()method on the tunnel management client which uploads events to the tunnel service as a background task. The upload endpoint is specific to a tunnel and is authenticated with the same credentials used for tunnel access. (C# + TS)The tunnel service will use these client events (correlated with server telemetry) to support improved diagnostics and reporting for tunnel connection issues and success rates.
The events do not include any user data or personally-identifiable information such as usernames, machine names or IP addresses, or any unique machine identifiers. Still, the events reporting is disabled by default and must be enabled by the application via the
EnableEventsReportingproperty on the tunnel management client.