feat: improved cloudwatch analytics rollup BM-1092 #3381
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
blacha
changed the title
blacha
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.
Motivation
We currently get 10s of millions of requests per day, which are all logged by cloudwatch into a s3 bucket, these logs are very large when looking over the entire history of basemaps, so we rollup the logs into hourly summaries of the requests.
The current implementation rolls up the logs into coarse buckets these buckets give a good overview of usage but do not allow us to dig into more detailed usage trends such as which datasets are used in what formats.
Modification
Introduces a new analytic lambda to run side by side with the existing lambda until we are comfortable to turn off the old lambda.
The logs are now rolled aggregated on more fields such as