Agent Trajectory Observability Format (ATOF)
Agent Trajectory Observability Format (ATOF)
Use the atof section when you want the raw Agent Trajectory Observability
Format (ATOF) 0.1 event stream written as JSONL.
ATOF JSONL export is useful for local debugging, offline inspection, and preserving the canonical event stream before it is translated into another format.
plugins.toml Example
This configuration registers the plugin-managed ATOF exporter and writes one
JSON object per lifecycle event to logs/events.jsonl.
Fields
Expected Output
Each emitted scope, tool, LLM, middleware, or mark event is written as one ATOF JSON object per line. For event field semantics, see Events.
Register the plugin before instrumented work starts and clear it during shutdown so file handles flush.
Plugin Configuration
Use plugin configuration when the application should let NeMo Relay own the ATOF exporter lifecycle.
Python
Node.js
Rust
Manual API
Use the manual AtofExporter API when a test or script needs a custom
subscriber name or explicit registration window.
Python
Node.js
Rust
Common Validation Failures
modeis notappendoroverwrite.- The output directory is not writable at runtime.
- ATOF is enabled in a target that cannot access the native filesystem.