Index: tools/metrics/histograms/histograms.xml |
diff --git a/tools/metrics/histograms/histograms.xml b/tools/metrics/histograms/histograms.xml |
index 48c4b5647bffe386679dcc80f81e46d79291c622..0d449c343fd1651a4a74c35152a33eace99e4c0b 100644 |
--- a/tools/metrics/histograms/histograms.xml |
+++ b/tools/metrics/histograms/histograms.xml |
@@ -5289,6 +5289,16 @@ Therefore, the affected-histogram name has to have at least one dot in it. |
</summary> |
</histogram> |
+<histogram name="Drive.MetadataDBValidityCheckFailureReason" |
+ enum="DriveMetadataDBVlidityCheckFailureReason"> |
kinaba
2014/08/05 06:00:14
CHECK_VALIDITY_FAILURE_MAX_VALUE
hashimoto
2014/08/05 06:08:09
Fixed typo.
kinaba
2014/08/05 06:11:57
Eh, sorry for my garbage review comment (caused by
|
+ <owner>joshwoodward@google.com</owner> |
+ <summary> |
+ Reason of drive resource metadata database validity check failure. Recorded |
+ when the validity check fails during Drive metadata initialization triggered |
+ by profile initialization. |
+ </summary> |
+</histogram> |
+ |
<histogram name="Drive.MetadataDBVersionBeforeUpgradeCheck"> |
<owner>joshwoodward@google.com</owner> |
<summary> |
@@ -37750,6 +37760,17 @@ Therefore, the affected-histogram name has to have at least one dot in it. |
<int value="9" label="Cannot open existing DB. Created new DB."/> |
</enum> |
+<enum name="DriveMetadataDBVlidityCheckFailureReason" type="int"> |
kinaba
2014/08/05 06:00:14
ditto
hashimoto
2014/08/05 06:08:09
Fixed typo.
|
+ <int value="0" label="Invalid header"/> |
+ <int value="1" label="Broken ID entry"/> |
+ <int value="2" label="Broken entry"/> |
+ <int value="3" label="Invalid local ID"/> |
+ <int value="4" label="Invalid parent ID"/> |
+ <int value="5" label="Broken child map"/> |
+ <int value="6" label="Child entry count mismatch"/> |
+ <int value="7" label="Iterator error"/> |
+</enum> |
+ |
<enum name="EAPInnerProtocol" type="int"> |
<int value="0" label="UNKNOWN"/> |
<int value="1" label="NONE"/> |