> ## Documentation Index
> Fetch the complete documentation index at: https://koreai.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Workspace analytics

Monitor agent performance, sessions, request-level traces, and individual LLM generations across your workspace.

**Workspace Analytics** gives you visibility into how agents behave in production — from aggregate metrics to individual session transcripts and step-level execution logs.

* **Navigation**: Settings > Analytics
* **Required role**: Owner, Admin, or Operator; Member for project-scoped views.

Use the **All Projects** dropdown and time range controls (24h, 7d, 30d, 90d) to filter data across all tabs.

***

## Agents

The **Agents** tab shows aggregate performance metrics for all agents in the selected project and time range.

<Note>Agent performance metrics appear once agents start processing sessions.</Note>

### Metrics

| Metric | Description |
| - | - |
| Total sessions | Number of agent sessions in the selected time range. |
| Avg. session duration | Mean time from session start to last message. |
| Resolution rate | Percentage of sessions that reached a successful outcome. |
| Avg. messages per session | Mean number of user and agent messages per session. |
| Total tokens consumed | Input and output tokens across all models. |
| Total estimated cost | Calculated LLM cost for the period. |
| Error rate | Percentage of sessions that encountered errors. |

Filter by date range, project, agent, or model. Charts show session volume over time, token usage, cost trends, top agents by session count and cost, and error breakdown.

***

## Sessions

The **Sessions** tab lists individual user sessions across all agents in the selected project and time range.

<Note>Session data appears once agents start processing requests.</Note>

### Browse sessions

1. Go to **Settings** > **Analytics** > **Session Explorer**.
2. Search by session ID, user message content, or agent name.
3. Filter by status, date range, or agent.
4. Click a session to view the conversation transcript, tool calls, model usage, state transitions, and metadata.

***

## Traces

The **Traces** tab provides a step-by-step execution log of agent runs. It offers two views: **Event Stream** and **SQL Query**.

<Note>Trace events appear once agents start processing sessions.</Note>

### Event stream

The **Event Stream** view shows a chronological log of all agent events in the selected project and time range.

Each trace records a span tree — a hierarchical view of all operations:

| Event type | What it captures |
| - | - |
| LLM calls | Prompt, response, tokens, and latency. |
| Tool executions | Name, input, output, and duration. |
| Step transitions | Flow step changes for agents with a FLOW section. |
| Guardrail evaluations | Category, score, and decision. |
| Knowledge base queries | Query text, retrieved chunks, and relevance scores. |

Filter events by type:

| Filter | Description |
| - | - |
| All | Show all event types. |
| LLM | LLM call events. |
| Tool | Tool invocation events. |
| Decision | Agent decision and routing events. |
| Error | Events that resulted in an error. |
| Handoff | Agent handoff and delegation events. |
| Agent | Agent lifecycle events. |
| Session | Session start and end events. |

Use the search bar to find events by session ID, agent name, or event type. The total event count is shown next to the search bar.

**Trace search syntax:**

| Operator | Example | Description |
| - | - | - |
| `agent:` | `agent:customer-support` | Filter by agent name. |
| `status:` | `status:error` | Filter by outcome. |
| `model:` | `model:claude-4-sonnet` | Filter by model used. |
| `duration:>` | `duration:>2s` | Filter by total duration. |
| `tokens:>` | `tokens:>5000` | Filter by token count. |

### SQL query

The **SQL Query** view lets you run custom queries against trace event data.

<Note>Admin access is required to use the SQL Query view.</Note>

| Control | Description |
| - | - |
| Example Queries | A dropdown of pre-built queries to help you get started. |
| SQL editor | Write or paste a SQL query. Use `{tenantId:String}` and `{projectId:String}` for isolation. |
| Clear | Clear the current query from the editor. |
| Execute | Run the query and view results. |

***

## Generations

The **Generations** tab lists individual LLM calls across all agents in the selected project and time range, with token, latency, and cost details for each call.

<Note>Generation data appears once agents start making LLM calls.</Note>

### Filtering

Generations can be filtered at two levels:

**1. Top-level filters** (apply to the whole list):

| Filter | Behavior |
| - | - |
| Project | Single-select. |
| Environment | Multi-select. |
| Channel | Multi-select. |
| Time range | Presets only: 24h, 7d, 30d, 90d. |
| Search | Full-text search with search-as-you-type. |

**2. Advanced (per-column) filters** - refine the top-level results further. Click **Filters** to add one or more conditions:

1. Click **+ Add filter**.
2. Choose a field - Model, Name, Status, Status Code, Channel Type, Source, Source Subtype, Source ID, and others.
3. Choose an operator (for example: **is**) and a value.
4. Click **Apply Filters** to run the query, or **Clear all** to remove every condition.

**Columns**

| Column | Description |
| - | - |
| Model | The LLM model used for the call. |
| Name | Name of the generation (for example: agent, guardrail evaluation, or action). |
| Status | Outcome of the call (for example: Success). |
| Channel | Channel the request originated from (for example: Web Debug). |
| Source | Origin of the call (for example: Runtime, Runtime Internal, Guardrails). |
| Total Tokens | Combined input and output tokens for the call. |
| Latency | Total time taken for the call to complete. |
| TTFT | Time to first token - latency until the first output token is returned. Populated for streaming calls only; shows "Not applicable" otherwise. |
| Cost | Estimated cost of the call. |
| Start Time | Timestamp when the call started. |

Additional columns - **Session**, **Channel Type**, **Source Subtype**, and **Source ID** - are available but hidden by default.

* Reorder columns by dragging them in the **Customize Columns** sidebar.
* Model is pinned by default.

### Generation payload

Click any row to view the exact request and response, and call metadata. This is the primary place to troubleshoot a specific call - **Event ID** and **Call ID** are the two fields to use when correlating a generation with logs or traces elsewhere.

| Field | Description |
| - | - |
| Event ID | Unique identifier for the trace event. Use to correlate with trace data. |
| Call ID | Unique identifier for the LLM call. Use to correlate with provider-side logs. |
| Session | Session ID the call belongs to. |
| Provider | LLM provider (for example: openai). |
| Input Tokens | Tokens sent in the request. |
| Output Tokens | Tokens returned in the response. |
| Total Tokens | Combined input and output tokens. |
| Latency | Total call duration. |
| TTFT | Time to first token (see Columns above). |
| Status | Outcome of the call. |

The panel has two tabs:

* **Request** - the payload sent to the model.
* **Response** - the JSON response returned by the model, including the generated text and provider metadata.

### Export

Click **Export** to download the current list as a CSV.

<Note>Only the entries visible on the current page are exported (up to 50 rows).</Note>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.