feat(event): Add view to allow caching of charge/filters for billable_metrics #2231
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
jdenquin
approved these changes
Jul 4, 2024
vincent-pochet
force-pushed
the
feat-event-filter-view
branch
from
6daf851 to
5ddaf06
Compare
vincent-pochet
force-pushed
the
feat-event-filter-view
branch
from
5ddaf06 to
09d1d57
Compare
ancorcruz
pushed a commit
that referenced
this pull request
Jul 7, 2024
…_metrics (#2231) This PR is part of the real-time aggregation epic This PR adds a new `billable_metrics_grouped_charges` database view. It selects the charges for each organization/billable metric code/plan tupple. It will be used to route events received on the ingest service to the right bucket in order to perform a pre-computation and allow future "real time aggregation"
vincent-pochet
added a commit
that referenced
this pull request
Jul 18, 2024
## Context This PR update the `billable_metrics_grouped_charges` view introduced in #2231 to allow a better filtering of events related to in advance charges. Today all event having the code of a billable metric related to an in advance charge is sent to the event_worker even if no subscription is attached to it leading to a lot of load on the worker for jobs that will in the end not be charged ## Description This PR will allow us to the update the ingest service so that only event related to an in advance charge on a active subscription are sent to the event worker
abdussamadbello
pushed a commit
to abdussamadbello/lago-api
that referenced
this pull request
Aug 8, 2024
…#2300) ## Context This PR update the `billable_metrics_grouped_charges` view introduced in getlago#2231 to allow a better filtering of events related to in advance charges. Today all event having the code of a billable metric related to an in advance charge is sent to the event_worker even if no subscription is attached to it leading to a lot of load on the worker for jobs that will in the end not be charged ## Description This PR will allow us to the update the ingest service so that only event related to an in advance charge on a active subscription are sent to the event worker
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 real-time aggregation epic
Description
This PR adds a new
billable_metrics_grouped_chargesdatabase view. It selects the charges for each organization/billable metric code/plan tupple. It will be used to route events received on the ingest service to the right bucket in order to perform a pre-computation and allow future "real time aggregation"