Repository navigation
Conversation
Cloud Logging retention and query limits make it impractical to analyze task outcomes across weeks of runs. This sink routes only the `stage_summary` records (one per task stage, from both the `python` and `k8s-logs` logs) into BigQuery tables partitioned by day, with partitions expiring after 90 days.
This was referenced Oct 27, 2026
This branch has not been deployed
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.
Cloud Logging retention and query limits make it impractical to analyze task outcomes across weeks of runs. This sink exports only the
stage_summaryrecords from #5557 (one per task stage, from both thepythonandk8s-logslogs) into BigQuery tables partitioned by day, with partitions expiring after 90 days.It's independent of #5557 and harmless without it. It's also entirely optional: if you'd rather not provision this in every deployment, we can drop it and keep the export on our side. One known gap: Swarming bots that log to a separate
LOGGING_CLOUD_PROJECT_IDaren't covered by a sink in this project.Feedback on the dataset location, retention, or naming is very welcome.
cc @IvanBM18 @g-ortuno for visibility