-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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 changes to the .gitpod.yml
#6894
Comments
.gitpod.yml
@loujaybee this is a very interesting concept. I wonder if we could do more things on the client by just adding a tailored extension, which would take care of the whole |
This one is a little tricky, so probably best if @akosyakov is able to collaborate with whoever picks this up to come up with a plan. As with all of the analytics tickets, having something working initially is better than trying to overthink it, and come up with something super comprehensive. |
There is potentially some tracking added already here in the supervisor [1]. Let's investigate if we have that data, and if those events are working as expected. |
@jakobhero Could you check please whether we have |
Hi @akosyakov, i had another look at the events coming into Segment and |
I think it is configured here: gitpod/components/common-go/analytics/analytics.go Lines 42 to 46 in 0851301
gitpod/components/common-go/analytics/analytics.go Lines 92 to 102 in 0851301
@csweichel Could it be that |
For what it's worth, dashboard and server side analytics calls also depend on the configuration of those as far as i know and they don't seem to be affected. |
yes, i see it in each workspace |
@akosyakov are you working on this if not what still needs to be done? |
@jeanp413 not actively I wanted to sync with @csweichel with how generally we can get analytics directly from workspace to Segment in secure way. If it is not possible then the fix is rather simple, use GitpodServer in supervisor to track this event. You can make a PR for it, but we delay merging after talking to Chris. |
@akosyakov is that related to this #7257 (comment). If so I'd be fine waiting as that would also help make straightforward sending telemetry in vscode core (instead of creating a web socket connection) |
@jeanp413 since we are fine to use untrusted, it would be good to investigate why supervisor cannot send to segment, we don't log any errors there to avoid spamming logs, but maybe it is good to enable them temporarily |
Removing from scheduled as not a great deal we can do whilst we're waiting for visualisation dashboards to be created. Since I've now closed the following epic (which used to contain this ticket). I'll now move this out of groundwork. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Context: This one is important as it will give us data around when a user is updating this file as part of their onboarding journey. e.g. are users updating the file on their first visit? second visit? etc
We would like to know: if / when a user is changing or updating their gitpod.yml.
Ideally, we would gather fine-grained data on which properties the user is updating on the YAML file. This is so we can optimize how and when we present certain features to our users.
Considerations:
gitpod.yml
that are interesting for us to track and why.Note: If necessary we can break this ticket down, simply knowing that the user has changed the file / added it would deliver value at this stage.
The text was updated successfully, but these errors were encountered: