-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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.
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
Implement analytics on file opening events in VS Code #6981
Comments
@akosyakov will update here with some more thoughts/notes on a technical solution. |
/assign |
Relates to: gitpod-io/openvscode-server#257 |
From vscode telemetry:
|
Hey @jeanp413! Looks like we are thinking pretty much the the same thing [1]. The events you suggest are (almost exactly) the same ones I suggested on the telemetry PR. But... I didn't manage to initiate/see the We'll need to find a mechanism to throttle / debounce the very frequent events though, like |
Let's consider this ticket done, when it's deployed, etc, and let's see where the other file events might be relevant in relation to the other epic: #7326 |
@loujaybee next VS Code stable release will be only in Feb, if you need it early please ask @jeanp413 to cherry pick changes into release branch and do a proper release. |
I'm cloing it, but keep in awaitting deployment since it is not in stable. |
As part of onboarding, we need events that define when a user has achieved recognition of the "read-only" aspects of Gitpod. A reasonable heuristic at this point would be to see if the user has interacted with the directory structure and/or the file system. This ticket is to instrument these events within VSCode to see when a user has opened a workspace and explored the internal file structures.
This metric is a candidate for an "end" point of the user onboarding funnel. However, #6896, would be a stronger metric for the onboarding funnel, however, this metric would be useful as a fallback for #6896 if we find that tracking commits prove to be challenging.
The text was updated successfully, but these errors were encountered: