Quantify initial stability report edge cases.

components/metrics/proto/system_profile.proto

 // Copyright 2014 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 //
 // Stores information about the user's brower and system configuration.
 // The system configuration fields are recorded once per client session.
 
 syntax = "proto2";
 
 option optimize_for = LITE_RUNTIME;
@@ skipping 422 matching lines @@
     optional bool is_disabled = 4;
 
     // True if the plugin is PPAPI.
     optional bool is_pepper = 5;
   }
   repeated Plugin plugin = 7;
 
   // Figures that can be used to generate application stability metrics.
   // All values are counts of events since the last time that these
   // values were reported.
-  // Next tag: 28
+  // Next tag: 31
   message Stability {
     // Total amount of time that the program was running, in seconds,
     // since the last time a log was recorded, as measured using a client-side
     // clock implemented via TimeTicks, which guarantees that it is monotonic
     // and does not jump if the user changes their clock.  The TimeTicks
     // implementation also makes the clock not count time the computer is
     // suspended.
     optional int64 incremental_uptime_sec = 1;
 
     // Total amount of time that the program was running, in seconds,
@@ skipping 88 matching lines @@
       optional int32 instance_count = 3;
 
       // The number of times this plugin process crashed.
       // This value will be <= |launch_count|.
       optional int32 crash_count = 4;
 
       // The number of times this plugin could not be loaded.
       optional int32 loading_error_count = 5;
     }
     repeated PluginStability plugin_stability = 22;
+
+    // The number of times a stability log's upload was deferred.
+    optional int32 deferred_count = 28;
+
+    // The number of times stability data was discarded. Note that this count
+    // is not version specific and instead accumulates across versions.
+    optional int32 discard_count = 29;
+
+    // The number of times the serialized system profile's version did not match
+    // the pref version.
+    optional int32 version_mismatch_count = 30;

[Alexei Svitkine (slow), 2016/08/30 21:25:59]

I'd actually prefer these be added as histograms.

Histograms have a number of advantages: not needing any server-side changes,
automatically useable from the various dashboards we have, less "set in stone" -
so that can be added/removed "easier".

You can still have the prefs that persist the values between sessions, but the
actual values can be logged as histograms.

[manzagop (departed), 2016/09/01 21:26:56]

Done.

   }
   optional Stability stability = 8;
 
   // Description of a field trial or experiment that the user is currently
   // enrolled in.
   // All metrics reported in this upload can potentially be influenced by the
   // field trial.
   message FieldTrial {
     // The name of the field trial, as a 32-bit identifier.
     // Currently, the identifier is a hash of the field trial's name.
@@ skipping 249 matching lines @@
 
     // The hash of the product version. Might not be set if the product version
     // could not be obtained from the disk.
     optional fixed32 product_version_hash = 4;
 
     // The current state of the product.
     optional AntiVirusState product_state = 5;
   }
   repeated AntiVirusProduct antivirus_product = 23;
 }