TotalApp Docs

Observability & Logs

See what every AI agent did: tokens used, tools called, errors thrown — across all apps and users.

Overview

Observability provides a detailed execution trace for every AI agent call that occurs inside a TotalApp workflow. Unlike the Monitoring screen (which tracks workflow-level status), Observability drills into the LLM layer — showing you exactly what the model received, what it decided to do, and what it produced.

This is the primary debugging and auditing tool for AI-powered pipelines. When an agent behaves unexpectedly, Observability lets you inspect the full context window the model saw, every tool call it made, and the exact token counts billed to your API account.

Screen preview

A quick look at the screens. Use the toggle in the corner of each preview to switch between the dark and light themes.

app.totalapp.app/analytics/observability
📡 Observability ● Live
142ms
P50 Latency
0.4%
Error Rate
8.2K
Req / min
Latency — Last 30 min
API Gateway 98ms OK
Analytics Service 142ms OK
Graph Engine 380ms Slow
Data Ingestion 54ms OK

Service observability

app.totalapp.app/observability
Observability
Analytics ServiceOK
Graph EngineDegraded
Data IngestionSlow
Weekly digestScheduled

Service health and weekly digest

app.totalapp.app/orch-observability
Total Calls
2,847
Tokens Used
1.2M
Avg Latency
342ms
Error Rate
0.8%
TimeSourceModelTokensms
14:22:01 Agent Arch. claude-sonnet-4-6 1,247 284
14:21:58 Prompt Lab claude-sonnet-4-6 847 312
14:21:45 HR Reports claude-sonnet-4-6 2,103 891
14:21:30 Tool Registry tinyllama-1.1b 312 124
14:21:12 Ecommerce claude-sonnet-4-6 3,891 timeout
14:20:57 Knowledge Base claude-sonnet-4-6 1,530 402
14:20:41 Model Center tinyllama-1.1b 268 97
14:20:15 Persona Editor claude-sonnet-4-6 964 655

Observability: live AI call log

Trace View

Each agent execution produces one trace entry. The trace expands into a timeline of events:

  • System prompt — the full system prompt sent to the model, including any persona blocks and injected knowledge-base chunks.
  • User message — the input the agent received from the upstream workflow node.
  • Tool calls — each tool the model invoked, with the exact arguments it passed and the value returned by the tool implementation.
  • Assistant response — the model's final text output after all tool calls resolved.
  • Token usage — input tokens, output tokens, and total tokens. For cloud models, this maps directly to API billing.
  • Latency — time from first token sent to last token received, broken down by model time vs. tool execution time.

Use Trace View to Cut Token Costs

Open a trace and look at the system prompt section. If you see large blocks of knowledge-base text that are not relevant to the query, your retrieval is too broad. Tighten the chunk size in the Knowledge Base or reduce the number of retrieved chunks per query to lower input token counts.

Filters and Search

  • Agent filter — show traces for a specific named agent or all agents.
  • Time range — last hour, last 24 hours, last 7 days, or a custom date range.
  • Status filter — success, error, or tool-call-only (traces where the model called at least one tool).
  • User filter — in multi-user deployments, filter traces by the user whose workflow triggered the agent call.
  • Search — full-text search across prompt content and agent responses to find traces containing a specific topic or error message.

Aggregated Metrics

The top of the Observability screen shows aggregate stats for the selected time range and filters:

  • Total calls — number of agent executions.
  • Total tokens — combined input + output tokens across all calls.
  • Average tokens per call — useful for spotting prompt-size regressions after a system prompt change.
  • Error rate — percentage of calls that resulted in an error (model error, tool failure, or context-length exceeded).
  • Tool call rate — percentage of calls where the model invoked at least one tool. A sudden drop might indicate the agent is no longer reliably using its tools.

Observability vs. Monitoring

Monitoring (Automation mode) tracks workflow-level success and failure at the node granularity. Observability (AI Orchestration mode) tracks LLM-level details inside an agent node — tokens, tool calls, latency. Use both together: Monitoring to find which workflow step failed, Observability to understand what the model did inside that step.