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 4f4cffc4af96538178acf3a266b68b549ab7c82b..fe3658a5074df0257cadde61c9366b7e80e04714 100644
--- a/tools/metrics/histograms/histograms.xml
+++ b/tools/metrics/histograms/histograms.xml
@@ -38237,6 +38237,49 @@ http://cs/file:chrome/histograms.xml - but prefer this file for new entries.
   </summary>
 </histogram>
 
+<histogram name="Net.Reporting.HeaderEndpointOutcome"
+    enum="NetReportingHeaderEndpointOutcome">
+  <owner>juliatuttle@chromium.org</owner>
+  <summary>
+    The outcome of Reporting trying to process a single endpoint in a Report-To
+    header once the header itself has been parsed.
+  </summary>
+</histogram>
+
+<histogram name="Net.Reporting.HeaderOutcome" enum="NetReportingHeaderOutcome">
+  <owner>juliatuttle@chromium.org</owner>
+  <summary>
+    The outcome of Reporting trying to process a Report-To header. Once it is
+    parsed, Net.Reporting.HeaderEndpointOutcome records the outcome of the
+    endpoints within it.
+  </summary>
+</histogram>
+
+<histogram name="Net.Reporting.ReportDeliveredAttempts" units="attempts">
+  <owner>juliatuttle@chromium.org</owner>
+  <summary>
+    When Reporting successfully delivers a report, the number of unsuccessful
+    delivery attempts that preceded the successful one.
+  </summary>
+</histogram>
+
+<histogram name="Net.Reporting.ReportDeliveredLatency" units="ms">
+  <owner>juliatuttle@chromium.org</owner>
+  <summary>
+    When Reporting successfully delivers a report, the delivery latency. Starts

[rkaplow, 2017/05/24 17:29:56]

sentance is a bit awkward

+    when the report is queued and finishes when the delivery attempt returns
+    successfully.
+  </summary>
+</histogram>
+
+<histogram name="Net.Reporting.ReportOutcome" enum="NetReportingReportOutcome">
+  <owner>juliatuttle@chromium.org</owner>
+  <summary>
+    The outcome of Reporting trying to deliver a report, recorded when the
+    report is finally erased from memory.
+  </summary>
+</histogram>
+
 <histogram name="Net.RequestTime">
   <obsolete>
     Replaced by Net.RequestTime2 due to bug in original implementation.
@@ -46403,9 +46446,9 @@ http://cs/file:chrome/histograms.xml - but prefer this file for new entries.
 
 <histogram name="Omnibox.ProgressBarBreakPointUpdateCount"
     units="break point updates">
-  <obselete>
-    Obselete 05/16/2017. Data is unused (crbug.com/719801).
-  </obselete>
+  <obsolete>
+    Obsolete 05/16/2017. Data is unused (crbug.com/719801).
+  </obsolete>
   <owner>kkimlabs@chromium.org</owner>
   <summary>
     The number of progress bar break point updates from page load started to
@@ -46414,9 +46457,9 @@ http://cs/file:chrome/histograms.xml - but prefer this file for new entries.
 </histogram>
 
 <histogram name="Omnibox.ProgressBarUpdateCount" units="frame updates">
-  <obselete>
-    Obselete 05/16/2017. Data is unused (crbug.com/719801).
-  </obselete>
+  <obsolete>
+    Obsolete 05/16/2017. Data is unused (crbug.com/719801).
+  </obsolete>
   <owner>kkimlabs@chromium.org</owner>
   <summary>
     The number of progress bar frame updates from page load started to page load
@@ -71995,16 +72038,12 @@ http://cs/file:chrome/histograms.xml - but prefer this file for new entries.
 
 <histogram base="true" name="Storage.BytesRead" units="bytes">
   <owner>michaeln@chromium.org</owner>
-  <summary>
-    The number of bytes read. Recorded on each read.
-  </summary>
+  <summary>The number of bytes read. Recorded on each read.</summary>
 </histogram>
 
 <histogram base="true" name="Storage.BytesWritten" units="bytes">
   <owner>michaeln@chromium.org</owner>
-  <summary>
-    The number of bytes written. Recorded on each write.
-  </summary>
+  <summary>The number of bytes written. Recorded on each write.</summary>
 </histogram>
 
 <histogram name="Storage.ImportantSites.CBDChosenReason"
@@ -82079,8 +82118,8 @@ http://cs/file:chrome/histograms.xml - but prefer this file for new entries.
   <owner>philipel@chromium.org</owner>
   <summary>
     A successful probing attempt for a given bitrate, triggered by an update to
-    the max configured bitrate. NOTE! This is not the resulting bitrate from
-    a probing attempt, see WebRTC.BWE.MidCallProbing.ProbedKbps.
+    the max configured bitrate. NOTE! This is not the resulting bitrate from a
+    probing attempt, see WebRTC.BWE.MidCallProbing.ProbedKbps.
   </summary>
 </histogram>