Track when Desktop IDE URI redirect fails

[loujaybee]

When redirecting to JetBrains or other Desktop IDE's we use a redirect URI, however, it has been observed that on occasions that this redirect does not work as expected, sometimes where an exception is thrown with no user action implied. This is especially challenging during a users onboarding journey where they're likely to bounce/churn if they cannot easily set up a desktop IDE.

The following information should be considered:

• Device
• OS/Hardware etc
• The URI the user is redirecting to
• The IDE the user is redirecting to

Relates to:

• Introduce app-specific error codes to Gitpod #12089

[akosyakov]

We actually can add some analytics into Gateway plugin as @jeanp413 does it right now for VS Code desktop extension. In order to track installations, attempts to connect, their success/failure and reasons. Another issue?

[stale]

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.