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
This is a collection of tasks related to stabilizing our internal tracking of user activity from a workspace. Once completed, the code should ensure that there's a single place to keep track of user activity in order to reduce the chance of bugs where we forget to implement it properly for future features.
chore: remove stats batcher and workspace usage tracker #13393 - This was originally open because I had a hypothesis this was not helping much but required a good bit of code. @johnstcn helped me by running load tests to determine these were in fact doing some heavy lifting and validated their usage.
Once we update how the internal APIs handle tracking of user activity we must update things like the CLI and jetbrains plugins to be compatible with the new flows. This will ensure users will continue to see accurate data from these external sources.
Modify /usage endpoint to accept a payload and call StatsCollector.Collect(), returning a SessionID if required
Update CLI commands (coder ssh, etc.) to periodically send a payload to /usage
Include an option to skip tracking
Update coder-jetbrains plugin to periodically send payloads to /usage
Ensure that periodic background activity does not send unwanted activity bumps
Release Readiness
Before release we need to make sure that the new code paths are stable and ready for customers to consume. This requires testing and release documentation for how to safely upgrade.
Scaletest new changes
Require cli upgrade in release notes
The text was updated successfully, but these errors were encountered:
This is a collection of tasks related to stabilizing our internal tracking of user activity from a workspace. Once completed, the code should ensure that there's a single place to keep track of user activity in order to reduce the chance of bugs where we forget to implement it properly for future features.
Internal APIs
External APIs
Once we update how the internal APIs handle tracking of user activity we must update things like the CLI and jetbrains plugins to be compatible with the new flows. This will ensure users will continue to see accurate data from these external sources.
/usage
endpoint to accept a payload and callStatsCollector.Collect()
, returning aSessionID
if requiredcoder ssh
, etc.) to periodically send a payload to/usage
/usage
Release Readiness
Before release we need to make sure that the new code paths are stable and ready for customers to consume. This requires testing and release documentation for how to safely upgrade.
The text was updated successfully, but these errors were encountered: