Include the session id in feedback logs.

remoting/webapp/base/js/client_session.js

 // 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.
 
 /**
  * @fileoverview
  * Class handling creation and teardown of a remoting client session.
  *
  * The ClientSession class controls lifetime of the client plugin
  * object and provides the plugin with the functionality it needs to
@@ skipping 311 matching lines @@
 };
 
 /**
  * @return {!remoting.Error} The current error code.
  */
 remoting.ClientSession.prototype.getError = function() {
   return this.error_;
 };
 
 /**
+ * @return {string} The current log session id (distinct from the jingle session
+*      id). This is random GUID, refreshed every 24hrs.
+ */
+ remoting.ClientSession.prototype.getLogSessionId = function() {
+  return this.logToServer_.getSessionId();
+};
+
+/**
  * Called when the client receives its first frame.
  *
  * @return {void} Nothing.
  */
 remoting.ClientSession.prototype.onFirstFrameReceived = function() {
   this.hasReceivedFrame_ = true;
 };
 
 /**
  * @return {boolean} Whether the client has received a video buffer.
@@ skipping 255 matching lines @@
  * Enable or disable logging of connection errors due to a host being offline.
  * For example, if attempting a connection using a cached JID, host-offline
  * errors should not be logged because the JID will be refreshed and the
  * connection retried.
  *
  * @param {boolean} enable True to log host-offline errors; false to suppress.
  */
 remoting.ClientSession.prototype.logHostOfflineErrors = function(enable) {
   this.logHostOfflineErrors_ = enable;
 };
-