feat: track service unit cost of runs in database (SBP-445) - #113
Merged
Conversation
amandazhuyilan
approved these changes
Jul 29, 2026
amandazhuyilan
left a comment
Collaborator
There was a problem hiding this comment.
Looks good to me - looking forward to seeing some csv generated once this is in
This file contains hidden or 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
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.
Pull Request
Summary
SBP-445: retrieve the usage report (uploaded to S3) and record the actual service units for the workflow run in the database
Changes
UsageReport.csvto results/output specs so it gets synced along with other resultsservice_usagecolumn toWorkflowRunDB tableservice_usagecolumn to DB admin viewHow to Test
Run
uv run pytestType of change
Checklist