<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=387959) </details> <!--IssueSummary end--> ## Problem We need to collect usage metrics on several areas of the Web IDE’s usage. It is challenging to instrument many functionalities of the Web IDE that are provided by the underlying VSCode fork. ## Spike goals VSCode has built-in robust instrumentation tooling, and it already covers most features provided by this editor. The goal of this spike is to determine if we can intercept the editor’s [telemetryService](https://gitlab.com/gitlab-org/gitlab-web-ide-vscode-fork/-/blob/main/src/vs/platform/telemetry/common/telemetryService.ts#L135) and re-route the logs to GitLab’s snowplow.