Why am I not apparently getting any telemetry sent? about vscode-extension-telemetry

[lramos15]

So you set log level to trace and look in the Extension Telemetry output channel?

[tomqwpl]

Yes. Example of what I'm seeing in that channel output window:

[tomqwpl]

Trace level setting:

[lramos15]

Yes. Example of what I'm seeing in that channel output window:

That's the wrong channel, you want the one that says "Extension Telemetry"

[tomqwpl]

That's not what the doco says :-)

[tomqwpl]

So there are two output channels, one for the events that "internal" things produce and one for events that "extensions" produce?

[lramos15]

That's not what the doco says :-)

Thanks for the call out we will work on updating this to include the extension channel cc @gregvanl

The difference between the two channels is what the core VS Code product sends vs what extensions send

[tomqwpl]

So for me, if the point of that channel is to have visibility of the events that are being sent by vscode, for reasons of concerns of privacy and what data is being sent, having two channels is confusing. Not sure I understand why there are are two. Surely I would just want one place where I can see all the telemetry data that VScode is sending on my behalf?

[lramos15]

The reason for there being two is because extensions are installed at your own risk and we want to make it clear to users what something that is an external addon is collecting vs VS Code itself.

[tomqwpl]

Where do I find any information about what I'm looking for at the other end as it were? If I go to the Application Insights website, where do I go to see the telemetry events that have been logged? Am I just being impatient? Does is just take more than some hours for the data to be ingested? I'm not familiar with Application Insights, but a lot of the documentation seems to be around "requests" and the like (i.e web based applications), so I'm unclear how these telemetry events will manifest.

[lramos15]

You should be able to query App insights after just an hour, I've tested a sample extension to ensure the module is working as expected