### Problem Although we've implemented the [seat link service](https://gitlab.com/gitlab-org/customers-gitlab-com/issues/1139) this will only be used by connected customers. Firewalled and air-gapped customers still do not have an easy way to determine and provide sales with user usage information. ### Proposal We should aggregate the data needed (below) within the instance and make this data available to manually export. The resulting file should contain the information sales needs to manually process their renewal, add-on license amendment or quarterly/annual user true-up. #### This is what the instance is currently doing: 1. The [cron job worker](https://gitlab.com/gitlab-org/gitlab/blob/master/ee/app/models/historical_data.rb) runs daily at 12:00pm (UTC? Local?) 1. The historical data worker runs except when: * the instance is running Core * when a `Trial license` is loaded 1. The job creates a new record per day, capturing: * the current date * the [active user count](https://gitlab.com/gitlab-org/gitlab/blob/master/ee/app/models/historical_data.rb#L15) at the time of the job #### The export should: 1. Be in a non-editable format 1. Include the following header information 1. license key 1. email associated with the license 1. start and end date of the license 1. company name associated with the license 1. Include the daily `current_active_users_count` *(:no_entry: not `active_user_count: count(User.active)` - this includes non-billable users)* 1. Date/time the count was recorded This was originally an issue (https://gitlab.com/gitlab-org/gitlab/-/issues/213615) and transitioned into this epic once the issue was broken out into smaller pieces. You may find some useful discussion in the original issue.