Include time elapsed since start of a remoting session in each log entry.

remoting/webapp/crd/js/desktop_viewport.js

Index: remoting/webapp/crd/js/desktop_viewport.js
diff --git a/remoting/webapp/crd/js/desktop_viewport.js b/remoting/webapp/crd/js/desktop_viewport.js
index 1c9082d16fddaf5e965a901af7be899b9e79bca1..4ccc759d197ab28a00c3533ac30ce83131c0e8de 100644
--- a/remoting/webapp/crd/js/desktop_viewport.js
+++ b/remoting/webapp/crd/js/desktop_viewport.js
@@ -341,6 +341,9 @@ remoting.DesktopViewport.prototype.updateDimensions_ = function() {
   // When we receive the first plugin dimensions from the host, we know that
   // remote host has started.
   remoting.app.onVideoStreamingStarted();
+
+  remoting.clientSession.logToServer.logTotalTimeForInitialConnection();

[Jamie, 2015/02/25 21:12:35]

I would prefer that we don't introduce a dependency on remoting.clientSession in
this class. Doing this logging in onVideoStreamingStarted would seem more
appropriate. Kelvin can probably chime in here as to whether or not that's a
good idea.

In any case, you shouldn't call this multiple times, which will happen with this
layout, since I think updateDimensions is called whenever the remote desktop
size changes. An alternative would be to hook the connected event directly;
you'd lose information as to whether or not the video stream works, but that
feels orthogonal to the time taken to connect.

[anandc, 2015/02/26 20:21:49]

The user perceives a connection has been completed only when video-streaming
begins. As discussed offline, I'll create a new session-state for that, in a
separate CL.

+
 };
 
 /**