Add analytics to analyzer-cli and analysis server.

pkg/analysis_server/lib/src/domain_analysis.dart

Index: pkg/analysis_server/lib/src/domain_analysis.dart
diff --git a/pkg/analysis_server/lib/src/domain_analysis.dart b/pkg/analysis_server/lib/src/domain_analysis.dart
index eb75faacdb19bf845e022a1e7a51a6cba44a99f1..3d8a2b479c3d92246abc0ad7fb41f1428154de79 100644
--- a/pkg/analysis_server/lib/src/domain_analysis.dart
+++ b/pkg/analysis_server/lib/src/domain_analysis.dart
@@ -248,6 +248,8 @@ class AnalysisDomainHandler extends AbstractRequestHandler {
    * Implement the 'analysis.reanalyze' request.
    */
   Response reanalyze(Request request) {
+    server.options.analytics.sendEvent('analysis', 'reanalyze');

[Brian Wilkerson, 2017/06/30 18:51:22]

For consistency it might be useful to make all of the request implementation
methods follow a similar pattern, such as: extract parameters from the request,
send analytics, respond to the request.

[devoncarew, 2017/06/30 21:58:13]

Sounds good! I may implement in a follow-up CL. It would be nice to refactor a
bit so the domain is always available (as a field on AbstractRequestHandler, or
a getter on Request).

+
     AnalysisReanalyzeParams params =
         new AnalysisReanalyzeParams.fromRequest(request);
     List<String> roots = params.roots;
@@ -284,6 +286,10 @@ class AnalysisDomainHandler extends AbstractRequestHandler {
     var params = new AnalysisSetAnalysisRootsParams.fromRequest(request);
     List<String> includedPathList = params.included;
     List<String> excludedPathList = params.excluded;
+
+    server.options.analytics.sendEvent('analysis', 'setAnalysisRoots',
+        value: includedPathList.length);
+
     // validate
     for (String path in includedPathList) {
       if (!server.isValidFilePath(path)) {