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 1468912af806f6adf6524a8ad134ef010390a570..7117cbf42133c650fca43bd3bb78e00f5c7cf290 100644
--- a/tools/metrics/histograms/histograms.xml
+++ b/tools/metrics/histograms/histograms.xml
@@ -42181,6 +42181,65 @@ http://cs/file:chrome/histograms.xml - but prefer this file for new entries.
   <summary>Number of retries until the final response was recorded.</summary>
 </histogram>
 
+<histogram name="SiteEngagementService.EngagementScore">
+  <owner>calamity@chromium.org</owner>
+  <owner>dominickn@chromium.org</owner>
+  <summary>
+    Distribution of the engagement scores accumulated by a user, recorded once
+    per non-incognito startup.

[Ilya Sherman, 2015/10/01 07:08:17]

What is an Incognito startup?  Does "startup" mean something other than browser
process launch in this context?

[dominickn, 2015/10/01 08:19:44]

I have clarified this as "once per startup per non-incognito profile launch".

+  </summary>
+</histogram>
+
+<histogram name="SiteEngagementService.EngagementType"
+    enum="SiteEngagementServiceEngagementType">
+  <owner>calamity@chromium.org</owner>
+  <owner>dominickn@chromium.org</owner>
+  <summary>
+    The type of engagement (navigation, user input, etc.) which led to an
+    accumulation in site engagement.
+  </summary>
+</histogram>
+
+<histogram name="SiteEngagementService.OriginsEngaged">
+  <owner>calamity@chromium.org</owner>
+  <owner>dominickn@chromium.org</owner>
+  <summary>
+    The total number of origins with a non-zero site engagement score for this
+    profile, recorded once per non-incognito startup.
+  </summary>
+</histogram>
+
+<histogram name="SiteEngagementService.OriginsWithMaxDailyEngagement">
+  <owner>calamity@chromium.org</owner>
+  <owner>dominickn@chromium.org</owner>
+  <summary>
+    The number of origins which have reached the daily site engagement point
+    cap, recorded each time an origin reaches the cap. Thus, each bin N contains
+    the number of clients where at least N origins have reached the maximum
+    daily site engagement point cap.

[Ilya Sherman, 2015/10/01 07:08:17]

When does N reset -- upon browser relaunch?

And, is zero never recorded for this histogram?

[dominickn, 2015/10/01 08:19:44]

Upon discussion, we have redesigned this histogram so that it and several others
are recorded at browser startup per non-incognito profile, and then every hour
hence. This should address the zero issue, though there is still some skew
against users who do not browse for long period of time.

+  </summary>
+</histogram>
+
+<histogram name="SiteEngagementService.OriginsWithMaxEngagement">
+  <owner>calamity@chromium.org</owner>
+  <owner>dominickn@chromium.org</owner>
+  <summary>
+    The number of origins which have reached the absolute site engagement point
+    cap, recorded each time an origin reaches the cap. Thus, each bin N contains
+    the number of clients where at least N origins have reached the maximum
+    absolute site engagement point cap.
+  </summary>
+</histogram>
+
+<histogram name="SiteEngagementService.TotalEngagement">
+  <owner>calamity@chromium.org</owner>
+  <owner>dominickn@chromium.org</owner>
+  <summary>
+    The total site engagement accumulated by this profile, recorded once per
+    non-incognito startup.
+  </summary>
+</histogram>
+
 <histogram name="SiteIsolation.AllResponses">
   <owner>creis@chromium.org</owner>
   <summary>
@@ -70520,6 +70579,12 @@ To add a new entry, add it with any value and run test to compute valid value.
   <int value="3" label="Fresh index with cache updated since backend start"/>
 </enum>
 
+<enum name="SiteEngagementServiceEngagementType" type="int">
+  <int value="0" label="Navigation"/>
+  <int value="1" label="Keypress"/>
+  <int value="2" label="Mouse"/>
+</enum>
+
 <enum name="SiteIsolationMimeType" type="int">
   <int value="0" label="HTML"/>
   <int value="1" label="XML"/>