Report data usage UMA for Chrome services

components/data_use_measurement/core/data_use_user_data.h

Index: components/data_use_measurement/core/data_use_user_data.h
diff --git a/components/data_use_measurement/core/data_use_user_data.h b/components/data_use_measurement/core/data_use_user_data.h
index 80d310e0ade12ae9a8da8e049d71f752603b701c..382a8342d7bf5ebf4b1fd45ab1582b2f629534ec 100644
--- a/components/data_use_measurement/core/data_use_user_data.h
+++ b/components/data_use_measurement/core/data_use_user_data.h
@@ -23,6 +23,22 @@ class DataUseUserData : public base::SupportsUserData::Data {
   enum ServiceType {
     NOT_TAGGED,
     SUGGESTIONS,
+    TRANSLATE,
+    SYNC,
+    OMNIBOX,
+    INVALIDATION,
+    RAPPOR,
+    POLICY,
+    UMA,
+    GOOGLE_APIS,
+    DOMAIN_RELIABILITY,
+    PROFILE_DOWNLOADER,
+    GOOGLE_URL_TRACKER,
+    AUTOFILL,
+    VARIATIONS,
+    DEVICE_MANAGEMENT,

[bartfab (slow), 2015/09/07 14:27:19]

What are the expected semantics of |DEVICE_MANAGEMENT| and |POLICY|? You used
|DEVICE_MANAGEMENT| for the core URL fetchers that talk to the policy server and
|POLICY| for auxiliary fetchers that talk to other services. I find that
strange.

[amohammadkhan, 2015/09/08 13:26:55]

I wanted to have a breakdown between different types of request in this service.
But I think you are right and it is not necessary, so I changed all requests'
tags to |POLICY|.

+    SPELL_CHECKER,
+    GEO_LOCATION,
   };
 
   explicit DataUseUserData(ServiceType service_type);