Track add_on_metrics in HistoricalData
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Background
We currently track add-on metrics as part of seat link records for online cloud licenses to provide visibility into Duo seat adoption for Self-Managed customers.
Now that offline cloud license customers can purchase Duo Enterprise, we will need to capture this same adoption data from these users and ensure these metrics are part of the offline license data sharing process.
In order to allow the offline cloud license usage export file to contain these add-on metrics, we will need to start tracking this as part of GitLab's historical license data.
Proposal
Using the abstraction created in #550997 (closed), generate the add-on metrics and save it to the new HistoricalData record that is created as part of the HistoricalData.track! method
Test the HistoricalDataWorker using various offline cloud licenses with and without add-ons, along with the current license usage exports to ensure no breaking changes occur.