Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Add UKM/UMA for additional bids and negative interest groups.
This adds several new metrics: - ConfigPromisesResolved Latency shows the time between the start of the auction and the time at which the config promises are resolved. - ConfigPromisesResolved CriticalPath shows the time between the start of the BiddingAndScoring phase (after interest groups have been loaded) and the time at which the config promises are resolved, effectively the time at which additional bids would have been delayed waiting for the config promises. - AdditionalBidDecodeLatency metric show the latency for time spent decoding additional bids where that decoding was successful. - NumAdditionalBids* show the frequency of various both error and non-error outcomes of additional bids. - NumNegativeInterestGroups counts the negative interest groups associated with an auction. (For a multi-seller auction, this is the cumulative count of negative interest groups across all component auctions.) - NumNegativeInterestGroupsIgnoredDueTo InvalidSignature or JoiningOriginMismatch counts the number of negative interest groups negatively targeted on an additional bid that were ignored because of some validation failure, as detaield in the "failed open" scenarios described in the explainer. - NumAuctionsWithConfigPromises is the number of auctions in this auction (so, at most 1 in a single-seller auction, at most the number of component auctions plus one for the top-level auction in a multi-seller auction) that had config promises that were resolved. UMA metrics appear for most of these metrics as well. - Ads.InterestGroup.Auction.ConfigPromisesLatency - Ads.InterestGroup.Auction.ConfigPromisesCriticalPathLatency - Ads.InterestGroup.Auction.AdditionalBid.DecodeLatency - Ads.InterestGroup.Auction.AdditionalBid.Result - Ads.InterestGroup.Auction.NumNegativeInterestGroups We don't include UMA for the NumNegativeInterestGroupsIgnoredDueTo UKM because these would make the most sense relative to the number of negative targeting interest groups considered, so that we'd ideally record the frequency of all negative targeting results - not present, present, ignored due to invalid signature, or ignored due to invalid joining origin - but doing so would be slightly misleading, since ShouldDropDueToNegativeTargeting skips all other negative interest groups once one is found, which would bias that metric towards present. Change-Id: Ifa0e61e18d39cf1ba2dcd689b1d0ebba9b049b26 Bug: 1464874 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4943170 Reviewed-by: Maks Orlovich <morlovich@chromium.org> Commit-Queue: Orr Bernstein <orrb@google.com> Cr-Commit-Position: refs/heads/main@{#1216120}
- Loading branch information