Re: [ecd-tools-wg] Telemetry for openvsx extensions

[Mike Milinkovich <mike.milinkovich@xxxxxxxxxxxxxxxxxxxxxx>]

On 2020-06-23 3:38 p.m., Brad Micklea wrote:

I think it comes from our corporate web analytics platform - as a side effect of Red Hat hosting it. It's not connected to OpenVSX in any way. But I expect that we'd like to see additional telemetry there too.

Right. But I think the VSCode telemetry is tracking what people are doing on their desktops. Tracking user interactions on a website is a simpler problem, if for no other reason than the user will have already accepted your terms of use and privacy policy to get access to the tool.

Venkat, I am assuming you're interested in telemetry on the desktop. If so, the first question is whether you are looking for data to be collected by the ECD Tools WG, or are you proposing the creation of a standard API that extensions can use to implement their own telemetry collection?

On Tue, Jun 23, 2020 at 3:36 PM Venkatauday Balabhadrapatruni <venkatauday.balabhadrapatruni@xxxxxxxxxxxx> wrote:

Thanks Brad. Any details on how that is done? I guess for the hosted service, this information is not available for all to see? A related q is, how would this relate to the openvsx extensions?

Cheers,
 
Venkat Balabhadrapatruni
Broadcom Distinguished Engineer, Mainframe Software Division
 
5465 Legacy Dr, Suite 700 | Plano, TX 75024 
Office: +1 214 471 9387| venkatauday.balabhadrapatruni@xxxxxxxxxxxx

On Jun 23, 2020, 1:31 PM -0500, Brad Micklea <bmicklea@xxxxxxxxxx>, wrote:

I know our hosted Eclipse Che service has telemetry associated with it so we can see how many people are signing up, how often they're using it and for how long, what stacks they're using, etc...

On Mon, Jun 22, 2020 at 9:36 AM Venkatauday Balabhadrapatruni <venkatauday.balabhadrapatruni@xxxxxxxxxxxx> wrote:

Hi All 

We at Broadcom are moving towards taking advantage of the telemetry capabilities in VSCode (https://code.visualstudio.com/docs/getstarted/telemetry) in all of our VSCode extensions. The intent of course is to understand how our customers are using the extensions and focus on addressing any issues that are hindering the adoption or usage of the features. We have worked with our customers to define the kind of metrics we would be capturing - and currently the intent is to focus on understanding:

• What extensions are being used or not being used?
• What are the usability issues, if any the users are running into? 
• What are the performance issues, if any the users are running into?

Of course the set of metrics/events being collected will depend on the extension, there is common data like OS, Location of users etc. 

As we are developing these capabilities across our VSCode extensions, questions are popping up on how telemetry would work in the cloud based or hosted IDE’s. We want to understand what architectural and design considerations for hosted IDE’s we need to consider as we ramp up the telemetry capabilities for our VSCode extensions. 

The intent of this thread is to understand what efforts if any are on going re: telemetry or if this is something that needs to be explored in the context of OpenVSX extensions.

Let me know if you need any more information.