Add Installer.TimeToRebootMinutes metric
This patch introduces a new metric for tracking the duration between
when an update has successfully completed (and the user is presented
with the "reboot arrow" in the panel) and when the system has booted
into the new update.
BUG=chromium:248800
TEST=New unit test + Unit tests pass + Manual tested
Change-Id: Ia22cedc3b70f1d9c2598bed9469b34a257546a64
Reviewed-on: https://gerrit.chromium.org/gerrit/59132
Reviewed-by: Don Garrett <dgarrett@chromium.org>
Reviewed-by: Chris Sosa <sosa@chromium.org>
Tested-by: David Zeuthen <zeuthen@chromium.org>
Commit-Queue: David Zeuthen <zeuthen@chromium.org>
diff --git a/payload_state.h b/payload_state.h
index f8a2d0c..7c0d0d3 100644
--- a/payload_state.h
+++ b/payload_state.h
@@ -85,6 +85,8 @@
return num_reboots_;
}
+ virtual void UpdateEngineStarted();
+
private:
// Increments the payload attempt number which governs the backoff behavior
// at the time of the next update check.
@@ -280,6 +282,17 @@
// increments num_reboots.
void UpdateNumReboots();
+ // Writes the current wall-clock time to the kPrefsSystemUpdatedMarker
+ // state variable.
+ void CreateSystemUpdatedMarkerFile();
+
+ // Called at program startup if the device booted into a new update.
+ // The |time_to_reboot| parameter contains the (wall-clock) duration
+ // from when the update successfully completed (the value written
+ // into the kPrefsSystemUpdatedMarker state variable) until the device
+ // was booted into the update (current wall-clock time).
+ void BootedIntoUpdate(base::TimeDelta time_to_reboot);
+
// Interface object with which we read/write persisted state. This must
// be set by calling the Initialize method before calling any other method.
PrefsInterface* prefs_;