tree: d16c1686168e8206368095832f49ea1faa182d78 [path history] [tgz]
  1. Android.mk
  2. boot_event_record_store.cpp
  3. boot_event_record_store.h
  4. boot_event_record_store_test.cpp
  5. bootstat.cpp
  6. event_log_list_builder.cpp
  7. event_log_list_builder.h
  8. event_log_list_builder_test.cpp
  9. README.md
  10. testrunner.cpp
bootstat/README.md

bootstat

The bootstat command records boot events (e.g., firmware_loaded, boot_complete) and the relative time at which these events occurred. The command also aggregates boot event metrics locally and logs the metrics for analysis.

Usage: bootstat [options]
options include:
  -d              Dump the boot event records to the console.
  -h              Show this help.
  -l              Log all metrics to logstorage.
  -r              Record the relative time of a named boot event.

Relative time

The timestamp recorded by bootstat is the uptime of the system, i.e., the number of seconds since the system booted.

Recording boot events

To record the relative time of an event during the boot phase, call bootstat with the -r option and the name of the boot event.

$ bootstat -r boot_complete

The relative time at which the command runs is recorded along with the name of the boot event to be persisted.

Logging boot events

To log the persisted boot events, call bootstat with the -l option.

$ bootstat -l

bootstat logs all boot events recorded using the -r option to the EventLog using the Tron histogram. On GMS devices these logs are uploaded via Clearcut for aggregation and analysis.

Printing boot events

To print the set of persisted boot events, call bootstat with the -p option.

$ bootstat -p
Boot events:
------------
boot_complete   71