Overview
Analytics provides a history of all administrative tasks through two views: the Dashboard view and the Data view. Switch between them using the toggle at the top right of the Analytics page. The views display key performance metrics, trends, and reports, enabling you to gauge real-time usage and performance.
Dashboard View
The Dashboard view provides graphical reports on usage, performance, and feedback. At the top, you can see the total queries, total tokens, and total active users for the day.
All graphical reports support Day, Week, and Month views with left-right navigation for detailed metrics at each time point. Time averaging: 30-minute average (daily), 6-hour average (weekly), daily average (monthly).
Tokens Used
Displays token usage trends across models.

Tokens Per Agent
Displays token consumption broken down by agent.

Queries Per Agent
Displays query volume by agent, categorized by agent type: AI for Service, GPT, Data, Search, and Workflow.

Top Agents
Displays agents ranked by query volume in descending order.
Top Users
Displays the top 10 users by query count.
Users
Displays unique users interacting with the system, comparing web vs. native platforms.

Average Response Time
Displays the average response time of the service over time.

Errors
Displays the number of queries that resulted in errors over time.

Feedback
Displays end-user feedback on responses.
Trace Logs
Trace logs record how the platform processed each user query, from request to response. Each record maps to one user query. Use trace logs to investigate a response, review what a query cost, and see which source answered it. Navigation: Admin Console → Usage → Trace logsFind a Trace Log
The Trace logs page lists records for the selected time range, newest first.
Use the following options to narrow the list:
Record Details
Select More on a record to open its detail panel. Summary The top of the panel shows the outcome of the request:
Request fields
Every record shows the following fields, whatever the source:
Source fields
The value of Source decides which fields follow it. Each source adds a type, an ID, and a name:
For Enterprise Search records:
- Queries that use exclusive search log Enterprise Search as the source.
- KnowledgeBases ID lists only the knowledge bases in scope for that query, not every knowledge base in the search application.
- When the search runs on the XO Platform, KnowledgeBases ID contains a single ID, and KnowledgeBases name shows the bot name.
- Trace ID of the step
- Request: the prompt or payload that the platform sent
- Response: what the step returned
- Response time of the step
Trace Log API
Retrieve trace log records programmatically through the Trace Log API to pull them into your own reporting tools, data warehouses, or dashboards. For the endpoint, parameters, and response reference, see Trace Log API.Feedback Management
Feedback Management gives administrators visibility into user feedback submitted across the platform, with configurable email notifications and scoped access by role. Navigation: Admin Console → Usage → FeedbackAccessing the Feedback Page
Access to the Feedback page is role-based:Feedback Detail View
Click any feedback entry to open its detail view. The view displays the associated trace log and the submitted feedback — type, category, and any additional comments.Notify Feedback
Click Notify Feedback on the Feedback page to configure email notifications. Select which feedback types should trigger notifications and add recipients. Recipients can be any valid email address or distribution list and do not need to belong to the account. Notification scope follows the level at which it is configured — account-level covers all workspaces and agents, workspace-level covers all agents in that workspace, and agent-level covers only that specific agent. Email notifications include: user email, query, agent name, workspace, feedback type, feedback category, and additional comments (if provided).Model Spendings
The Model Spendings page shows how much your account spends on LLM usage, in US dollars, for a selected month. Navigation: Admin Console → Usage → Model Spendings Use the month selector at the top of the page to choose a month. The page opens on the current month, and every widget reflects the month you select. For the current month, the widgets show month-to-date figures.
How the platform calculates spend
The platform calculates spend for each trace from the LLM model that the trace used and the tokens it consumed. It prices input and output tokens separately when the model prices them differently, and applies the current per-token rate for that model. Every dollar figure on the Spend and Rate Limits pages comes from this calculation.
Model Spendings does not include Amazon Bedrock usage, embedding model usage, or container creation.
Rate Limits
Rate Limits control LLM usage by dollar amount. Set a budget for the account, group users into profiles that share a pool, and limit how much each user can spend in a day, week, or month. Navigation: Admin Console → Usage → Rate LimitsTurn On Rate Limits
Use the toggle at the top of the Rate Limits page to turn rate limits on or off for the account.
The top of the page also shows the total budget across all profiles, converted to a monthly amount. The total updates whenever you change a profile pool limit or its time window.
Profiles
A profile groups users who share a pool limit.- Every account includes an All users profile that you cannot delete. New users join All users unless you assign them to another profile.
- Create a custom profile with New Profile. Enter a name, set its pool limit and per-user limit, and add users.
- A user belongs to one profile at a time. Adding a user to a profile removes the user from the previous profile.
- Open the profile and select the option to add users.
- Search for users and select them, or import a file that lists the users. The popup shows the current profile of each user.
- Select Add.
Pool and Per-User Limits
Each profile sets its own time windows for the pool limit and the per-user limit. The platform measures consumption within calendar windows, not rolling windows:
The platform counts all consumption in the current window, even when you set a limit partway through it. When you change the time window, the platform converts the amount: a daily amount multiplies by 7 for a week and by 30 for a month, and the reverse applies when you shorten the window. You cannot set a limit to zero.
Confirmations and warnings
The platform asks you to confirm changes that affect users immediately, including when you:
- Change a daily limit to a weekly or monthly limit, which increases the effective budget.
- Set a limit below the amount that users already spent in the current window.
- Set per-user limits that together exceed the pool, or a per-user limit larger than the whole pool.
- Use different time windows for the pool and the per-user limit.
- Turn off the per-user limit or turn off rate limits for the account.
- Delete a profile that has users. The users return to All users, and their limits change immediately.
Monitor Usage
The Usage panel of a profile lists its users and their consumption for the current window. When the pool limit and the per-user limit use different time windows, the panel shows a consumption column for each window. Select View all user usage to open the Manage users usage popup. The popup has a tab for each profile and an All users tab. The All users tab lists every user in the account with a Profile column. Select a user in any tab to open that user’s trace logs for the applicable time window.Add Extra Budget
When a user reaches the per-user limit, you can add extra budget from that user’s row.- The extra amount applies to the current time window only. At the next window boundary, the limit returns to the configured amount.
- You can add extra budget more than once in the same window. The amounts add up.
- The user can send requests again immediately, as long as the profile pool has budget left. If the pool is also exhausted, the platform tells you that the extra budget does not unblock the user.
End-User Experience
Usage alerts: When users cross 50%, 75%, 90%, and 95% of their limit, an alert appears below the compose bar. Users can dismiss the alert, and it reappears after a page refresh or in a new session. Usage screen: Users can view their own usage at any time. The screen shows:- Personal consumption for the configured time window and when it resets. Users see their consumption even when no per-user limit applies.
- The profile pool total, the pool consumption, and when the pool resets.
- A bar graph of consumption, with a daily view for the last 30 days and a weekly view for the current month.
- Spend by agent for the month, with the top 10 agents and a View all option.