Lines Matching refs:metrics

4 The metricsd daemon is used to gather metrics from the platform and application,
6 The metrics will then be available in their aggregated form to the developer
16 metrics collection. All metrics collection is funneled through this library. The
17 easiest and recommended way for a client-side module to collect user metrics is
18 to link `libmetrics` and use its APIs to send metrics to `metricsd` for transport to
24 - To access the metrics library API in the module, include the
25   <metrics/metrics_library.h> header file.
31 - Samples are uploaded only if the `/data/misc/metrics/enabled` file exists.
37 You will be able to see all uploaded metrics on the metrics dashboard,
41 It usually takes a day for metrics to be available on the dashboard.
59 `metricsd` is the daemon that listens for metrics logging calls (via Binder),
60 aggregates the metrics and uploads them periodically. This daemon should start as
65 * The binder thread listens for one-way Binder calls, aggregates the metrics in
69 * The uploader thread takes care of backing up the metrics to disk periodically
70   (to avoid losing metrics on crashes), collecting metadata about the client
71   (version number, channel, etc..) and uploading the metrics periodically to the
82 The recommended way to generate metrics data from a module is to link and use
120 * Run `metrics_client -d` to dump the currently aggregated metrics. Your
122 * Make sure that the aggregated metrics were uploaded to the server successfully