You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In order to send events from the dashboard and other places (vs code, local companion app, etc.) to our analytics end-point, the server should expose an API. I think it would be easiest to add a trackEvent method to the websocket protocol.
The text was updated successfully, but these errors were encountered:
We already have the AnalyticsWriter API in gitpod-protocol. We could implement the AnalyticsWriter interface on the gitpod-server API. Downside is that we bloat extend that API further. Upside: we get authentication along for the ride and don't have to expose the segment write key/config.
In order to send events from the dashboard and other places (vs code, local companion app, etc.) to our analytics end-point, the server should expose an API. I think it would be easiest to add a
trackEvent
method to the websocket protocol.The text was updated successfully, but these errors were encountered: