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
Right now there is no way to collect metrics and logs from clients like VS Code Browser, Desktop, JB Gateway and local app, since the supervisor is a point of failure itself. We are relying on analytics for that, but it is rather overkill for counters of connections and errors. Instead we should add new API endpoints to ide proxy which allow to collect metrics and logs, such endpoints should be rate limited. Under the hood log endpoint should redirect to GCP error logging in a special project. As first use case we can have a look at refactoring telemetry of connections between VS Code Browser and Server.
The text was updated successfully, but these errors were encountered:
Right now there is no way to collect metrics and logs from clients like VS Code Browser, Desktop, JB Gateway and local app, since the supervisor is a point of failure itself. We are relying on analytics for that, but it is rather overkill for counters of connections and errors. Instead we should add new API endpoints to ide proxy which allow to collect metrics and logs, such endpoints should be rate limited. Under the hood log endpoint should redirect to GCP error logging in a special project. As first use case we can have a look at refactoring telemetry of connections between VS Code Browser and Server.
The text was updated successfully, but these errors were encountered: