-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Generate organization usage stats from LMS #6159
Comments
Related: hypothesis/product-backlog#1536 |
There's now reports generated with the new process this can be accessed from this report: Little demo: simplescreenrecorder-2024-06-18_15.05.22.mp4What left for this to be closed:
Known issues:
What I have not done in this stream of work:
|
Current situation
The report system is not prepared to deal with arbitrary contract dates and modifying that would be a fundamental architecture change.
As a stop gap measure we allow now to generate usage reports for an org between two any arbitrary dates. It's up to the user of the admin pages now to use the adecute dates here and copy over the information to HubSpot.
Proposal for next version
An organization might have multiple deals, current and past, we'll store all of them in the DB fetching them from HS every day/week.
Based on the contract dates generate monthly reports for ongoing deals.
This usage reports do take into account sub-organizations. Generating the report for all organizations guarantees we have the data for both the parent orgs and their children.
Generating the reports is an expensive operation so we should rate limit the process. If this is a monthly process it shouldn't be a problem that, worst case scenario, all the report takes a couple of days to be generated.
Store both the count and the actual report (ie a list of rows) in the DB. Having the counts will allow to create graphs comparing deals/dates/periods trivially in metabase. Storing the full report allow to fetch them repeatedly without the cost of generating it.
Once the reports are generated write the result (just the count of unique users) in HS.
The text was updated successfully, but these errors were encountered: