Report user actions for interactions with the Windows Settings app.

tools/metrics/actions/actions.xml

 <!--
 Copyright 2014 The Chromium Authors. All rights reserved.
 Use of this source code is governed by a BSD-style license that can be
 found in the LICENSE file.
 -->
 
 <!--
 This file is a comprehensive list of Chrome user actions along with the owner
 and description for each user action. A user action should be tied to an actual
 action taken by a user. It should be logged immediately after a user takes the
@@ skipping 12610 matching lines @@
 
 <action name="Settings.Searching">
   <owner>dschuyler@chromium.org</owner>
   <description>
     A new search has been started in the chrome://settings (preferences) page. A
     search is considered complete via timeout since there is no concrete way to
     define the end of a search (the search is incremental).
   </description>
 </action>
 
+<action name="SettingsAppMonitor.AppFocused">
+  <owner>grt@chromium.org</owner>
+  <description>The Windows Settings app became focused.</description>
+</action>
+
+<action name="SettingsAppMonitor.ChooserInvoked">
+  <owner>grt@chromium.org</owner>
+  <description>
+    The user opened the Windows Settings app's browser chooser.
+  </description>
+</action>
+
+<action name="SettingsAppMonitor.ChromeBrowserChosen">
+  <owner>grt@chromium.org</owner>
+  <description>
+    The user selected Chrome from the Windows Settings app's browser chooser.
+  </description>
+</action>
+
+<action name="SettingsAppMonitor.Failed">
+  <owner>grt@chromium.org</owner>
+  <description>
+    The Windows Settings app monitor failed to initialize successfully.

[Alexei Svitkine (slow), 2016/05/24 19:33:38]

Since this doesn't correspond to a user action (something triggered by the
user), I suggest using a histogram to track this case and
SettingsAppMonitor.Initialized. It can be a boolean histogram with those two
options.

The other cases seem fine to use actions for.

[grt (UTC plus 2), 2016/05/25 12:52:47]

I had thought Initialized would be good because it gives a concrete start point
(w/ a timestamp) to the interaction regardless of how it was initiated
(chrome://settings, the default browser infobar, or some other thing).
WDYT of making Failed a BooleanHit histogram but leaving Initialized as-is?

[Alexei Svitkine (slow), 2016/05/25 15:51:34]

OK. Maybe mention that in its description.
A BooleanHit histogram is not great - because you get an absolute number that
won't tell you much w/ out other information (e.g. BooleanHit 38929 - is that a
lot or a little?). I would make it a BooleanSuccess with buckets for success and
failed.

[grt (UTC plus 2), 2016/05/26 13:13:48]

Done.

+  </description>
+</action>
+
+<action name="SettingsAppMonitor.Initialized">
+  <owner>grt@chromium.org</owner>
+  <description>
+    The Windows Settings app monitor initialized successfully.
+  </description>
+</action>
+
+<action name="SettingsAppMonitor.OtherBrowserChosen">
+  <owner>grt@chromium.org</owner>
+  <description>
+    The user selected a different browser from the Windows Settings app's
+    browser chooser.
+  </description>
+</action>
+
 <action name="SettingsResetBubble.LearnMore">
   <owner>mad@chromium.org</owner>
   <description>Please enter the description of this user action.</description>
 </action>
 
 <action name="SettingsResetBubble.NoThanks">
   <owner>mad@chromium.org</owner>
   <description>Please enter the description of this user action.</description>
 </action>
 
@@ skipping 1889 matching lines @@
 <action name="webapps.AddShortcut.Manifest">
   <owner>mlamouri@chromium.org</owner>
   <description>
     Shortcut added to the homescreen with a valid Manifest. This action will be
     recorded in addition to AppShortcut, AppShortcutApple and Bookmark actions
     to keep a trend of whether the webapp also add meta tags.
   </description>
 </action>
 
 </actions>