Index: tools/metrics/histograms/histograms.xml |
diff --git a/tools/metrics/histograms/histograms.xml b/tools/metrics/histograms/histograms.xml |
index 94e3845d52afa8b8dc23ee7c5e6335a47f9649ae..932a4d29d74dbb043b011a410867e0c896d818d7 100644 |
--- a/tools/metrics/histograms/histograms.xml |
+++ b/tools/metrics/histograms/histograms.xml |
@@ -5756,6 +5756,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> |
@@ -5855,9 +5876,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> |
@@ -5882,8 +5903,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> |