Skip to main content
InteraOne records AI calls and execution events without making the gateway wait for every analytics write. Agent-side trackers capture latency, tokens, estimated cost, provider/model metadata, success, and errors; an observability worker batches events for persistence.

​
Recorded signals

​
number
End-to-end or provider-call duration, depending on the event type.
​
object
Prompt, completion, and total token counts when the provider returns usage.
​
number
Estimated provider cost based on the configured model registry; treat this as an estimate.
​
boolean
required
Whether the operation completed successfully.
​
object
Provider, model, tool, channel, run, and other structured diagnostic context.
System events are indexed by organization, category, event type, time, provider, and model. The collection has a 90-day TTL index in the current model.

​
Three levels of diagnosis

  • AI queue age or failed jobs exceed normal bounds.
  • Provider success rate or time to first token degrades.
  • Tool error rate spikes by tool name.
  • Fallback and human-escalation rate changes unexpectedly.
  • Qdrant or embedding calls fail or return no context unusually often.
  • Observability/analytics workers repeatedly fail to flush.
Do not put raw secrets, OTPs, authorization headers, or unnecessary message content in telemetry. Logs and events are operational data and need the same tenant access controls and retention discipline as application records.
Last modified on July 17, 2026