Repository navigation
Conversation
Currently, diagnosing where a ClusterFuzz task failed or spent its time requires scraping unstructured Cloud Logging prose across preprocess, main, and postprocess stages. With this change, every stage exit emits a single `Stage <stage> finished.` log carrying `jsonPayload.extras.stage_summary` with stage status, duration, error type, variant, and per-step status, duration, and failure or skip reason across all 8 UTasks and 3 TrustedTasks. Also provision a filtered Cloud Logging sink (`stage-summaries`) in Terraform that routes only `stage_summary` records into a partitioned BigQuery dataset (`stage_summaries`).
Author
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.
Currently, diagnosing where a ClusterFuzz task failed or spent its
time requires scraping unstructured Cloud Logging prose across
preprocess, main, and postprocess stages. With this change, every
stage exit emits a single
Stage <stage> finished.log carryingjsonPayload.extras.stage_summarywith stage status, duration, errortype, variant, and per-step status, duration, and failure or skip
reason across all 8 UTasks and 3 TrustedTasks.
Also provision a filtered Cloud Logging sink (
stage-summaries) inTerraform that routes only
stage_summaryrecords into a partitionedBigQuery dataset (
stage_summaries).