AdminLogs and Auditing

Logs and Auditing

Know what every agent did, as whom, and what it cost. Archestra logs every model request, tool call, and admin change, from Chat, messaging channels, and connected clients. You do not turn anything on.

To forward events from the Audit tab to your SIEM, configure audit log export.

An incident investigation with model requests and parallel MCP tool calls on a shared waterfall timeline, including timing, tokens, cost, and conversation details

What Gets Logged

TabOne row perOpen a row for
LLM ProxySession: agent, model, tokens, spendThe whole conversation. Export JSON saves it.
MCP GatewayTool call: tool, gateway, account used, resultThe arguments and the full result
AuditChange: who, what, when, and if it succeededThe values before and after, the source IP, and any admin acting as someone else
GuardrailsRequest to a service used by Guardrails: service, tool, outcome. Or a yell: the report, who sent it, and whether it is resolvedThe service request and reply, or the whole report
Agent connectionsCalls grouped by user, agent, or gateway; setup and disconnect events under ActivityDrill into a group to see which agents and gateways it used

Open an LLM Proxy session to see every request and the MCP tool calls it triggered on one timeline; select a row for its timing, tokens, cost, conversation, and raw request and response. Requests handled by an auto router are marked auto→ and open to an Auto routing panel showing the router, tier scores, chosen model, and estimated savings. A tool call opened from the MCP Gateway tab shows where it sat in its session, or nearby calls from the same caller when it is not linked to one. Timing measures request processing before the log is saved, including the full stream for LLM requests. Older records may have no timing.

When your coding agent hands a task to a Remote Agent and brings it back, the run's requests join the session's timeline. Ran on shows when the work was in your client and when it was in Agent Runtime. Click an Agent Runtime stretch to open the run.

If a model response stream ends cleanly before its provider reports token counts, the request still appears in the session with any response received so far. Its token count shows Unknown rather than zero; zero means the provider actually reported zero.

A session's Status shows Failed when a request failed or a Chat turn ended in an error, even if every request row looks healthy. The session page lists those errors under Failed turns, as the user saw them, and marks the last request before each one Turn failed. Export JSON includes them.

In Agent connections, the Usage tab groups calls with Show and by; select a bar or row to drill down, and Back to step out. The page follows the selected date range, except the State column on User connections, which always reflects the last 30 days. User connections lists users with no calls too, and Export CSV saves the filtered list.

Keep Prompts Out of the Logs

Keep the cost and audit trail without storing what people sent. Set ARCHESTRA_LOGS_CONTENT_MODE=metadata_only and restart Archestra. Each row still shows the agent, the model or tool, the account used, tokens, cost, and whether the call failed. Opening it shows Content not stored instead of the prompt, response, arguments, or result.

  • Rows already stored keep their content.
  • Traces leave the content out too, even when content capture is on.
  • Chat history is not affected.

Keep Media in the Logs

By default, logs keep the conversation text but not the images, audio, and files in it. Each row shows Not kept: media logging is off where media was. To let Logs show and play media, go to Settings → LLM, turn on Keep media in logs, and click Save.

  • The setting covers model requests and responses and MCP tool calls, from Chat, agents, and connected clients.
  • Changing it needs organizationSettings:update and applies to new rows only.
  • Traces never carry media, whatever the setting.

Who Can Read Them

One permission shows your own logs. An admin permission shows everyone's.

TabYour ownEveryone's
LLM Proxy, MCP Gateway, Guardrailslog:readlog:admin
AuditauditLog:readauditLog:admin

Sharing an agent or a gateway with someone does not let them read its logs.

What to Know