Adding UMA stats for requestFileSystem error analysis.

Adding UMA stats for requestFileSystem error analysis.

BUG=
TEST=


Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=114448

[tzik, 2011-12-12 13:50:15]

Hi, kinuko-san.
I'd like to add UMA stats to investigate errors on requestFileSystem.
Could you review this patch?

[kinuko, 2011-12-14 04:22:39]

On 2011/12/12 13:50:15, tzik wrote:
> Hi, kinuko-san.
> I'd like to add UMA stats to investigate errors on requestFileSystem.
> Could you review this patch?

LGTM thanks!

[commit-bot: I haz the power, 2011-12-14 05:21:13]

No LGTM from valid reviewers yet.

[commit-bot: I haz the power, 2011-12-14 13:11:30]

No LGTM from valid reviewers yet.

[commit-bot: I haz the power, 2011-12-14 14:43:20]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/tzik@chromium.org/8918005/1

[commit-bot: I haz the power, 2011-12-14 17:36:33]

Change committed as 114448

[kinuko, 2011-12-15 04:34:05]

http://codereview.chromium.org/8918005/diff/1/webkit/fileapi/sandbox_mount_po...
File webkit/fileapi/sandbox_mount_point_provider.cc (right):

http://codereview.chromium.org/8918005/diff/1/webkit/fileapi/sandbox_mount_po...
webkit/fileapi/sandbox_mount_point_provider.cc:359: kFileSystemErrorMax);
Tzik-san, I know this patch has been already landed but could we add slightly
more detailed metrics for this case?
GetDirectoryForOriginAndType could fail for various reasons and I suspect this
one would be the primary hot error spot.
(For example if it's failing due to CURRENT file corruption in origin db like
the one reported in 103018 the error must come from GetDirectoryForOrigin() =>
OriginDatabase::GetPathForOrigin() => OriginDatabase::Init().