Separate UMA histograms for user and device policy invalidation

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 dce89b4b973c7c79a1cdb76bea0b40d67a63a8dc..e238b63a8c4fc2678aafcd36c78ef5ce23c2f2f4 100644
--- a/tools/metrics/histograms/histograms.xml
+++ b/tools/metrics/histograms/histograms.xml
@@ -5750,6 +5750,27 @@ Therefore, the affected-histogram name has to have at least one dot in it.
   <summary>URL fetcher status for auto-enrollment requests.</summary>
 </histogram>
 
+<histogram name="Enterprise.DevicePolicyInvalidations"
+    enum="EnterprisePolicyInvalidations">
+  <owner>bartfab@chromium.org</owner>
+  <summary>
+    Events for counting device policy invalidations received with and without
+    payloads. Invalidations indicate that a policy has been updated and should
+    be refreshed. Payloads provide context about the policy update, but may be
+    absent if dropped by the invalidation service.
+  </summary>
+</histogram>
+
+<histogram name="Enterprise.DevicePolicyRefresh" enum="EnterprisePolicyRefresh">
+  <owner>bartfab@chromium.org</owner>
+  <summary>
+    Events measuring effectiveness of refreshing device policy when
+    invalidations are received from a service. For each refresh, indicates
+    whether the policy changed, and whether the policy was invalidated at the
+    time of the refresh.
+  </summary>
+</histogram>
+
 <histogram name="Enterprise.DMToken" enum="EnterpriseDMTokenType">
   <owner>joaodasilva@chromium.org</owner>
   <summary>
@@ -5849,9 +5870,9 @@ Therefore, the affected-histogram name has to have at least one dot in it.
     enum="EnterprisePolicyInvalidations">
   <owner>joaodasilva@chromium.org</owner>
   <summary>
-    Events for counting policy invalidations received with and without payloads.
-    Invalidations indicate that a policy has been updated and should be
-    refreshed. Payloads provide context about the policy update, but may be
+    Events for counting user policy invalidations received with and without
+    payloads. Invalidations indicate that a policy has been updated and should
+    be refreshed. Payloads provide context about the policy update, but may be
     absent if dropped by the invalidation service.
   </summary>
 </histogram>
@@ -5876,8 +5897,8 @@ Therefore, the affected-histogram name has to have at least one dot in it.
 <histogram name="Enterprise.PolicyRefresh" enum="EnterprisePolicyRefresh">
   <owner>joaodasilva@chromium.org</owner>
   <summary>
-    Events measuring effectiveness of refreshing policy when invalidations are
-    received from a service. For each refresh, indicates whether the policy
+    Events measuring effectiveness of refreshing user policy when invalidations
+    are received from a service. For each refresh, indicates whether the policy
     changed, and whether the policy was invalidated at the time of the refresh.
   </summary>
 </histogram>