usage: query usage for recently active users #173
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
gioelecerati
changed the title
gioelecerati
force-pushed
the
gio/usage/active-users
branch
from
adb66a0
to
7d6ec86
Compare
gioelecerati
changed the title
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.
This removes any need to fetch users by activity on studio and doing multiple api calls to data to retrieve usage for these users. In a single api, you can fetch usage for active users in a requested timeframe
Also, this creates a new endpoint
groupedwhere you can pass a list of userIds with their billing cycle and retrieve their usage in a single query