[FilesBulkPinning] Add daily DSS availability percentage metric The current metric DSSAvailabilityPercentage only gets emitted once a change is detected. This can lead to lots of metrics coming in whilst the initial sync is happening but only one being emitted when syncing is stabilized. It seems this skews the metrics slightly as a user might go from 0% availabile to 100% and stay at 100% from then on, yet we need to make sure the 100% is representative as the final figure, not the increase from 0% to 100%. This new metric will get emitted after a daily period has elapsed and will represent a more point in time capture. So in the previous example the 0% to 100% increase will likely get ignored as this will happen in the first day and the final 100% is more indicative. Fixed: b/300534960 Change-Id: I2997a4ac056117c866ddeb4972abedb620d156c8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4862928 Reviewed-by: François Degros <fdegros@chromium.org> Reviewed-by: Nigel Tao <nigeltao@chromium.org> Commit-Queue: Ben Reich <benreich@chromium.org> Reviewed-by: Hiroki Nakagawa <nhiroki@chromium.org> Cr-Commit-Position: refs/heads/main@{#1200047}
Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
To check out the source code locally, don't use git clone! Instead, follow the instructions on how to get the code.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure .
For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.
If you found a bug, please file it at https://crbug.com/new.