Histogram for UMA log upload connection type.

components/metrics/metrics_service.cc

Index: components/metrics/metrics_service.cc
diff --git a/components/metrics/metrics_service.cc b/components/metrics/metrics_service.cc
index f86f33ab8b511b4d90afd011da3705426cfe4ba4..1e32073b515c0e5180c669c62ee5a11e817ea52e 100644
--- a/components/metrics/metrics_service.cc
+++ b/components/metrics/metrics_service.cc
@@ -997,7 +997,7 @@ void MetricsService::OnLogUploadComplete(int response_code) {
   scheduler_->UploadFinished(server_is_healthy, log_manager_.has_unsent_logs());
 
   if (server_is_healthy)
-    client_->OnLogUploadComplete();
+    client_->OnLogUploadComplete(upload_succeeded);

[Ilya Sherman, 2015/03/24 21:55:44]

I think we might be able to significantly reduce the size of this CL by asking
the log_uploader_ to log the network metrics, rather than asking the client to
do so.  If we don't care about the Error 400 check above, we could even just
directly log the metric in NetMetricsLogUploader::OnURLFetchComplete().  WDYT?

[gayane -on leave until 09-2017, 2015/03/25 21:02:33]

I like this. Done.

 }
 
 void MetricsService::IncrementPrefValue(const char* path) {