Store `seats_currently_in_use` field in gitlab.com `subscription` table
Problem
The Data team needs to be able to replicate the GitLab UI Billing/Usage values that Customers/Users see on the GitLab UI into internal reports (for Sales, Product, etc) from the data warehouse. To ensure one SSOT for these calculations, it would be ideal that these values are stored in the same location at the same data granularity.
This issue specifically tracks storing the seats_currently_in_use
field in gitlab.com subscription
table. I will leave it up to the person who picks up this ticket to decide if this issue should also track making the UI read and use this value or if that should be a separate issue. Thank you for your help!
FYI @amandarueda , @jbrennan1 , @derekatwood , @jeromezng
Proposal
Currently, the max_seats_used
is stored into the gitlab_subscriptions
table via this cron job. It would be ideal if this cron job also stored the other values on the billing page into the datawarehouse at the same time and that the UI was retrieving this value so that there can be more consistency across systems in terms of our internal and external reporting of this value.