Use better histogram parameters for duration metrics
In the current code this is capped at 20 minutes which is not helpful
as we're interested in data for devices that take much longer to
update. Instead, use one year for UpdateDuration and one month for
UpdateDurationUptime. Also move the code that sends the metric into
PayloadState to better conform with newly added code.
Also rename the metrics to they have the suffix Minutes. E.g. the new
metric names are
Installer.UpdateDurationMinutes
Installer.UpdateDurationUptimeMinutes
Also add unit test for utils::FormatTimeDelta().
BUG=None
TEST=Unit tests, look at chrome://histogram
Change-Id: I8581ec111f9833bdd72f10888c9626f40779f8b9
Reviewed-on: https://gerrit.chromium.org/gerrit/48558
Commit-Queue: David Zeuthen <zeuthen@chromium.org>
Reviewed-by: David Zeuthen <zeuthen@chromium.org>
Tested-by: David Zeuthen <zeuthen@chromium.org>
diff --git a/payload_state.h b/payload_state.h
index 43fe5cc..b12e6b0 100644
--- a/payload_state.h
+++ b/payload_state.h
@@ -120,6 +120,9 @@
// Reports the various metrics related to rebooting during an update.
void ReportRebootMetrics();
+ // Reports the various metrics related to update duration.
+ void ReportDurationMetrics();
+
// Resets all the persisted state values which are maintained relative to the
// current response signature. The response signature itself is not reset.
void ResetPersistedState();