Log operator code histogram on new metric log

chrome/browser/metrics/chrome_browser_main_extra_parts_metrics.cc

Index: chrome/browser/metrics/chrome_browser_main_extra_parts_metrics.cc
diff --git a/chrome/browser/metrics/chrome_browser_main_extra_parts_metrics.cc b/chrome/browser/metrics/chrome_browser_main_extra_parts_metrics.cc
index 3fd5bb647c6bbfde4f6ded0d741dea504d93c975..b10ac644231c22b4494a74ce1a077e1ca21a53cb 100644
--- a/chrome/browser/metrics/chrome_browser_main_extra_parts_metrics.cc
+++ b/chrome/browser/metrics/chrome_browser_main_extra_parts_metrics.cc
@@ -17,6 +17,7 @@
 #include "chrome/browser/about_flags.h"
 #include "chrome/browser/browser_process.h"
 #include "chrome/browser/chrome_browser_main.h"
+#include "chrome/browser/chrome_browser_metrics_service_observer.h"
 #include "chrome/browser/pref_service_flags_storage.h"
 #include "chrome/browser/shell_integration.h"
 #include "content/public/browser/browser_thread.h"
@@ -154,6 +155,12 @@ void ChromeBrowserMainExtraPartsMetrics::PostBrowserStart() {
       FROM_HERE,
       base::Bind(&RecordStartupMetricsOnBlockingPool),
       base::TimeDelta::FromSeconds(kStartupMetricsGatheringDelaySeconds));
+
+  // Create the metrics log observer.
+  // We only need this histogram for Android for now.
+#if defined(ANDROID)
+  metrics_service_observer_.reset(new ChromeBrowserMetricsServiceObserver());

[Lei Zhang, 2014/05/08 20:32:15]

If you want this to happen earlier, so it is closer in behavior to the previous
patch set, feel free to add
ChromeBrowserMainExtraPartsMetrics::PreCreateThread().

[bolian, 2014/05/08 22:17:57]

From what I tested this seems fine and it happened before the first metrics log.

+#endif
 }
 
 namespace chrome {