[Telemetry] Add section about experiments #8965
Open
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
sandy081
previously approved these changes
Oct 13, 2025
isidorn
reviewed
Oct 13, 2025
docs/configure/telemetry.md
Outdated
|
|
||
| VS Code uses an A/B experimentation system to roll out new features to a subset of users before making them generally available. This helps us validate that a new feature is working as expected across a diverse set of users before rolling it out to everyone. By participating in experimentation, you help us improve the quality of VS Code and can help shape the future of the product through early feedback. | ||
|
|
||
| To enable this experimentation system, VS Code uses the usage data telemetry data to determine which users should receive the new feature. If you disable usage data telemetry by setting `setting(telemetry.telemetryLevel)` to `error`, `crash`, or `off`, experimentation is not available to you and the roll out of new features to you might be delayed. |
There was a problem hiding this comment.
typo "data telemetry data"
isidorn
reviewed
Oct 13, 2025
docs/configure/telemetry.md
Outdated
|
|
||
| VS Code uses an A/B experimentation system to roll out new features to a subset of users before making them generally available. This helps us validate that a new feature is working as expected across a diverse set of users before rolling it out to everyone. By participating in experimentation, you help us improve the quality of VS Code and can help shape the future of the product through early feedback. | ||
|
|
||
| To enable this experimentation system, VS Code uses the usage data telemetry data to determine which users should receive the new feature. If you disable usage data telemetry by setting `setting(telemetry.telemetryLevel)` to `error`, `crash`, or `off`, experimentation is not available to you and the roll out of new features to you might be delayed. |
There was a problem hiding this comment.
I would also explain why this is. For example "to validate if a feature is good, we need to see how users use the feature, thus users that disable telemetry are not part of feature roll-outs since we can not measure impact"
isidorn
previously approved these changes
Oct 13, 2025
|
@sbatten Can you review the updates to the telemetry doc? Thanks! |
sbatten
reviewed
Oct 15, 2025
sbatten
reviewed
Oct 15, 2025
|
@sbatten Thanks for reviewing - applied your suggestions! |
|
@sbatten Can you do a final review to get this published. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
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.
This pull request updates the telemetry documentation for Visual Studio Code to clarify how telemetry data is used, especially regarding feature rollouts and experimentation. The changes improve transparency about the role of telemetry in enabling early access to new features and update instructions and terminology for disabling telemetry.
Fixes #8949