feat(daily_usage): Add DailyUsage model #2718
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
added a commit
that referenced
this pull request
Oct 29, 2024
## Context This PR is part of the Usage Revenue and unit. It follows #2718 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 the base logic to compute the daily usage for every active subscription. For now the feature is enabled by checking the presence of the `LAGO_ENABLE_REVENUE_ANALYTICS` environment variable.
vincent-pochet
added a commit
that referenced
this pull request
Nov 4, 2024
## Description This PR fixes a flacky test that was introduced by the recent daily_usage feature See #2718
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 is the first part of a feature implementing a daily usage monitoring. Is simply introduce a new
DailyUsagemodel to store the computed daily usage.