Add histogram WebRTC.UserMediaRequest.Events to allow to track getUserMedia failures and hangs.

content/renderer/media/webrtc_uma_histograms.h

 // Copyright (c) 2012 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 #ifndef CONTENT_RENDERER_MEDIA_WEBRTC_UMA_HISTOGRAMS_H_
 #define CONTENT_RENDERER_MEDIA_WEBRTC_UMA_HISTOGRAMS_H_
 
 #include "base/memory/singleton.h"
 #include "base/threading/non_thread_safe.h"
 #include "content/common/content_export.h"
+#include "content/public/common/media_stream_request.h"
 
 namespace content {
 
+// Enum to track UserMediaRequest events. MediaStreamRequestResult events are
+// mapped directly to MediaStreamRequestResult + 10.
+enum UserMediaRequestEvent {
+  USERMEDIAREQUEST_CREATED = 0,

[vrk (LEFT CHROMIUM), 2014/08/04 18:22:17]

I don't think CREATED is a useful histogram value - it will skew the other
percentages, since every CREATED gets counted for every CANCELLED and
NO_RESPONSE value.

I think it'd make more sense to split the values up as follows:
- gUM returned Success
- gUM returned Failure
- gUM cancelled
- gUM called but no response*

*As per other comment, would be better if we could drill down more specifically:
- gUM called, user allowed permission, and no response
- gUM called, user denied permission, and no response
- gUM called, user did not allow/deny permission

[andresp-chromium, 2014/08/04 19:16:23]

This was intended to be an events counter.. in such case it would be acceptable
that events were unrelated and percentage diagrams wouldn't need to make sense
(IMO).

Anyhow when I started following all the code paths with stream generation and so
on it became harder so I am splitting this part into another CL (to prepare
tomorrow) and for now this CL only has stream request result being logged.

On 2014/08/04 18:22:17, Victoria Kirst wrote:

+  USERMEDIAREQUEST_CANCELLED = 1,
+  USERMEDIAREQUEST_NO_RESPONSE = 2,
+  // Unused enum ids so they can be used to track events that don't exist in
+  // MediaStreamRequestResult without destroying existent mappings.
+  USERMEDIAREQUEST_RESULT = 10,

[vrk (LEFT CHROMIUM), 2014/08/04 18:22:17]

ISTM it'd make more sense to have two histograms:

UserMediaRequest.event: histogram of how often gUM returns with success or
failure vs cancel or no response
- UserMediaRequestEvent enum 

UserMediaRequest.result: histogram of results for the gUM calls that do return
either success or failure
- MediaStreamRequestResult enum

So then you wouldn't need to have the USERMEDIAREQUEST_RESULT = 10 stuff.

[andresp-chromium, 2014/08/04 19:16:24]

Totally agree.

On 2014/08/04 18:22:17, Victoria Kirst wrote:

+  NUM_USERMEDIAREQUEST_EVENTS =
+      USERMEDIAREQUEST_RESULT + NUM_MEDIA_REQUEST_RESULTS
+};
+
+void LogUserMediaRequestEvent(UserMediaRequestEvent event);
+void LogUserMediaRequestResult(MediaStreamRequestResult result);
+
 // Helper enum used for histogramming calls to WebRTC APIs from JavaScript.
 enum JavaScriptAPIName {
   WEBKIT_GET_USER_MEDIA,
   WEBKIT_PEER_CONNECTION,
   WEBKIT_DEPRECATED_PEER_CONNECTION,
   WEBKIT_RTC_PEER_CONNECTION,
   WEBKIT_GET_MEDIA_DEVICES,
   INVALID_NAME
 };
 
@@ skipping 50 matching lines @@
 
   int num_streams_;
   bool has_used_api_[INVALID_NAME];
 
   DISALLOW_COPY_AND_ASSIGN(PerSessionWebRTCAPIMetrics);
 };
 
 } //  namespace content
 
 #endif  // CONTENT_RENDERER_MEDIA_WEBRTC_UMA_HISTOGRAMS_H_