Bypass data reduction proxy when using VPN

tools/metrics/actions/actions.xml

Index: tools/metrics/actions/actions.xml
diff --git a/tools/metrics/actions/actions.xml b/tools/metrics/actions/actions.xml
index fb613df197bb1eca80c55b226c2946d8ff88a601..9c3faf4dcdcd56fa3af0d83e7cc0a781a062345a 100644
--- a/tools/metrics/actions/actions.xml
+++ b/tools/metrics/actions/actions.xml
@@ -2191,6 +2191,22 @@ should be able to be added at any place in this file.
   <description>Please enter the description of this user action.</description>
 </action>
 
+<action name="DataReductionProxy_DisabledOnVPN">
+  <owner>bengr@chromium.org</owner>
+  <description>
+    Counts the number of times the data reduction proxy was disabled because the
+    device was using a VPN.
+  </description>
+</action>
+
+<action name="DataReductionProxy_IPAddressChanged">
+  <owner>bengr@chromium.org</owner>
+  <description>
+    Counts the number of times devices changed addresses while the data
+    reduction proxy was enabled.
+  </description>
+</action>

[Ilya Sherman, 2014/07/08 23:43:04]

Do you need timestamps for these events?  If not, I'd recommend using histograms
instead.

[bengr, 2014/07/10 18:22:40]

We don't need timestamps for these events, Are you just saying use an enumerated
histogram with each of these as a bucket?

+
 <action name="DataReductionProxy_PromoDisplayed">
   <owner>Please list the metric's owners. Add more owner tags as needed.</owner>
   <description>Please enter the description of this user action.</description>