Skip to main content
Admin › Monitoring › Conversation Logs
Conversation Logs are records that lay out each individual conversation (request) as a single row as it happened in the system. Where Usage aggregates and summarizes tokens and cost, Conversation Logs let you inspect “who · which agent/model · when · how many tokens” at the level of a single request. They are the source rows behind the numbers you see in the usage charts.
Conversation Logs screen — filter bar, statistics cards (total requests, total tokens, user count, model count), log table with time, user, model, agent, source, platform, input, output, and total columns
Conversation Logs include actual user names and emails. Only admins with access permission can view them.

​
Statistics Summary

The top of the screen shows aggregate cards based on the current period and filters.
MetricMeaning
Total requestsNumber of requests matching the conditions
Total tokensSum of input + output tokens
User countNumber of distinct users who made requests
Model countNumber of distinct models used

​
Log Entry Structure

Each row is a single request. The table consists of the following columns.
ColumnDescription
TimeWhen the request occurred
UserRequesting user (name, email)
ModelModel used for the response (e.g., google/gemini-3-flash-preview)
AgentAgent the request went through (when applicable)
SourceRequest source type — general chat (Chat), agent (Agent), code gateway (Code), API
PlatformClient the request came from (e.g., Web)
InputInput (prompt) tokens
OutputOutput (response) tokens
TotalSum of input + output tokens

​
Filtering and Viewing

FilterDescription
PeriodShared period bar at the top — 1h / 6h / 1d / 7d / 30d / All / Custom
SourceAll sources or only a specific source (general chat · agent · code gateway · API)
ModelAll models or only a specific model
UserSearch and select by user name
Only items that actually have conversation records appear as candidates in the source, model, and user filters.
If there are many rows, navigate pages at the bottom (default 50 per page).

​
Difference from Usage

Conversation Logs view the same token data as Usage, but the unit you look at differs.
AspectUsageConversation Logs
UnitAggregated by period, model, userA single request
FormCharts, totalsRow-level table
Main useToken/cost trends, identifying top users/modelsTracing individual requests of a specific user, model, or agent
When you spot an anomaly in Usage (e.g., a token spike for a specific user or model), you filter Conversation Logs by the same user or model to drill down to the source request level and check — they’re used together in that flow.

​
Use Cases

  1. Enter a name in the User filter to view only that user
  2. Narrow the Period to find requests at the point you want to check
  3. Use Model, Agent, and Total tokens to identify which requests consumed the most tokens
  1. Select a high-priced model with the Model filter
  2. Look at rows with large Total tokens to find token-heavy requests
  3. Compare against the overall trend for the same model in Usage
  1. Use the Source filter to see only agent or code gateway requests
  2. Use the Agent column to check which agents are called
  3. Use the Platform column to see which client the requests come from
  • Aggregate trends: Usage — summarizes tokens and cost by period, model, and user
  • Activity audit: Audit Logs — records resource changes, sign-ins, and other activity
  • Retention period: Accumulated logs are cleaned up per the Data Retention setting