Extension telemetry stopped collecting ~3 weeks ago about vscode-extension-telemetry

[lramos15]

Try updating your webpack externals

https://github.com/microsoft/vscode/blob/24739b3e01f8f7d27efa33e7ff9101fb8157032d/extensions/shared.webpack.config.js#L147-L154

[kingdonb]

My extension is this one:

https://github.com/weaveworks/vscode-gitops-tools

and the fixes I've tried are on the edge branch, we did a major upgrade on the extension unrelated to telemetry in the last 30 days and it's possible that we upgraded something, but seems unlikely that 100% of the clients would have upgraded and received it all at once. The big upgrade was published on July 28, so I'm pretty sure that had nothing to do with it.

[lramos15]

That's interesting, #183 uses a completely different code path (not App insights) so a lot of the issues there shouldn't affect you. Did you update the module recently?

[kingdonb]

Not until after I started having issues, no. At that point I realized my engine and the dependency itself were both quite out of date, so I figured the best plan was to upgrade.

I tried that in the edge branch, we have pushed updates to (attempt to) use the latest version of the telemetry package, but all of my experiments have been failure and I haven't seen any sign of telemetry since that day in August, when we did no release.

I think it must have been we're using a deprecated path, but I haven't found anything to clarify it since I posted this. No sign that we are even ingesting metrics at all except for the "Server exceptions and dependency failures" which all appeared to be server exceptions, however I don't understand how to delve into those errors and see details about them.

[kingdonb]

@lramos15 Not sure if we actually did that, but it looks like September 17 telemetry started up again.

This was 2 days after our most proximate release, and it was another 2 weeks almost before we made another release after that. I'm inclined to think that something was broken at Microsoft Azure and they fixed it, (or else there was something broken about my account subscription and it's been fixed by someone else when I wasn't paying attention.)

🤷 closing