rfc: egress tracking #37
Conversation
fforbeck
force-pushed
the
rfc/egress-tracking
branch
3 times, most recently
from
f7dba03
to
1971015
Compare
fforbeck
force-pushed
the
rfc/egress-tracking
branch
from
1971015
to
2318425
Compare
|
|
||
| - **Question:** How can logs and monitoring be effectively implemented in both alternatives? Does Alternative 2’s reliance on signed receipts offer sufficient logging capabilities? Do we really need these signed receipts? | ||
|
|
||
| - **Answer:** ??? |
There was a problem hiding this comment.
I do think it's at least moderately important to have those signed receipts - I suspect customers are going to want as much information as possible about what they're being charged for. We might be able to just aggregate metrics around them and store in Glacier for the sake of minimizing costs, but having signed receipts for each request feels like something that will eventually be fairly useful?
@alanshaw is right that there will be a LOT of them and they'll probably have different retention policies than most other UCAN invocation receipts, though for the sake of getting this shipped we might want to use the upload API service for now and add a new service later?
It definitely might be worth adding a new service that uses a similar invocation processing pipeline and different retention policies - ideally we'd move egress tracking receipts from S3 hot storage to Glacier pretty quickly for these, faster than for most other receipts we store.
### Add `usage/record` Capability definition for Egress Traffic Tracking **Summary:** - Introduced a new capability `usage/record` definition to track egress traffic metrics. - The `w3upInfra` upload-api will be updated to implement this new capability by leveraging Stripe's Usage Records API for accurate tracking and billing. RFC: storacha/RFC#37
📚 Preview
Storacha Network aims to implement a scalable, automated mechanism for tracking egress traffic and updating Stripe’s Usage Record API with relevant data for accurate customer billing, this RFC outlines two approaches with distinct trade-offs.