The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/7e33a712878360d6439612e36f33e59acb17a94e

commit 7e33a712878360d6439612e36f33e59acb17a94e
Author: xiyuan <xiyuan@chromium.org>
Date: Tue Mar 08 19:26:38 2016

kiosk: Add kiosk launch type UMA

BUG= 592022 

Review URL: https://codereview.chromium.org/1765273002

Cr-Commit-Position: refs/heads/master@{#379883}

[modify] https://crrev.com/7e33a712878360d6439612e36f33e59acb17a94e/chrome/browser/chromeos/login/app_launch_controller.cc
[modify] https://crrev.com/7e33a712878360d6439612e36f33e59acb17a94e/tools/metrics/histograms/histograms.xml

Change is in M51-Dev 8041.0.0 (51.0.2672.0) and later. Will verify today.

what stats should I be looking for in the histograms in order to test and verify this bug

It's a UMA enum metric named Kiosk.LaunchType.

I have ran several Kiosk apps in consumer mode as well as enterprise enrolled and then I searched in the chrome://histograms and could not find any record of Kiosk or Kiosk.LaunchType or launch.type. Unable to verify.
platform and version information :

CHROMEOS_RELEASE_DESCRIPTION=8095.0.0  dev-channel panther test

Not sure the good way to verify it. But chrome://histograms could not be used in this case because it only returns "Stats accumulated from browser startup to previous page load...". This means the Kiosk.LaunchType will not show up after browser is restarted (i.e. exit kiosk sessions and get into a user session).

Maybe we need to figure out a way to look at the raw metrics data.

the machine ran multiple kiosk apps in consumer and enrolled enterprise mode with a reboot in between each kiosk app run, no data has been recorded in UMA stats:

https://uma.googleplex.com/histograms/?endDate=02-02-2014&dayCount=7&fixupData=true&otherVersions=true&showMax=true&filters=platform%2Ceq%2CC%2Cisofficial%2Ceq%2CTrue&implicitFilters=isofficial

https://uma.googleplex.com/histograms/?endDate=03-16-2016&dayCount=28&histograms=Kiosk.LaunchType&fixupData=false&showMax=false&filters=platform%2Ceq%2CC%2Cisofficial%2Ceq%2CTrue&implicitFilters=isofficial

UMA dashboard is not real time and make sure the devices is powered on and be online long enough to ensure the metrics is uploaded.

I will try to figure out a script to ask Chrome to dump histograms while running to make it easier to test.

UMA finally updated and showed a record of the Kiosk.LaunchType on my test device, therefore the bug is verified. And yes we would like to see that script for histograms. Thanks

Test device info:
CHROMEOS_RELEASE_DESCRIPTION=8095.0.0  dev-channel panther test
"serial_number"="E5MSCX027759"

Attached is a script to ask running Chrome instance to dump histogram data out as json. After kiosk is launched, run the script and the output file is /tmp/chrome.histogram.json. Look for "Kiosk.LaunchType" in the file and check out the "buckets" field. Or find some visualize tool for the data.

Deleted: dump_histogram.sh 668 bytes

dump_histogram.sh 668 bytes View Download