Adding bluetooth histograms for NCN.CM histograms

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 5e08392296ed9f521091dc10aeef2b70480646db..e844efc1ef402902213d29aacd077708f4ffaa6b 100644
--- a/tools/metrics/histograms/histograms.xml
+++ b/tools/metrics/histograms/histograms.xml
@@ -11307,6 +11307,11 @@ Therefore, the affected-histogram name has to have at least one dot in it.
   <summary>
     Rough estimate of the fastest round-trip-time seen on a 2G connection,
     before the NetworkChangeNotifier detected a connectivity change.
+
+    This metric is recorded when the NetworkChangeNotifier detects a
+    connectivity change.  This will miss data from users whose connection type
+    never changes and will be biased to users whose connection type changes
+    frequently.
   </summary>
 </histogram>
 
@@ -11315,6 +11320,11 @@ Therefore, the affected-histogram name has to have at least one dot in it.
   <summary>
     Rough estimate of the fastest round-trip-time seen on a 3G connection,
     before the NetworkChangeNotifier detected a connectivity change.
+
+    This metric is recorded when the NetworkChangeNotifier detects a
+    connectivity change.  This will miss data from users whose connection type
+    never changes and will be biased to users whose connection type changes
+    frequently.
   </summary>
 </histogram>
 
@@ -11323,6 +11333,24 @@ Therefore, the affected-histogram name has to have at least one dot in it.
   <summary>
     Rough estimate of the fastest round-trip-time seen on a 4G connection,
     before the NetworkChangeNotifier detected a connectivity change.
+
+    This metric is recorded when the NetworkChangeNotifier detects a
+    connectivity change. This will miss data from users whose connection type
+    never changes and will be biased to users whose connection type changes
+    frequently.
+  </summary>
+</histogram>
+
+<histogram name="NCN.CM.FastestRTTOnBluetooth" units="milliseconds">
+  <owner>pauljensen@chromium.org</owner>
+  <summary>
+    Rough estimate of the fastest round-trip-time seen on a Bluetooth
+    connection, before the NetworkChangeNotifier detected a connectivity change.
+
+    This metric is recorded when the NetworkChangeNotifier detects a
+    connectivity change.  This will miss data from users whose connection type
+    never changes and will be biased to users whose connection type changes
+    frequently.
   </summary>
 </histogram>
 
@@ -11331,6 +11359,11 @@ Therefore, the affected-histogram name has to have at least one dot in it.
   <summary>
     Rough estimate of the fastest round-trip-time seen on an Ethernet
     connection, before the NetworkChangeNotifier detected a connectivity change.
+
+    This metric is recorded when the NetworkChangeNotifier detects a
+    connectivity change.  This will miss data from users whose connection type
+    never changes and will be biased to users whose connection type changes
+    frequently.
   </summary>
 </histogram>
 
@@ -11340,6 +11373,11 @@ Therefore, the affected-histogram name has to have at least one dot in it.
     Rough estimate of the fastest round-trip-time seen while the
     NetworkChangeNotifier thought there was no network connection, before the
     NetworkChangeNotifier detected a connectivity change.
+
+    This metric is recorded when the NetworkChangeNotifier detects a
+    connectivity change.  This will miss data from users whose connection type
+    never changes and will be biased to users whose connection type changes
+    frequently.
   </summary>
 </histogram>
 
@@ -11348,6 +11386,11 @@ Therefore, the affected-histogram name has to have at least one dot in it.
   <summary>
     Rough estimate of the fastest round-trip-time seen on an unknown connection
     type, before the NetworkChangeNotifier detected a connectivity change.
+
+    This metric is recorded when the NetworkChangeNotifier detects a
+    connectivity change.  This will miss data from users whose connection type
+    never changes and will be biased to users whose connection type changes
+    frequently.
   </summary>
 </histogram>
 
@@ -11356,6 +11399,11 @@ Therefore, the affected-histogram name has to have at least one dot in it.
   <summary>
     Rough estimate of the fastest round-trip-time seen on a Wifi connection,
     before the NetworkChangeNotifier detected a connectivity change.
+
+    This metric is recorded when the NetworkChangeNotifier detects a
+    connectivity change.  This will miss data from users whose connection type
+    never changes and will be biased to users whose connection type changes
+    frequently.
   </summary>
 </histogram>
 
@@ -11364,6 +11412,11 @@ Therefore, the affected-histogram name has to have at least one dot in it.
   <summary>
     Time between switching to a 2G connection and receiving the first network
     data.
+
+    This metric is recorded when the NetworkChangeNotifier detects a
+    connectivity change.  This will miss data from users whose connection type
+    never changes and will be biased to users whose connection type changes
+    frequently.
   </summary>
 </histogram>
 
@@ -11372,6 +11425,11 @@ Therefore, the affected-histogram name has to have at least one dot in it.
   <summary>
     Time between switching to a 3G connection and receiving the first network
     data.
+
+    This metric is recorded when the NetworkChangeNotifier detects a
+    connectivity change.  This will miss data from users whose connection type
+    never changes and will be biased to users whose connection type changes
+    frequently.
   </summary>
 </histogram>
 
@@ -11380,6 +11438,24 @@ Therefore, the affected-histogram name has to have at least one dot in it.
   <summary>
     Time between switching to a 4G connection and receiving the first network
     data.
+
+    This metric is recorded when the NetworkChangeNotifier detects a
+    connectivity change.  This will miss data from users whose connection type
+    never changes and will be biased to users whose connection type changes
+    frequently.
+  </summary>
+</histogram>
+
+<histogram name="NCN.CM.FirstReadOnBluetooth" units="milliseconds">
+  <owner>pauljensen@chromium.org</owner>
+  <summary>
+    Time between switching to a Bluetooth connection and receiving the first
+    network data.
+
+    This metric is recorded when the NetworkChangeNotifier detects a
+    connectivity change.  This will miss data from users whose connection type
+    never changes and will be biased to users whose connection type changes
+    frequently.
   </summary>
 </histogram>
 
@@ -11388,6 +11464,11 @@ Therefore, the affected-histogram name has to have at least one dot in it.
   <summary>
     Time between switching to an Ethernet connection and receiving the first
     network data.
+
+    This metric is recorded when the NetworkChangeNotifier detects a
+    connectivity change.  This will miss data from users whose connection type
+    never changes and will be biased to users whose connection type changes
+    frequently.
   </summary>
 </histogram>
 
@@ -11395,6 +11476,11 @@ Therefore, the affected-histogram name has to have at least one dot in it.
   <owner>pauljensen@chromium.org</owner>
   <summary>
     Time between disconnecting and receiving the first network data.
+
+    This metric is recorded when the NetworkChangeNotifier detects a
+    connectivity change.  This will miss data from users whose connection type
+    never changes and will be biased to users whose connection type changes
+    frequently.
   </summary>
 </histogram>
 
@@ -11403,6 +11489,11 @@ Therefore, the affected-histogram name has to have at least one dot in it.
   <summary>
     Time between switching to an unknown connection type and receiving the first
     network data.
+
+    This metric is recorded when the NetworkChangeNotifier detects a
+    connectivity change.  This will miss data from users whose connection type
+    never changes and will be biased to users whose connection type changes
+    frequently.
   </summary>
 </histogram>
 
@@ -11411,6 +11502,11 @@ Therefore, the affected-histogram name has to have at least one dot in it.
   <summary>
     Time between switching to a Wifi connection and receiving the first network
     data.
+
+    This metric is recorded when the NetworkChangeNotifier detects a
+    connectivity change.  This will miss data from users whose connection type
+    never changes and will be biased to users whose connection type changes
+    frequently.
   </summary>
 </histogram>
 
@@ -11419,6 +11515,11 @@ Therefore, the affected-histogram name has to have at least one dot in it.
   <summary>
     How much data was transfered while connected via a 2G connection, before the
     NetworkChangeNotifier detected a connectivity change.
+
+    This metric is recorded when the NetworkChangeNotifier detects a
+    connectivity change.  This will miss data from users whose connection type
+    never changes and will be biased to users whose connection type changes
+    frequently.
   </summary>
 </histogram>
 
@@ -11427,6 +11528,11 @@ Therefore, the affected-histogram name has to have at least one dot in it.
   <summary>
     How much data was transfered while connected via a 3G connection, before the
     NetworkChangeNotifier detected a connectivity change.
+
+    This metric is recorded when the NetworkChangeNotifier detects a
+    connectivity change.  This will miss data from users whose connection type
+    never changes and will be biased to users whose connection type changes
+    frequently.
   </summary>
 </histogram>
 
@@ -11435,6 +11541,24 @@ Therefore, the affected-histogram name has to have at least one dot in it.
   <summary>
     How much data was transfered while connected via a 4G connection, before the
     NetworkChangeNotifier detected a connectivity change.
+
+    This metric is recorded when the NetworkChangeNotifier detects a
+    connectivity change.  This will miss data from users whose connection type
+    never changes and will be biased to users whose connection type changes
+    frequently.
+  </summary>
+</histogram>
+
+<histogram name="NCN.CM.KBTransferedOnBluetooth" units="KB">
+  <owner>pauljensen@chromium.org</owner>
+  <summary>
+    How much data was transfered while connected via a Bluetooth connection,
+    before the NetworkChangeNotifier detected a connectivity change.
+
+    This metric is recorded when the NetworkChangeNotifier detects a
+    connectivity change.  This will miss data from users whose connection type
+    never changes and will be biased to users whose connection type changes
+    frequently.
   </summary>
 </histogram>
 
@@ -11443,6 +11567,11 @@ Therefore, the affected-histogram name has to have at least one dot in it.
   <summary>
     How much data was transfered while connected via an Ethernet connection,
     before the NetworkChangeNotifier detected a connectivity change.
+
+    This metric is recorded when the NetworkChangeNotifier detects a
+    connectivity change.  This will miss data from users whose connection type
+    never changes and will be biased to users whose connection type changes
+    frequently.
   </summary>
 </histogram>
 
@@ -11452,6 +11581,11 @@ Therefore, the affected-histogram name has to have at least one dot in it.
     How much data was transfered while the NetworkChangeNotifier thought there
     was no network connection, before the NetworkChangeNotifier detected a
     connectivity change.
+
+    This metric is recorded when the NetworkChangeNotifier detects a
+    connectivity change.  This will miss data from users whose connection type
+    never changes and will be biased to users whose connection type changes
+    frequently.
   </summary>
 </histogram>
 
@@ -11460,6 +11594,11 @@ Therefore, the affected-histogram name has to have at least one dot in it.
   <summary>
     How much data was transfered while connected via an unknown connection type,
     before the NetworkChangeNotifier detected a connectivity change.
+
+    This metric is recorded when the NetworkChangeNotifier detects a
+    connectivity change.  This will miss data from users whose connection type
+    never changes and will be biased to users whose connection type changes
+    frequently.
   </summary>
 </histogram>
 
@@ -11468,6 +11607,11 @@ Therefore, the affected-histogram name has to have at least one dot in it.
   <summary>
     How much data was transfered while connected via a Wifi connection, before
     the NetworkChangeNotifier detected a connectivity change.
+
+    This metric is recorded when the NetworkChangeNotifier detects a
+    connectivity change.  This will miss data from users whose connection type
+    never changes and will be biased to users whose connection type changes
+    frequently.
   </summary>
 </histogram>
 
@@ -11476,6 +11620,11 @@ Therefore, the affected-histogram name has to have at least one dot in it.
   <summary>
     Rough estimate of peak throughput seen on a 2G connection, before the
     NetworkChangeNotifier detected a connectivity change.
+
+    This metric is recorded when the NetworkChangeNotifier detects a
+    connectivity change.  This will miss data from users whose connection type
+    never changes and will be biased to users whose connection type changes
+    frequently.
   </summary>
 </histogram>
 
@@ -11484,6 +11633,11 @@ Therefore, the affected-histogram name has to have at least one dot in it.
   <summary>
     Rough estimate of peak throughput seen on a 3G connection, before the
     NetworkChangeNotifier detected a connectivity change.
+
+    This metric is recorded when the NetworkChangeNotifier detects a
+    connectivity change.  This will miss data from users whose connection type
+    never changes and will be biased to users whose connection type changes
+    frequently.
   </summary>
 </histogram>
 
@@ -11492,6 +11646,24 @@ Therefore, the affected-histogram name has to have at least one dot in it.
   <summary>
     Rough estimate of peak throughput seen on a 4G connection, before the
     NetworkChangeNotifier detected a connectivity change.
+
+    This metric is recorded when the NetworkChangeNotifier detects a
+    connectivity change.  This will miss data from users whose connection type
+    never changes and will be biased to users whose connection type changes
+    frequently.
+  </summary>
+</histogram>
+
+<histogram name="NCN.CM.PeakKbpsOnBluetooth" units="Kbps">
+  <owner>pauljensen@chromium.org</owner>
+  <summary>
+    Rough estimate of peak throughput seen on a Bluetooth connection, before the
+    NetworkChangeNotifier detected a connectivity change.
+
+    This metric is recorded when the NetworkChangeNotifier detects a
+    connectivity change.  This will miss data from users whose connection type
+    never changes and will be biased to users whose connection type changes
+    frequently.
   </summary>
 </histogram>
 
@@ -11500,6 +11672,11 @@ Therefore, the affected-histogram name has to have at least one dot in it.
   <summary>
     Rough estimate of peak throughput seen on an Ethernet connection, before the
     NetworkChangeNotifier detected a connectivity change.
+
+    This metric is recorded when the NetworkChangeNotifier detects a
+    connectivity change.  This will miss data from users whose connection type
+    never changes and will be biased to users whose connection type changes
+    frequently.
   </summary>
 </histogram>
 
@@ -11509,6 +11686,11 @@ Therefore, the affected-histogram name has to have at least one dot in it.
     Rough estimate of peak throughput seen while the NetworkChangeNotifier
     thought there was no network connection, before the NetworkChangeNotifier
     detected a connectivity change.
+
+    This metric is recorded when the NetworkChangeNotifier detects a
+    connectivity change.  This will miss data from users whose connection type
+    never changes and will be biased to users whose connection type changes
+    frequently.
   </summary>
 </histogram>
 
@@ -11517,6 +11699,11 @@ Therefore, the affected-histogram name has to have at least one dot in it.
   <summary>
     Rough estimate of peak throughput seen on an unknown connection type, before
     the NetworkChangeNotifier detected a connectivity change.
+
+    This metric is recorded when the NetworkChangeNotifier detects a
+    connectivity change.  This will miss data from users whose connection type
+    never changes and will be biased to users whose connection type changes
+    frequently.
   </summary>
 </histogram>
 
@@ -11525,6 +11712,11 @@ Therefore, the affected-histogram name has to have at least one dot in it.
   <summary>
     Rough estimate of peak throughput seen on a Wifi connection, before the
     NetworkChangeNotifier detected a connectivity change.
+
+    This metric is recorded when the NetworkChangeNotifier detects a
+    connectivity change.  This will miss data from users whose connection type
+    never changes and will be biased to users whose connection type changes
+    frequently.
   </summary>
 </histogram>
 
@@ -11533,6 +11725,11 @@ Therefore, the affected-histogram name has to have at least one dot in it.
   <summary>
     How long was spent connected via a 2G connection, before the
     NetworkChangeNotifier detected a connectivity change.
+
+    This metric is recorded when the NetworkChangeNotifier detects a
+    connectivity change.  This will miss data from users whose connection type
+    never changes and will be biased to users whose connection type changes
+    frequently.
   </summary>
 </histogram>
 
@@ -11541,6 +11738,11 @@ Therefore, the affected-histogram name has to have at least one dot in it.
   <summary>
     How long was spent connected via a 3G connection, before the
     NetworkChangeNotifier detected a connectivity change.
+
+    This metric is recorded when the NetworkChangeNotifier detects a
+    connectivity change.  This will miss data from users whose connection type
+    never changes and will be biased to users whose connection type changes
+    frequently.
   </summary>
 </histogram>
 
@@ -11549,6 +11751,24 @@ Therefore, the affected-histogram name has to have at least one dot in it.
   <summary>
     How long was spent connected via a 4G connection, before the
     NetworkChangeNotifier detected a connectivity change.
+
+    This metric is recorded when the NetworkChangeNotifier detects a
+    connectivity change.  This will miss data from users whose connection type
+    never changes and will be biased to users whose connection type changes
+    frequently.
+  </summary>
+</histogram>
+
+<histogram name="NCN.CM.TimeOnBluetooth" units="milliseconds">
+  <owner>pauljensen@chromium.org</owner>
+  <summary>
+    How long was spent connected via a Bluetooth connection, before the
+    NetworkChangeNotifier detected a connectivity change.
+
+    This metric is recorded when the NetworkChangeNotifier detects a
+    connectivity change.  This will miss data from users whose connection type
+    never changes and will be biased to users whose connection type changes
+    frequently.
   </summary>
 </histogram>
 
@@ -11557,6 +11777,11 @@ Therefore, the affected-histogram name has to have at least one dot in it.
   <summary>
     How long was spent connected via an Ethernet connection, before the
     NetworkChangeNotifier detected a connectivity change.
+
+    This metric is recorded when the NetworkChangeNotifier detects a
+    connectivity change.  This will miss data from users whose connection type
+    never changes and will be biased to users whose connection type changes
+    frequently.
   </summary>
 </histogram>
 
@@ -11565,6 +11790,11 @@ Therefore, the affected-histogram name has to have at least one dot in it.
   <summary>
     How long was spent disconnected, before the NetworkChangeNotifier detected a
     connectivity change.
+
+    This metric is recorded when the NetworkChangeNotifier detects a
+    connectivity change.  This will miss data from users whose connection type
+    never changes and will be biased to users whose connection type changes
+    frequently.
   </summary>
 </histogram>
 
@@ -11573,6 +11803,11 @@ Therefore, the affected-histogram name has to have at least one dot in it.
   <summary>
     How long was spent connected via an unknown connection type, before the
     NetworkChangeNotifier detected a connectivity change.
+
+    This metric is recorded when the NetworkChangeNotifier detects a
+    connectivity change.  This will miss data from users whose connection type
+    never changes and will be biased to users whose connection type changes
+    frequently.
   </summary>
 </histogram>
 
@@ -11581,6 +11816,11 @@ Therefore, the affected-histogram name has to have at least one dot in it.
   <summary>
     How long was spent connected via a Wifi connection, before the
     NetworkChangeNotifier detected a connectivity change.
+
+    This metric is recorded when the NetworkChangeNotifier detects a
+    connectivity change.  This will miss data from users whose connection type
+    never changes and will be biased to users whose connection type changes
+    frequently.
   </summary>
 </histogram>