UMA metrics for cloud policies.

chrome/browser/policy/cloud_policy_controller.cc

Index: chrome/browser/policy/cloud_policy_controller.cc
diff --git a/chrome/browser/policy/cloud_policy_controller.cc b/chrome/browser/policy/cloud_policy_controller.cc
index 8c3ba08c9d3518cbfb1c9ea1518b376c636c6176..1d630cf0fb389d39473ae1bd69a3d509c5781002 100644
--- a/chrome/browser/policy/cloud_policy_controller.cc
+++ b/chrome/browser/policy/cloud_policy_controller.cc
@@ -16,6 +16,7 @@
 #include "chrome/browser/policy/cloud_policy_subsystem.h"
 #include "chrome/browser/policy/device_management_backend.h"
 #include "chrome/browser/policy/device_management_service.h"
+#include "chrome/browser/policy/enterprise_metrics.h"
 #include "chrome/browser/policy/proto/device_management_constants.h"
 
 // Domain names that are known not to be managed.
@@ -112,8 +113,11 @@ void CloudPolicyController::HandlePolicyResponse(
       cache_->SetPolicy(response.response(0));
       SetState(STATE_POLICY_VALID);
     } else {
+      em::LogPolicyOperation(em::kPolicyFetchBadResponse);

[kmixter1, 2011/06/28 01:06:02]

Have we considered/investigated a paging/escalation system for these if we see
spikes in errors?

[Joao da Silva, 2011/06/30 12:57:00]

AFAIK that hasn't been discussed yet. It would be great to have it for
BadResponses and for spikes in other events too. Let's discuss it in the next
meeting.

[kmixter1, 2011/06/30 23:28:59]

Once this hits stable, we should present these in one of the meetings and start
considering how they could be turned into inputs for alert systems.

       SetState(STATE_POLICY_UNAVAILABLE);
     }
+  } else {
+    em::LogPolicyOperation(em::kPolicyFetchBadResponse);
   }
 }