Add data point for global.json state telemetry collected #49294
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
There was a problem hiding this comment.
Pull Request Overview
This PR updates the telemetry documentation to include a new data point that tracks the state of global.json when CLI commands are invoked.
Key changes:
- Added documentation for a new telemetry data point that captures
global.jsonstate with four possible values:not_found,valid,invalid_json, andinvalid_data
Co-authored-by: Copilot <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
This pull request updates the telemetry documentation to include a new data point collected by the CLI. Specifically, it now describes how the state of
global.jsonis captured when a command is invoked.Telemetry documentation update:
global.jsonstate at command invocation, detailing states:not_found,valid,invalid_json,invalid_data.Fixes #48493
Internal previews