feros
Runtime

Recording and Tracing

Session recording and observability flow in feros.

Recording and Tracing

Recording

  • voice/server can write call recordings based on recording config
  • Docker default uses shared recordings volume and file:///recordings
  • studio/api serves recording files through recordings routes

Tracing and Events

  • Runtime emits structured session events
  • voice-trace adapters can persist DB events and external traces
  • Observability settings are configurable through /api/settings/observability

Typical Diagnostics

  • Stage latency (STT/LLM/TTS)
  • Session lifecycle anomalies
  • Tool-call failures and retries

On this page