New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 810499 link

Starred by 1 user
Status: Assigned
Owner:
vakh@chromium.org
Cc:
csharrison@chromium.org
skare@chromium.org
isherman@chromium.org
vakh@chromium.org
asvitk...@chromium.org
█ rkaplow@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug
Team-Security-UX



Sign in to add a comment

Reduce or refactor the interstitial.* UMA metric names

Project Member Reported by nparker@chromium.org, Feb 8 2018 
I went to look at UMA metrics for social_engineering interstitials, and when I fetched "interstitial.social_engineering*" I got the following 60 metrics, most of which didn't have any data. We should cull or refactor this list to make it more useful.


interstitial.social_engineering_ads.decision
interstitial.social_engineering_ads.decision.from_client_side_detection
interstitial.social_engineering_ads.decision.from_data_saver
interstitial.social_engineering_ads.decision.from_device
interstitial.social_engineering_ads.decision.from_device_v4
interstitial.social_engineering_ads.decision.repeat_visit
interstitial.social_engineering_ads.decision.repeat_visit.from_client_side_detection
interstitial.social_engineering_ads.decision.repeat_visit.from_data_saver
interstitial.social_engineering_ads.decision.repeat_visit.from_device
interstitial.social_engineering_ads.decision.repeat_visit.from_device_v4
interstitial.social_engineering_ads.interaction
interstitial.social_engineering_ads.interaction.from_client_side_detection
interstitial.social_engineering_ads.interaction.from_data_saver
interstitial.social_engineering_ads.interaction.from_device
interstitial.social_engineering_ads.interaction.from_device_v4
interstitial.social_engineering_ads_subresource.decision
interstitial.social_engineering_ads_subresource.decision.from_client_side_detection
interstitial.social_engineering_ads_subresource.decision.from_data_saver
interstitial.social_engineering_ads_subresource.decision.from_device
interstitial.social_engineering_ads_subresource.decision.from_device_v4
interstitial.social_engineering_ads_subresource.decision.repeat_visit
interstitial.social_engineering_ads_subresource.decision.repeat_visit.from_client_side_detection
interstitial.social_engineering_ads_subresource.decision.repeat_visit.from_data_saver
interstitial.social_engineering_ads_subresource.decision.repeat_visit.from_device
interstitial.social_engineering_ads_subresource.decision.repeat_visit.from_device_v4
interstitial.social_engineering_ads_subresource.interaction
interstitial.social_engineering_ads_subresource.interaction.from_client_side_detection
interstitial.social_engineering_ads_subresource.interaction.from_data_saver
interstitial.social_engineering_ads_subresource.interaction.from_device
interstitial.social_engineering_ads_subresource.interaction.from_device_v4
interstitial.social_engineering_landing.decision
interstitial.social_engineering_landing.decision.from_client_side_detection
interstitial.social_engineering_landing.decision.from_data_saver
interstitial.social_engineering_landing.decision.from_device
interstitial.social_engineering_landing.decision.from_device_v4
interstitial.social_engineering_landing.decision.repeat_visit
interstitial.social_engineering_landing.decision.repeat_visit.from_client_side_detection
interstitial.social_engineering_landing.decision.repeat_visit.from_data_saver
interstitial.social_engineering_landing.decision.repeat_visit.from_device
interstitial.social_engineering_landing.decision.repeat_visit.from_device_v4
interstitial.social_engineering_landing.interaction
interstitial.social_engineering_landing.interaction.from_client_side_detection
interstitial.social_engineering_landing.interaction.from_data_saver
interstitial.social_engineering_landing.interaction.from_device
interstitial.social_engineering_landing.interaction.from_device_v4
interstitial.social_engineering_landing_subresource.decision
interstitial.social_engineering_landing_subresource.decision.from_client_side_detection
interstitial.social_engineering_landing_subresource.decision.from_data_saver
interstitial.social_engineering_landing_subresource.decision.from_device
interstitial.social_engineering_landing_subresource.decision.from_device_v4
interstitial.social_engineering_landing_subresource.decision.repeat_visit
interstitial.social_engineering_landing_subresource.decision.repeat_visit.from_client_side_detection
interstitial.social_engineering_landing_subresource.decision.repeat_visit.from_data_saver
interstitial.social_engineering_landing_subresource.decision.repeat_visit.from_device
interstitial.social_engineering_landing_subresource.decision.repeat_visit.from_device_v4
interstitial.social_engineering_landing_subresource.interaction
interstitial.social_engineering_landing_subresource.interaction.from_client_side_detection
interstitial.social_engineering_landing_subresource.interaction.from_data_saver
interstitial.social_engineering_landing_subresource.interaction.from_device
interstitial.social_engineering_landing_subresource.interaction.from_device_v4

Comment 1 by vakh@chromium.org, Feb 9 2018

Components: Internals>Metrics>UMA
Owner: vakh@chromium.org
Status: Assigned (was: Untriaged)
UMA team -- we have a lot of histograms here that got added because we used suffixes but the suffixes are not really useful for all the cases.

Is there a way to filter out some histograms that are generated as a cross-product of 'histogram_suffixes' and 'affected-histogram' ?

Comment 2 by asvitk...@chromium.org, Feb 9 2018 

You could split the suffixes sections into multiple ones - e.g. have some suffixes only apply to one set of histograms and others to another. But I don't know the details of the specific thing you want to do here, so let me know if the above doesn't work for you.

Comment 3 by nparker@chromium.org, Feb 16 2018

Labels: SafeBrowsing-Triaged
►

Sign in to add a comment