RAPPOR implementation

tools/metrics/histograms/histograms.xml

Index: tools/metrics/histograms/histograms.xml
diff --git a/tools/metrics/histograms/histograms.xml b/tools/metrics/histograms/histograms.xml
index a811a2c4d65de30c4d9f46282808ba20edc7743e..b2e53631d59c7048eb07f0ec36c9bfc48a1f81e9 100644
--- a/tools/metrics/histograms/histograms.xml
+++ b/tools/metrics/histograms/histograms.xml
@@ -15984,6 +15984,19 @@ other types of suffix sets.
   </summary>
 </histogram>
 
+<histogram name="Rappor.DiscardReason" enum="RapporDiscardReason">
+  <summary>
+    For each Rappor log that is discarded, the reason that it was discarded.
+  </summary>
+</histogram>
+
+<histogram name="Rappor.UploadResponseCode">

[Ilya Sherman, 2014/02/12 23:25:59]

Hmm, do we not have an enum in this for response codes?  That's a little
surprising.

[Steven Holte, 2014/02/13 05:11:12]

It looks like we actually do, although of the only thing that uses it is
Wallet.ResponseCode.  There are a bunch of other histograms that report them,
but just don't use the enum (including Variations.SeedFetchResponseCode)

Modified to use the enum.

+  <summary>
+    For each upload to the Rappor server, log the response received from the
+    server.
+  </summary>
+</histogram>
+
 <histogram name="Renderer.AcceleratedFixedRootBackground"
     enum="AcceleratedFixedRootBackground">
   <summary>
@@ -30525,6 +30538,12 @@ other types of suffix sets.
   <int value="6" label="CANCELLED"/>
 </enum>
 
+<enum name="RapporDiscardReason" type="int">
+  <int value="0" label="Upload Success"/>
+  <int value="1" label="Upload Rejected"/>
+  <int value="2" label="Queue Overflowed"/>
+</enum>
+
 <enum name="RecentTabsAction" type="int">
   <int value="0" label="Local Session Tab"/>
   <int value="1" label="Other Device Tab"/>