Lines Matching refs:tracing

8 1. Whether you are interested only in tracing events coming from your own app
13 2. For app-specific tracing, whether you need to trace simple types of timeline
85 The SDK offers two abstraction layers to inject tracing data, built on top of
91 Track events are the suggested option when dealing with app-specific tracing as
130 Track events are the best default option and serve most tracing use cases with
154 apps for tracing. However, in some rare circumstances they are not
165 automatically create one instance of the class for each tracing session it is
213 trace config to enable tracing:
222 source. The lambda function passed to that method will only be called if tracing
224 multiple concurrent tracing sessions are active.
236 ensure data source isn't destroyed (e.g., because of stopping tracing) while
249 in both modes and respond both to in-process tracing requests and system
250 tracing requests. Both modes generate the same trace file format.
267 tracing sessions.
292 When using system mode, the tracing session must be controlled from the outside,
295 system traces, tracing data producers are not allowed to read back the trace
304   [Linux quickstart](/docs/quickstart/linux-tracing.md) for instructions.
319 typically want to choose the categories which are enabled for tracing.
347 After building the trace config, you can begin tracing:
360 Now that tracing is active, instruct your app to perform the operation you
361 want to record. After that, stop tracing and collect the
377 to close the file after tracing is done:
393 [atrace-ndk]: https://developer.android.com/ndk/reference/group/tracing