Reporting top cpu and memory consumers via rappor on chromeos

tools/metrics/rappor/rappor.xml

Index: tools/metrics/rappor/rappor.xml
diff --git a/tools/metrics/rappor/rappor.xml b/tools/metrics/rappor/rappor.xml
index 19e18be557749cd8fa47c8707e6d7ad9c2e17930..ae4cceef50d21336604187927845d4f3bb81677d 100644
--- a/tools/metrics/rappor/rappor.xml
+++ b/tools/metrics/rappor/rappor.xml
@@ -931,6 +931,80 @@ components/rappor/rappor_service.cc.
   </summary>
 </rappor-metric>
 
+<rappor-metric name="ResourceReporter.Cpu" type="UMA_RAPPOR_TYPE">
+  <owner>afakhry@chromium.org</owner>
+  <summary>
+    A Chrome task, its process priority, and its CPU usage range.
+  </summary>
+  <string-field name="task">
+    <summary>
+      The canonicalized name of a Chrome task. In most cases this is the origin
+      URL of the task's WebContents.
+    </summary>
+  </string-field>
+  <flags-field name="priority">
+    <flag>Bit 0: FOREGROUND</flag>
+    <flag>Bit 1: BACKGROUND</flag>
+    <summary>
+      Bitfield for the task's process priority (whether it's foregrounded or
+      backgrounded).
+    </summary>
+  </flags-field>
+  <flags-field name="num_cores_range">
+    <flag>Bit 0: RANGE_CORES_NA</flag>
+    <flag>Bit 1: RANGE_CORES_1_CORE</flag>
+    <flag>Bit 2: RANGE_CORES_2_CORES</flag>
+    <flag>Bit 3: RANGE_CORES_3_TO_4_CORES</flag>
+    <flag>Bit 4: RANGE_CORES_5_TO_8_CORES</flag>
+    <flag>Bit 5: RANGE_CORES_9_TO_16_CORES</flag>
+    <flag>Bit 6: RANGE_CORES_ABOVE_16_CORES</flag>
+    <summary>
+      Bitfield for the current system's number or cores range.
+    </summary>
+  </flags-field>
+  <flags-field name="usage_range">
+    <flag>Bit 0: RANGE_0_TO_10_PERCENT</flag>
+    <flag>Bit 1: RANGE_10_TO_30_PERCENT</flag>
+    <flag>Bit 2: RANGE_30_TO_60_PERCENT</flag>
+    <flag>Bit 3: RANGE_ABOVE_60_PERCENT</flag>
+    <summary>
+      Bitfield for the tasks CPU usage range.
+    </summary>
+  </flags-field>
+</rappor-metric>
+
+<rappor-metric name="ResourceReporter.Memory" type="UMA_RAPPOR_TYPE">
+  <owner>afakhry@chromium.org</owner>
+  <summary>
+    A Chrome task, and its memory usage range.
+  </summary>
+  <string-field name="task">
+    <summary>
+      The canonicalized name of a Chrome task. In most cases this is the origin
+      URL of the task's WebContents.
+    </summary>
+  </string-field>
+  <flags-field name="priority">
+    <flag>Bit 0: FOREGROUND</flag>
+    <flag>Bit 1: BACKGROUND</flag>
+    <summary>
+      Bitfield for the task's process priority (whether it's foregrounded or
+      backgrounded).
+    </summary>
+  </flags-field>
+  <flags-field name="usage_range">
+    <flag>Bit 0: RANGE_0_TO_200_MB</flag>
+    <flag>Bit 1: RANGE_200_TO_400_MB</flag>
+    <flag>Bit 2: RANGE_400_TO_600_MB</flag>
+    <flag>Bit 3: RANGE_600_TO_800_MB</flag>
+    <flag>Bit 4: RANGE_800_TO_1_GB</flag>
+    <flag>Bit 5: RANGE_ABOVE_1_GB</flag>
+    <summary>
+      Bitfield for the tasks CPU usage range.

[Steven Holte, 2015/11/19 22:05:32]

Fix this summary.

[afakhry, 2015/11/21 01:32:58]

Done.

+    </summary>
+  </flags-field>
+</rappor-metric>
+
 <rappor-metric name="Search.DefaultSearchProvider" type="ETLD_PLUS_ONE">
   <owner>holte@chromium.org</owner>
   <summary>