feat: Kinesis delivery stream and Athena query infrastructure to enable queries over the UCAN logs #191
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
View stack outputs
|
vasco-santos
force-pushed
the
feat/kinesis-delivery-stream
branch
from
f44f646
to
90b83db
Compare
vasco-santos
force-pushed
the
feat/kinesis-delivery-stream
branch
from
90b83db
to
9709d14
Compare
|
See grafana integration ✨ |
23 tasks
merging into #191 - mostly put this up so @vasco-santos can review before I push it into the PR he opened! - implement date based partitioning - expand `value` and `out` struct definitions to allow for more interesting queries
Plus example query joining dynamo to ucan logs. Additionally, with input from @dchoi27, two major optimizations: 1. partition by `type` and rework the ucan table to only look at "receipts" - everything in "workflows" shows up in receipts so this reduces the amount of data scanned by ~50% 2. partition by `op` to allow us to create tables that only query a specific operation (ie, `store/add` or `provider/add`) - this lets us add operation-specific schemas with much less clutter in result types Using these optimizations, I've added standalone tables for `store/add`, `upload/add` and `provider/add` UCANs. and reworked the saved queries to use them. --------- Co-authored-by: Vasco Santos <santos.vasco10@gmail.com>
travis
changed the title
Stack outputs updated
|
vasco-santos
commented
Oct 5, 2023
There was a problem hiding this comment.
This looks great to me! Thanks for moving this forward @travis ❤️
travis
approved these changes
Oct 11, 2023
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 PR has an implementation of option 2 from #190 (comment)
This encompasses a fair amount of functionality - partitioning the UCAN logs into S3 buckets, configuring a Glue database and tables, adding example queries to Athena and more. A partial list of functionality follow:
implement UCAN log partitioning in S3
type- everything in "workflows" shows up in "receipts" so this reduces the amount of data scanned by ~50%opto allow us to create tables that only query a specific operation (ie,store/addorprovider/add) - this lets us add operation-specific Glue table schemas with much less clutter in result types than we'd need if we tried to defined all possible inputs and outputs in a single tableuse these partitions to implement standalone tables for receipts in general and the
store/add,upload/addandprovider/addUCANs specifically,add queries that demonstrate the use of all of these tables
add dynamo connector so we can join the UCAN logs to our Dynamo tables in queries
add queries that demonstrate using the Dynamo and Glue tables together