tools/metrics/histograms/histograms.xml - Issue 445513002: Add Drive.MetadataDBValidityCheckFailureReason UMA histogram

Keyboard Shortcuts

	File
u :	up to issue
j / k :	jump to file after / before current file
J / K :	jump to next file with a comment after / before current file
	Side-by-side diff
i :	toggle intra-line diffs
e :	expand all comments
c :	collapse all comments
s :	toggle showing all comments
n / p :	next / previous diff chunk or comment
N / P :	next / previous comment
<Up> / <Down> :	next / previous line

	Issue
u :	up to list of issues
j / k :	jump to patch after / before current patch
o / <Enter> :	open current patch in side-by-side view
i :	open current patch in unified diff view

	Issue List
j / k :	jump to issue after / before current issue
o / <Enter> :	open current issue

Unified Diff: tools/metrics/histograms/histograms.xml

Side-by-side diff isn't available for this file because of its large size.

Issue 445513002: Add Drive.MetadataDBValidityCheckFailureReason UMA histogram (Closed) Base URL: svn://svn.chromium.org/chrome/trunk/src

Patch Set: Introduce a function Created 6 years, 4 months ago

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Jump to:

Index: tools/metrics/histograms/histograms.xml

diff --git a/tools/metrics/histograms/histograms.xml b/tools/metrics/histograms/histograms.xml

index 9ef66e50e646f39727ae34f685e46621f02157e3..3fb40bd3d8a3a4f859a13d2f2655cd4ca304213d 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="DriveMetadataDBValidityCheckFailureReason">

+ <owner>joshwoodward@google.com</owner>

Alexei Svitkine (slow) 2014/08/06 15:55:48 Nit: @chromium.org accounts are generally preferre

hashimoto 2014/08/07 04:32:01 Replaced with chromium.org accounts of appropriate

+ <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>

<owner>joshwoodward@google.com</owner>

@@ -37919,6 +37929,17 @@ Therefore, the affected-histogram name has to have at least one dot in it.

</enum>

+<enum name="DriveMetadataDBValidityCheckFailureReason" type="int">

+ <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>

« no previous file with comments | « chrome/browser/chromeos/drive/resource_metadata_storage.cc ('k') | no next file » | no next file with comments »