Bring VS Code telemetry reporting in DevKit to match log level requirements of VS #69444
Conversation
This file contains 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
dotnet-issue-labeler
bot
added
Area-IDE
untriaged
ryzngard
commented
Aug 9, 2023
| [MemberNotNullWhen(false, nameof(_telemetryReporter))] | ||
| private static bool IgnoreReporting(LogMessage logMessage) | ||
| => _telemetryReporter is null || | ||
| logMessage.LogLevel < LogLevel.Information; |
There was a problem hiding this comment.
Matches
ToddGrun
approved these changes
Aug 9, 2023
dibarbet
approved these changes
Aug 9, 2023
arunchndr
approved these changes
Aug 9, 2023
ghost
added this to the 
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.
The volume of telemetry for DevKit is orders of magnitude higher per machine than VS because we weren't filtering on LogLevel in the same way. This brings the behavior to be the same.