feat(DailyUsage): Add daily_usages:fill_history task #2751
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
vincent-pochet
force-pushed
the
feat-daily-usage-history
branch
5 times, most recently
from
c3534c9 to
c420967
Compare
vincent-pochet
force-pushed
the
feat-daily-usage-history
branch
2 times, most recently
from
cedfd47 to
b354e6d
Compare
vincent-pochet
force-pushed
the
feat-daily-usage-history
branch
from
b354e6d to
5f8636e
Compare
vincent-pochet
changed the title
rsempe
approved these changes
Nov 8, 2024
vincent-pochet
added a commit
that referenced
this pull request
Nov 21, 2024
…rvice (#2843) ## Context A rake task to fill the history data of the DailyUsage model was recently added (#2751) Since this task is recomputing the usage for all subscriptions of an organization for a defined number of days, without taking advantage of the usage cache, it can be very slow. Also, an organization can have a large number of subscription, making the current linear approach very inefficient. ## Description This PR extracts the existing logic from the rake task itself in a job/service, taking advantage of sidekiq to parralelize the work
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Context
This PR is part of the Usage Revenue and unit.
Today, Lago does not offer a way to retrieve customer usage with a granularity lower than the billing period (via invoices and fees). On the other end, it is possible to get the current usage for a customer/subscription, but this usage is just a “snapshot” of the usage a the current time.
Description
This PR adds a rake task to fill the daily usage history for a specific organization