Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Tooling to allow for the extraction of telemetry metadata #75524

Closed
lramos15 opened this issue Jun 14, 2019 · 1 comment
Closed

Tooling to allow for the extraction of telemetry metadata #75524

lramos15 opened this issue Jun 14, 2019 · 1 comment
Assignees
@lramos15
Labels
feature-request Request for new features or functionality

Comments

@lramos15
Copy link
Member

Currently all our telemetry events are annotated with specialized JSON comments that dictate why we collect the data. It would be easy enough to extract these comments into a single JSON file so that the telemetry data which VS Code collects could be viewed. Currently, the only way to view telemetry is with the --verbose flag which only shows you the telemetry which events which you have fired and not the entire catalog of events which could be sent.
@lramos15 lramos15 added the feature-request Request for new features or functionality label Jun 14, 2019
@lramos15 lramos15 added this to the June 2019 milestone Jun 14, 2019
@lramos15 lramos15 self-assigned this Jun 14, 2019
@kieferrm kieferrm mentioned this issue Jun 14, 2019
Closed
18 tasks
@jrieken jrieken removed this from the June 2019 milestone Jun 27, 2019
@kieferrm kieferrm mentioned this issue Jul 5, 2019
Closed
29 tasks
@lramos15
Copy link
Member Author

Tool released see https://www.npmjs.com/package/vscode-telemetry-extractor

@vscodebot vscodebot bot locked and limited conversation to collaborators Sep 2, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@lramos15 lramos15

Labels
feature-request Request for new features or functionality
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jrieken @lramos15