Add UMA histograms for more detailed latency tracking on the CRD host.

remoting/proto/video.proto

Index: remoting/proto/video.proto
diff --git a/remoting/proto/video.proto b/remoting/proto/video.proto
index b2b1258887cdbb3e78596274a70d6dbd1d935572..5c8f3b66bc6bedb53d86c106fb2319359481903d 100644
--- a/remoting/proto/video.proto
+++ b/remoting/proto/video.proto
@@ -71,6 +71,20 @@ message VideoPacket {
 
   // Frame identifier used to match VideoFrame and VideoAck.
   optional int32 frame_id = 13;
+
+  // Time passed from when the last event was received until capturing has

[anandc, 2015/09/25 19:21:45]

"Time between when the" etc., or just remove "passed".

[Sergey Ulanov, 2015/09/25 20:35:26]

Done.

+  // started.
+  optional int64 capture_pending_time_ms = 14;
+
+  // Total overhead time for IPC and threading when capturing frames.
+  optional int64 capture_overhead_time_ms = 15;
+
+  // Time passed between when the frame was captured and when encoder started

[anandc, 2015/09/25 19:21:45]

Remove "passed".

[Sergey Ulanov, 2015/09/25 20:35:26]

Done.

+  // encoding it.
+  optional int64 encode_pending_time_ms = 16;
+
+  // Total latency for the event being blocked until it's sent to the client.

[anandc, 2015/09/25 19:21:45]

"Time for which the event is blocked until it's sent to the client"?

[Sergey Ulanov, 2015/09/25 20:35:26]

Done. It's also frame, not event

+  optional int64 send_pending_time_ms = 17;
 }
 
 // VideoAck acknowledges that the frame in the VideoPacket with the same