Katexs
Traces

ObservabilityBeta

Traces

Step-by-step timing and cost of every call, chat reply and tool run.

What's traced

Katexs writes a trace for every voice call, every chat reply and every tool run. A trace has a correlation id (the call or chat session), the agent, the channel, the start time, the duration, the credit cost and a status, plus one span per step:

SpanExample
engine_callThe model producing a chat reply, or the voice call as a whole
toolbook_appointment, with redacted input and output
knowledgeThe sources retrieved for a chat reply

Chat traces also record the time to the first token and the token count.

Privacy

Inputs and outputs in traces are redacted summaries, and phone numbers and email addresses in tool inputs are masked. Traces are scoped to the workspace that created them.

Availability

The Traces view is in Beta and is being rolled out to workspaces. Traces are recorded for every workspace today. Ask support@katexs.com to enable the view for yours.

Last updated November 2026 · Found a problem? Email support@katexs.com