Telemetry Review

Review FPS, memory, battery, lifecycle, and custom telemetry in the local host player alongside logs, screenshots, touches, annotations, and artifacts.

Telemetry turns runtime behavior into time-series evidence instead of isolated events. The local player aligns each channel with the session timeline so a reviewer can connect performance changes with screens, logs, touches, and app state.

Telemetry sources

Depending on SDK configuration, a session can contain:

  • FPS and frame timing;
  • memory usage;
  • battery level;
  • app lifecycle state;
  • custom counters, gauges, and state channels.

The host stores samples with timestamps and preserves their channel metadata for later review.

Review a range

Use a timeline range when you need statistics over one interaction and the full timeline when trend shape matters. Typical questions include:

  • Did memory climb throughout the flow or spike once?
  • Did FPS fall before or after navigation?
  • Did battery or lifecycle state change near the issue?
  • Which custom channel changed near a screenshot, gesture, or log cluster?

Add an annotation to preserve the conclusion or extract the relevant range into a focused session.

The player’s global Trends area groups longer-lived quality signals by app. It shows the current measurement, reference, delta, decision, and stored history. Rebuild one app’s trends after changing workspace rules when you need stored measurements re-evaluated without rerunning the app.

Use ansight session metrics <session-id> --json for raw samples and ansight session telemetry analyze <session-id> --json for bounded FPS-drop and memory-spike findings. See CLI Commands.