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 a96e994d642d164532ea795b2440dc2a7e53abec..5cdc00b4eeba1b66823f72f09ccd7cc454bf8e4f 100644
--- a/tools/metrics/histograms/histograms.xml
+++ b/tools/metrics/histograms/histograms.xml
@@ -2438,6 +2438,92 @@ http://cs/file:chrome/histograms.xml - but prefer this file for new entries.
   </summary>
 </histogram>
 
+<histogram name="BackgroundSync.Event.OneShotResult" enum="BooleanSuccess">
+  <owner>iclelland@chromium.org</owner>
+  <summary>Records whether a one-shot sync event succeeded or failed.</summary>
+</histogram>
+
+<histogram name="BackgroundSync.Event.PeriodicResult" enum="BooleanSuccess">
+  <owner>iclelland@chromium.org</owner>
+  <summary>Records whether a periodic sync event succeeded or failed.</summary>
+</histogram>
+
+<histogram name="BackgroundSync.Event.Time" units="milliseconds">
+  <owner>iclelland@chromium.org</owner>
+  <summary>Time taken to execute all sync events to completion.</summary>
+</histogram>
+
+<histogram name="BackgroundSync.Registration.OneShot"
+    enum="BackgroundSyncRegistrationResult">
+  <owner>iclelland@chromium.org</owner>
+  <summary>
+    Records the result of attempting to register a one-shot sync.
+  </summary>
+</histogram>
+
+<histogram name="BackgroundSync.Registration.OneShot.CouldFire"
+    enum="BooleanCouldFireImmediately">
+  <owner>iclelland@chromium.org</owner>
+  <summary>
+    Records the result of attempting to register a one-shot sync in a situation
+    where the sync could fire immediately.
+  </summary>
+</histogram>
+
+<histogram name="BackgroundSync.Registration.Periodic"
+    enum="BackgroundSyncRegistrationResult">
+  <owner>iclelland@chromium.org</owner>
+  <summary>
+    Records the result of attempting to register a periodic sync.
+  </summary>
+</histogram>
+
+<histogram name="BackgroundSync.Registration.Periodic.CouldFire"
+    enum="BooleanCouldFireImmediately">
+  <owner>iclelland@chromium.org</owner>
+  <summary>
+    Records the result of attempting to register a periodic sync in a situation
+    where the sync could fire immediately.
+  </summary>
+</histogram>
+
+<histogram name="BackgroundSync.Unregistration.OneShot" enum="BooleanSuccess">
+  <owner>iclelland@chromium.org</owner>
+  <summary>
+    Records the result of attempting to unregister a one-shot sync.
+  </summary>
+</histogram>
+
+<histogram name="BackgroundSync.Unregistration.Periodic" enum="BooleanSuccess">
+  <owner>iclelland@chromium.org</owner>
+  <summary>
+    Records the result of attempting to unregister a periodic sync.
+  </summary>
+</histogram>
+
+<histogram name="BackgroundSync.WakeUp.OneShot" enum="BooleanSuccess">
+  <owner>iclelland@chromium.org</owner>
+  <summary>
+    Records the fact that Chrome was started by the Background Sync Manager in
+    order to fire a registered one-shot sync event.
+  </summary>
+</histogram>
+
+<histogram name="BackgroundSync.WakeUp.Periodic" enum="BooleanSuccess">
+  <owner>iclelland@chromium.org</owner>
+  <summary>
+    Records the fact that Chrome was started by the Background Sync Manager in
+    order to fire a registered periodic sync event.

[Alexei Svitkine (slow), 2015/07/09 21:02:57]

This description doesn't tell me much about what a false or true event is.

Is a false event that Chrome was started for some other purpose than the
Background Sync Manager to fire the event... Please clarify.

[iclelland, 2015/07/10 14:57:26]

False here would indicate that the wakeup was wasted -- that is, the sync event
that we woke the browser up for didn't actually exist, or we tried to run it and
it failed. It means that Chrome wasn't ablt to do any useful work.

Would a better enum be in order here, or just a different description?

[Alexei Svitkine (slow), 2015/07/10 15:12:50]

It sounds like an enum would be a better fit here indeed.

+  </summary>
+</histogram>
+
+<histogram name="BackgroundSync.WakeUp.Time" units="milliseconds">
+  <owner>iclelland@chromium.org</owner>
+  <summary>
+    Time taken to start Chrome in order to fire a registered sync event.
+  </summary>
+</histogram>
+
 <histogram name="BatteryStatus.NumberBatteriesLinux"
     enum="BatteryStatusNumberBatteries">
   <owner>timvolodine@chromium.org</owner>
@@ -50443,6 +50529,12 @@ http://cs/file:chrome/histograms.xml - but prefer this file for new entries.
   <int value="3" label="AUTO_LAUNCH_FOREGROUND_USELESS"/>
 </enum>
 
+<enum name="BackgroundSyncRegistrationResult" type="int">
+  <int value="0" label="REGISTRATION_RESULT_SUCCEEDED"/>
+  <int value="1" label="REGISTRATION_RESULT_FAILED"/>
+  <int value="2" label="REGISTRATION_RESULT_DUPLICATE"/>
+</enum>
+
 <enum name="BackgroundTracingState" type="int">
   <int value="0" label="Scenario activation requested"/>
   <int value="1" label="Scenario successfully activated"/>
@@ -50734,6 +50826,11 @@ http://cs/file:chrome/histograms.xml - but prefer this file for new entries.
   <int value="1" label="Corrupt"/>
 </enum>
 
+<enum name="BooleanCouldFireImmediately" type="int">
+  <int value="0" label="Could not fire immediately"/>
+  <int value="1" label="Could fire immediately"/>
+</enum>
+
 <enum name="BooleanCovered" type="int">
   <int value="0" label="Not Covered"/>
   <int value="1" label="Covered"/>