Chromium Code Reviews| Index: tools/metrics/rappor/rappor.xml |
| diff --git a/tools/metrics/rappor/rappor.xml b/tools/metrics/rappor/rappor.xml |
| index aa0111e895fabfe229106aea8be50f5ce5b59ae3..72e8ff53dd278e486c0a8c816532d3fe7eb87080 100644 |
| --- a/tools/metrics/rappor/rappor.xml |
| +++ b/tools/metrics/rappor/rappor.xml |
| @@ -849,6 +849,79 @@ 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 rappor identifier of a Chrome task. In most cases this is the hostname |
|
ncarter (slow)
2015/11/10 23:29:57
hostname? or origin?
afakhry
2015/11/12 00:21:28
Origin as you suggested is better.
|
| + of the task's URL. |
| + </summary> |
| + </string-field> |
| + <flags-field name="priority"> |
| + <flag>Bit 0: FOREGROUND</flag> |
| + <flag>Bit 1: BACKGROUND</flag> |
|
ncarter (slow)
2015/11/10 23:29:57
Why is this two bits? Seems like it could be one.
afakhry
2015/11/12 00:21:28
I'm honestly not sure about this one, and I'd leav
|
| + <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_0_CORES</flag> |
| + <flag>Bit 1: RANGE_CORES_1_TO_2_CORES</flag> |
| + <flag>Bit 2: RANGE_CORES_2_TO_4_CORES</flag> |
| + <flag>Bit 3: RANGE_CORES_4_TO_8_CORES</flag> |
| + <flag>Bit 4: RANGE_CORES_8_TO_16_CORES</flag> |
| + <flag>Bit 5: 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 rappor identifier of a Chrome task. In most cases this is the hostname |
| + of the task's URL. |
| + </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. |
| + </summary> |
| + </flags-field> |
| +</rappor-metric> |
| + |
| <rappor-metric name="Search.DefaultSearchProvider" type="ETLD_PLUS_ONE"> |
| <owner>holte@chromium.org</owner> |
| <summary> |