TELEMETRY
Observing system behavior without altering it
Waxell Telemetry is a read-only observability layer for agentic systems — it captures traces, spans, model calls, token usage, and latency across every execution without participating in governance or altering system state.
Telemetry provides visibility into how agentic systems behave as they run. It exists to make execution understandable, diagnosable, and reviewable in production environments.
In a governed system, telemetry is observational. Telemetry does not control execution, enforce policy, or mutate system state.
Free during beta. 2-line setup.
What does Waxell Telemetry observe?
Telemetry reflects what the system did, not what it intended to do.
Waxell telemetry is derived from canonical execution events emitted by the orchestration layer and runtime. These events are recorded as execution proceeds and preserved independently of workflow logic.
Because telemetry is derived rather than authored, it remains consistent even as workflows change.
Waxell telemetry captures the signals that matter for diagnosis and review: traces and spans across workflow steps, model calls with input and output context, token usage per call, latency per execution step, and the governance evaluation points where policies and budgets were checked.
These signals are emitted by the runtime as execution proceeds. Nothing is reconstructed afterward.
Waxell Observe captures these signals automatically — a two-line SDK initialization, no changes to agent logic. The signals feed into execution records, the durable per-run artifacts available for review and audit.
Traces, spans, token counts, latency per step, governance evaluation points — all of it, for every agent execution, from the moment you add Waxell Observe. Two lines of Python. No code changes to your agents.
READ ONLY BY DESIGN
Telemetry is immutable: once recorded, it cannot be altered, ensuring an unambiguous record for diagnosis, review, and audit.
EXPLAINING OUTCOMES
Telemetry records execution paths and decision context, enabling post-hoc analysis of outcomes without reconstructing intent or replaying logic.
How is Waxell Telemetry separated from governance?
Key properties
Execution records are immutable. Once a telemetry event is recorded, it cannot be altered — ensuring the record remains a reliable basis for diagnosis, review, and audit, even as systems evolve and workflows change.
Telemetry records execution paths, not just outcomes. The decision context captured at each step explains why the system behaved as it did, not only what happened at the end.