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 85c7346c99aa00051281e232a566e367816cd3da..9b0b7e26731caff4887706d3798d92f2168bbfa4 100644
--- a/tools/metrics/histograms/histograms.xml
+++ b/tools/metrics/histograms/histograms.xml
@@ -15573,6 +15573,20 @@ http://cs/file:chrome/histograms.xml - but prefer this file for new entries.
   </summary>
 </histogram>
 
+<histogram name="Enterprise.PolicyUpdatePeriod.Device" units="days">

[bartfab (slow), 2017/06/12 15:01:58]

Are you sure days are a good unit here? IIRC, our fallback policy polling
happens once every 24 hours, so pretty much all active users will have a 1 in
the histogram.

[Denis Kuznetsov (DE-MUC), 2017/07/03 10:20:00]

Yes, as we are trying to estimate the long tail of the of the curve so that we
can remove old dmtokens for ephemeral sessions.

+  <owner>antrim@chromium.org</owner>
+  <summary>
+    Time since last device policy fetch.
+  </summary>
+</histogram>
+
+<histogram name="Enterprise.PolicyUpdatePeriod.User" units="days">
+  <owner>antrim@chromium.org</owner>
+  <summary>
+    Time since last user policy fetch.
+  </summary>
+</histogram>
+
 <histogram name="Enterprise.PublicSession.SessionLength" units="minutes">
   <owner>xiyuan@chromium.org</owner>
   <owner>sduraisamy@chromium.org</owner>