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 a0de6b30290217e01e9f0c9df65641d0e1085504..daf2299a5fd325531a5d94ed86b90f68ac1fc1cc 100644
--- a/tools/metrics/histograms/histograms.xml
+++ b/tools/metrics/histograms/histograms.xml
@@ -25461,6 +25461,11 @@ Therefore, the affected-histogram name has to have at least one dot in it.
   </summary>
 </histogram>
 
+<histogram name="Signin.SignoutProfile" enum="SigninSignoutProfile">
+  <owner>mlerman@chromium.org</owner>
+  <summary>Track how a profile gets signed out.</summary>
+</histogram>
+
 <histogram name="SimpleCache.App.CheckCRCResult" enum="CheckCRCResult">
   <owner>Please list the metric's owners. Add more owner tags as needed.</owner>
   <summary>
@@ -43481,6 +43486,34 @@ Therefore, the affected-histogram name has to have at least one dot in it.
   <int value="13" label="Learn more undo"/>
 </enum>
 
+<enum name="SigninSignoutProfile" type="int">
+  <int value="0" label="Preference changed">
+    The preference or policy controlling if signin is valid has changed.
+  </int>
+  <int value="1" label="Google service pattern changed">
+    The valid username pattern for signing in to the Google service changed.
+  </int>
+  <int value="2" label="Signin preference changed during signin">
+    The preference or policy controlling if signin is valid changed during the
+    signin process.
+  </int>
+  <int value="3" label="User clicked signout">User clicked to signout.</int>
+  <int value="4" label="Signin aborted">
+    The signin process was aborted, but signin had succeeded, so signout. This
+    may be due to a server response, policy definition or user action.
+  </int>
+  <int value="5" label="Android signout">
+    User clicked to signout on android.

[Alexei Svitkine (slow), 2014/06/17 18:13:47]

Is there a reason this needs to be separate from "User clicked signout"?

You can already slice UMA data by platform, so why the need for a separate
entry?

[Mike Lerman, 2014/06/17 18:51:50]

I had been thinking that since it's a different code flow... but it's the same
intent, and we can always separate it out later. Change made.

+  </int>
+  <int value="6" label="Server forced">
+    The sync server caused the profile to be signed out.
+  </int>
+  <int value="7" label="Credentials transfered">
+    The credentials are being transfered to a new profile, so the old one is
+    signed out.
+  </int>
+</enum>
+
 <enum name="SimpleCache.EntryCreatedAndStream2Omitted" type="int">
   <int value="0" label="Stream 2 file was present"/>
   <int value="1" label="Empty stream 2 file was omitted"/>