Skip to main content
Tracing shows every turn any member has had with the Genie workspace AI, listed like a request log — status, which surface it came from, the model used, tokens, credits billed, duration, and which tools were called — with a detailed view of any individual turn.
Tracing requires a specific permission — See Genie AI traces — which only owners and admins hold by default, since traces include other members’ messages. Ask a workspace admin to grant it to your role if you need it. See Custom roles.

​
Open Tracing

Click the account row at the bottom of the workspace sidebar, choose Workspace settings, then open Governance, then open Tracing.

​
What the page shows

  • Stat tiles — total traces, error rate, total tokens, and average turn time, broken down into how long was spent before the AI model, inside it, and after.
  • Traces per day — a chart of daily volume, with failed turns shown as their own series so a bad day stands out at a glance.
  • Filters — time window (last 24 hours, 7 days, or 30 days), status (completed, failed, aborted, blocked), surface, and a free-text search across messages, answers, tool names, and errors.
  • The traces table — one row per turn: time, status, surface, message, model, tokens, credits, duration, tools called, and which member it was.
Click any row to open its full detail: a timeline of the turn’s phases, the member’s message, Genie’s reasoning, every tool call with what it sent and got back, the final answer, and any error. The detail opens as a resizable panel — drag its edge to make it wider — or click its expand button (or a trace’s row directly) for the same view as its own full page. Every id it shows — the member, the project, the conversation — is a link to that item, resolved to a human-readable name with the raw id underneath.

​
A readable name for every trace

A trace is no longer identified only by a raw id — it’s named <workspace-slug>-<n> (for example, genie-demo-142), a short counter unique to your workspace. That name is what you see in the table, the detail page’s title and URL, and what Genie AI uses when it mentions a trace or when you ask it to open one. Renaming your workspace never breaks a link built on this, since only the number is actually resolved — and an old link built on the raw id still opens the same trace.

​
Flaggings

A trace’s detail also shows what else noticed that turn: what the workspace’s PII rules matched on it, what a Guardrail intervened on, and what Governance says about the project it ran against. Each section needs its own permission to view — PII detection, guardrails, or a Governance viewer role — and renders “hidden — needs X” rather than an empty list when you don’t hold it, so an empty section always means nothing fired, never that you can’t see it.

​
Blocked turns

A message that Guardrails or a PII rule refuses now shows up in Tracing as a blocked turn — which rule blocked it, and why — instead of vanishing without a trace. It’s not counted as a failure (blocking a message on purpose isn’t an outage), and a PII-blocked turn only ever stores the already-masked message, never what was actually typed.

​
Imported traces from LiteLLM and Langdock

Tracing can also hold traces from tools outside Genie, so calls made through your LiteLLM proxy or your Langdock workspace sit next to Genie AI’s own turns. Open Tracing and use the three tabs: Genie AI, Imported, and Integrations.
  • LiteLLM — on Integrations, enter your proxy’s URL (self-hosted or hosted) and an API key. Genie tests the connection when you save, imports your spend logs when you press Sync now, and then syncs again every hour. A proxy admin key imports every request; a regular user’s key imports only that user’s. Disconnecting keeps what was already imported.
  • Langdock — export your usage from Langdock and drop the file on the Langdock card (CSV, TXT, LOG, JSON, or JSON lines, up to 4 MB). Uploading the same file twice adds nothing.
The Imported tab lists each trace with its time, source, status, model, user, tokens, cost, and duration. It can look back up to 12 months, filter by source and status, and load older entries. Open one to see the full request and response and every field the source sent, including ones Genie has no column for. Very long texts are shortened, and the detail says so.
Viewing imported traces needs the same See Genie AI traces permission. Connecting, syncing, uploading, or disconnecting also needs the Manage integrations permission. Costs are shown in the source’s own currency (LiteLLM reports US dollars), not Genie credits.
Imported traces contain text that other people sent through your proxy. Genie AI treats it as untrusted data and never follows instructions found inside it.

​
Manage Tracing from workspace chat

Ask the Genie workspace AI in plain language:
  • “Which Genie AI turns failed in this workspace this week?”
  • “Open trace [id]”
  • “How many tokens did we use yesterday?”
  • “Sync my LiteLLM traces now” or “Import this log as Langdock traces”
For safety, Genie AI never asks for your LiteLLM API key or changes its URL — do that on the Integrations tab.
Every member already has access to their own past conversations via the Genie MCP Server. Tracing — and its matching MCP tools — is the workspace-wide, admin view across every member’s turns.

Guardrails

Control what Genie AI will discuss in your workspace.

Governance

Review projects and enforce compliance rules.

Genie MCP Server

Manage your workspace programmatically from any AI client.

Members and roles

Grant the tracing permission to a custom role.