Skip to main content
Telemetry is the structured execution record for an Axilio phone session. It connects operations, inference work, file and media activity, output, and errors to the session where they happened. Use Telemetry to answer questions such as:
  • What did this session run?
  • Which operation took time or failed?
  • What did the run write to its console?
  • How did an SDK call relate to inference, file, or media work?
  • What billed-cost context is currently available for an operation?
Customers use Axilio Telemetry through the Dashboard, CLI, SDK helpers, and Axilio JSON API described in this section.

​
One record from live to retained

A phone session is the correlation boundary for Telemetry. You address its record by session_id. While a session is active, you can follow new spans and logs through the Dashboard, CLI, SDK helpers, or a read-only WebSocket. If you join late, the live service can replay a bounded recent window before it sends new data. When the session ends, the live URL stops working. You can then read the available retained record through the Dashboard, CLI, SDK helpers, or GET /phones/sessions/{session_id}/frames during its access window. First-party interfaces provide a path from live monitoring to retained reconciliation. Both access paths use the same tolerant JSON frame envelope. A frame is a wire representation of a span or log. Live spans can arrive in start and end phases, while the retained record represents each completed span as one completed frame.
Telemetry delivery is best effort. A live consumer must tolerate replayed frames and possible gaps. Reconcile with retained Telemetry after a gap, and do not treat either path as an exactly-once or lossless audit log.

​
Choose an interface

Start with Get started for one end-to-end session. Use the raw interfaces only when you need a custom reader or integration. Telemetry and recording are independent controls. Disabling recording does not disable Telemetry. Starting a direct session or workflow run with telemetry=false disables both live and retained Telemetry for that session.

​
Explore Telemetry

Get started

Follow one session from its first live frames to its retained trace.

Telemetry dashboard

Interpret operations, relationships, timing, output, errors, and cost context.

Follow live Telemetry

Attach to an active session through a first-party interface or WebSocket.

Retrieve Telemetry

Read and page through the available record by session ID.

Frame reference

Parse spans, logs, identifiers, timestamps, attributes, and additive values.

Data controls

Understand capture, retention, capability URLs, and sensitive-data boundaries.

Reliability and troubleshooting

Recover from gaps and diagnose disabled, empty, expired, or incompatible data.