PIR: Add more granular buckets to PIR wide event#8899
Merged
Conversation
Contributor
|
Privacy Review task: https://app.asana.com/0/69071770703008/1215775121446043 |
karlenDimla
approved these changes
Jun 17, 2026
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
2 participants
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.
Task/Issue URL: https://app.asana.com/1/137249556945/project/488551667048375/task/1215718565665536?focus=true
Tech Design URL (if applicable): N/A
Description
Adds 2 days, 5 days and 10 days buckets to the initial scan complete wide event.
Steps to test this PR
QA-optional
UI changes
No UI changes
Note
Low Risk
Analytics-only bucket and enum updates; no changes to scan scheduling, completion logic, or user-facing behavior.
Overview
Adds finer wall-clock duration buckets for the
wide_pir-time-to-first-scan-completewide event so time-to-first-full-scan can be reported with more granularity in the multi-day range.Runtime:
COMPLETION_INTERVAL_BUCKETSinPirInitialScanCompletionWideEventnow includes 2 days, 5 days, and 10 days (alongside existing 1/3/7/14 day boundaries).Schema: The
total_duration_ms_bucketedenum inpersonal_information_removal.json5is updated with the matching millisecond lower bounds (172800000,432000000,864000000) so emitted pixels stay valid.Reviewed by Cursor Bugbot for commit cbddcfd. Bugbot is set up for automated code reviews on this repo. Configure here.