Model Logs
The Model Logs tab displays detailed logs of individual AI model responses, providing visibility into performance metrics, token usage, execution steps, and generated artifacts. This tab is useful for debugging model behavior, monitoring response quality, and tracking resource consumption.
Filters
The filter panel at the top of the tab provides three filter controls arranged in a grid:
| Filter | Description |
|---|---|
| Date Range | Start and end date pickers with quick-select preset buttons for common ranges (e.g., last 7 days, last 30 days). Defaults to the last 7 days. |
| Model | Dropdown to filter by a specific model (All Models, GPT-4, GPT-3.5 Turbo, Claude 3 Opus, Claude 3 Sonnet) |
| Search | Free-text search input to filter logs by content |
A Refresh button in the header reloads the log data with the current filters applied.
Log Entry Fields
Each log entry is displayed as a card with two rows of information:
Primary Row
| Field | Description |
|---|---|
| Model | The name of the AI model used for the response |
| Timestamp | When the response was generated (formatted as YYYY-MM-DD HH:mm:ss) |
| Response Time | Total response time in milliseconds |
| Token Usage | Input and output token counts (e.g., "1,234 in / 567 out") |
Secondary Row
| Field | Description |
|---|---|
| Context | Number of attached files and message history length |
| Execution Steps | Count of completed and failed execution steps |
Artifacts
If the model response produced artifacts, they are listed below the secondary row with:
- Total artifact count
- Each artifact's type and a preview of its content (first 100 characters)
Pagination
The log list supports pagination with controls at the bottom:
| Control | Description |
|---|---|
| Previous / Next | Navigate between pages |
| Page indicator | Shows current page number and total pages |
| Items per page | Radio buttons to select 10, 25, or 50 items per page |
| Total Logs | Displays the total number of logs matching the current filters |
Logs are sorted by timestamp in descending order (newest first).
Empty State
When no logs match the current filter criteria, a message reads "No logs found for the selected filters."
Best Practices
- Start with a narrow date range (last 7 days) and expand if needed to avoid loading excessive data.
- Use the model filter to isolate performance comparisons between different AI models.
- Monitor response times and token usage to identify unusual spikes or degradation.
- Check execution step failure counts to identify reliability issues with specific model workflows.
Related Articles
- Metrics - Model and event metrics analytics
- Admin Dashboard Overview - Navigation and layout