feat: usage/record capability definition #1562
Open
+212
−4
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
fforbeck
changed the title
fforbeck
force-pushed
the
feat/egress-tracking
branch
3 times, most recently
from
01d4f07
to
845af69
Compare
fforbeck
force-pushed
the
feat/egress-tracking
branch
from
845af69
to
b853d98
Compare
alanshaw
requested changes
Oct 11, 2024
fforbeck
commented
Oct 14, 2024
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.
Add
usage/recordCapability definition for Egress Traffic TrackingSummary:
usage/recorddefinition to track egress traffic metrics.w3upInfraupload-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