-
Notifications
You must be signed in to change notification settings - Fork 46
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
User reports broken at https://portal.azure.com #209
Comments
This is a duplicate of #197 It sounds like maybe it's worth adding a flag for this information. VS Code tries to avoid PII in every place possible which includes this library. Instead we recommend custom queries utilizing |
Thanks @lramos15. I reopend it, because I felt that without user reports that the value telemetry is massively diminished and requires brainstorming about alternatives. If you have machineid then why not report that value also for the userid so the dashboard user reports work again. The number of users that share the same machine is neglectable imho. Even for Codespaces I would would be fine with different ids for different workspaces as our telemetry show that desktop VS Code is the massive majority. Not being able to report on unique user trends defeats the whole purpose of telemetry imho as that is the statistic management wants to know. |
This is what I would like to do, just need to figure out what property to assign it to in the App insights constructor |
I upgraded our extension from using
"vscode-extension-telemetry": "0.4.3"
to"@vscode/extension-telemetry": "0.9.6"
.Now when I log on to my Application Insight dashboard at https://portal.azure.com I am not able to run the User reports anymore. I can see that since I switched the library that those events do not have user information anymore. In the transaction search I was able to select any event and review the users timeline. With the data coming from the new library all the usr-related shortcuts are gone.
I consider this a major regression as I am not able to collect statistics about the number of unique users we have over time and how many user are using specific features anymore.
The text was updated successfully, but these errors were encountered: