Index: tools/metrics/histograms/histograms.xml |
diff --git a/tools/metrics/histograms/histograms.xml b/tools/metrics/histograms/histograms.xml |
index 087c348496c6904ff14ca1912b662720391978e3..025ba4662279967f60aa89884219c452b1dc17a3 100644 |
--- a/tools/metrics/histograms/histograms.xml |
+++ b/tools/metrics/histograms/histograms.xml |
@@ -31639,6 +31639,16 @@ Therefore, the affected-histogram name has to have at least one dot in it. |
<summary>Whether the scroll is executed on main thread.</summary> |
</histogram> |
+<histogram name="UMA.ClientIdBackupRecoveredWithAge" units="hours"> |
+ <owner>gab@chromium.org</owner> |
+ <summary> |
+ Recorded when we are somehow missing the client ID stored in Local State yet |
+ are able to recover it from a backup location along with the backed up |
+ installation date. This report carries the age in hours of the recovered |
+ client id. |
Ilya Sherman
2014/07/08 01:10:22
I think UMA_HISTOGRAM_CUSTOM_TIMES still records t
|
+ </summary> |
+</histogram> |
+ |
<histogram name="UMA.ClientIdMigrated" enum="BooleanMigrated"> |
<owner>asvitkine@chromium.org</owner> |
<summary> |