tools/metrics/histograms/histograms.xml

Index: tools/metrics/histograms/histograms.xml
diff --git a/tools/metrics/histograms/histograms.xml b/tools/metrics/histograms/histograms.xml
index 65d16025996f576bbbcd682f0b53093959a19207..b2633781cff53473556ab24f34921ec730730887 100644
--- a/tools/metrics/histograms/histograms.xml
+++ b/tools/metrics/histograms/histograms.xml
@@ -4743,6 +4743,34 @@ Therefore, the affected-histogram name has to have at least one dot in it.
   </summary>
 </histogram>
 
+<histogram name="EasyUnlock.ClickedButton" enum="EasyUnlockButton">
+  <owner>joshwoodward@google.com</owner>
+  <summary>Button clicked in easy unlock app during setup process.</summary>
+</histogram>

[Ilya Sherman, 2014/05/22 15:34:26]

It would be good to contextualize this data by also logging the number of times
that the EasyUnlock app was shown.

[tbarzic, 2014/05/22 17:18:56]

added EasyUnlock.AppLaunched action

+
+<histogram name="EasyUnlock.NotificationEvent"
+    enum="EasyUnlockNotificationEvent">
+  <owner>joshwoodward@google.com</owner>
+  <summary>
+    Tracks events related to notifications used by easy unlock feature. For
+    example a specific easy unlock notification being shown or clicked.
+  </summary>
+</histogram>
+
+<histogram name="EasyUnlock.SetupStateOnClose" enum="EasyUnlockSetupState">
+  <owner>joshwoodward@google.com</owner>
+  <summary>
+    State easy unlock setup was in when the app window was closed by user.
+  </summary>
+</histogram>
+
+<histogram name="EasyUnlock.UnlockEvent" enum="EasyUnlockUnlockEvent">
+  <owner>joshwoodward@google.com</owner>
+  <summary>
+    Screen unlock events detected while easy unlock was enabled.
+  </summary>
+</histogram>
+
 <histogram name="Enterprise.AutoEnrollmentExtraTime" units="milliseconds">
   <owner>joaodasilva@chromium.org</owner>
   <summary>
@@ -32899,6 +32927,36 @@ Therefore, the affected-histogram name has to have at least one dot in it.
   <int value="4" label="TTLS"/>
 </enum>
 
+<enum name="EasyUnlockButton" type="int">
+  <int value="0" label="FIND_DEVICE"/>
+  <int value="1" label="PAIR_DEVICE"/>
+  <int value="2" label="TRY_OUT_EASY_UNLOCK"/>
+  <int value="3" label="ENABLE_EASY_UNLOCK"/>
+  <int value="4" label="DISABLE_EASY_UNLOCK"/>
+</enum>
+
+<enum name="EasyUnlockNotificationEvent" type="int">
+  <int value="0" label="SET_UP_SHOWN"/>
+  <int value="1" label="SET_UP_CLICKED"/>
+  <int value="2" label="TRY_OUT_SHOWN"/>
+  <int value="3" label="TRY_OUT_CLICKED"/>
+</enum>
+
+<enum name="EasyUnlockSetupState" type="int">
+  <int value="0" label="SET_UP"/>
+  <int value="1" label="SCAN_INITIAL"/>
+  <int value="2" label="SCAN_IN_PROGRESS"/>
+  <int value="3" label="SCAN_ERROR"/>
+  <int value="4" label="PAIRING_INITIAL"/>
+  <int value="5" label="PAIRING_IN_PROGRESS"/>
+  <int value="6" label="PAIRING_ERROR"/>
+</enum>

[Ilya Sherman, 2014/05/22 15:34:26]

Is it not possible to have been in a success state?

[tbarzic, 2014/05/22 17:18:56]

Yeah, it is. It's actually the value 0, but I see how the label is confusing..

+
+<enum name="EasyUnlockUnlockEvent" type="int">
+  <int value="0" label="SCREEN_UNLOCKED_TOTAL"/>
+  <int value="1" label="SCREEN_UNLOCKED_USING_EASY_UNLOCK"/>

[Ilya Sherman, 2014/05/22 15:34:26]

nit: You can use human-friendly strings, like "Screen unlocked (total)" and
"Screen unlocked (via EasyUnlock)"

[tbarzic, 2014/05/22 17:18:56]

Done.

+</enum>
+
 <enum name="EnterpriseCheckError" type="int">
   <int value="0" label="Cound not get net join info."/>
   <int value="1" label="Cound not bind to domain controller."/>