Breakout Discussion

March 24, 2022
RFC

• Support for active user status for licensing #612
• ...see comments about discussion notes tasks

Primary metrics to start: (Post MVP)

• users
• make the V1 actve_users (Workspace agent last connected at):
  active_daily_users
active_hourly_users
  Beyond those, this will be a paid feature. Post MVP.

Early Discussions:

• [port the users and active_users over for V2 from V1
• data model
• Make the active-users event an hourly aggregated event.
• create table for metric events
• add corresponding models from v1 for the users and active_users metrics event
• port over the metrics pusher from V1
• add calls to metrics pusher where we need them
• Add API endpoints to read data from the tables
• scope out the cleanup operation
• support for max age of the data in the database (maybe a cron job or something to insert bulk metrics on an interval like an hour or some other time frame?) How do we make it so we don't have to aggregate a bunch of data. NOTE: maintain the data and frequency that Palatir is currently using. Don't add an event every time it happens, filter and collapse the data.
• Use the API key hourly refresh rate to help with the user metrics? What if users have multiple keys? join with owner and select account for query - for active_daily_users and active_houly_users. Nice optimization to reduce database row bloat.
• Concerned about the side effect of a user connecting a BUNCH of times through SSH or similar.
• clean up job to clear out old date to maintain the max number of rows or date cutoff for created date on the data

Frontend (post MVP)
UI / Dashboard would be PAID
We will get customers using V2 and the metrics now and then get feedback based on user input and needs.

• Ability to embed a URL from their own metrics service that they are using for collecting
• Export as CVS
• CLI tool for ASCII grahp