Logs
Review agent runs, filter activity, inspect traces, and debug tool usage in Fetch Hive
Use agent logs to inspect what happened after an agent run starts. In Fetch Hive, this is the main place to review run status, model usage, tool activity, cost, and trace timing outside the editor.
Overview
Agent logs live under Logs in the agents section. The page centers on a table of runs. When you click a row, Fetch Hive opens a run detail sheet with summary metrics and trace data.
This page covers logged runs, not the temporary test conversation in Chat. Use Chat in the editor to iterate on behavior, then use Logs to inspect runs after the fact.
How do I open agent logs?
Open Agents in the sidebar.
Click Logs in the agents section menu.
Fetch Hive opens the agent logs table. On this page, the agents sidebar does not show the Categories group, and it does not add the Source filter pattern used in prompt and workflow logs.
What's tracked in the agent logs table?
The main logs table shows summary fields for each run, including:
Completed At
Name
Model
Tools
Status
Total Tokens
Total Cost
Duration
API Key
Collaborator
The Tools column shows the tool sources involved in the run. Depending on the run, this can include Google Search, GPT Search, Vector Search, or SERP.
How do I filter agent logs?
Use the date range control in the header to pick a custom range or a preset such as Last 1 Day, Last 7 Days, Last 30 Days, or Last 90 Days.
Use Provider, Model, and API keys to narrow the table to the runs you care about.
Click Clear filters when you want to reset the active filter state.
Use Columns when you want to hide or restore table columns.
How do I inspect an agent run?
Click a row in the logs table.
Review the run detail sheet that opens on the right.
The sheet header shows the request ID when it is available, or the run ID as a fallback. It also shows the run status, agent name, and started time.
The summary strip below the header shows the run's Provider / Model, Agent, Duration, Tokens, Credits, Cost, Tool Calls, Owner, and Charge Type.
If the agent still exists and is not archived, the agent name in the summary strip links back to the editor.
Traces
Use the trace waterfall on the left side of the run detail sheet to understand how the run progressed over time.
When you select a span, the right side updates to show the details for that part of the run. Depending on the span, this can include:
model response data
request details
metadata
tool input
tool response
token and cost details
When the selected span is linked to a tool completion, Fetch Hive shows the tool-specific panels for Response and Input. When it is linked to the main model completion, Fetch Hive shows the response and request sections for that completion instead.
This is the main debugging view for agent runs. Start here when you need to understand whether the agent responded directly, reasoned first, called a tool, or slowed down on a specific step.
Notes
Agent logs do not include the Source filter pattern used in prompt and workflow logs.
This page does not expose a separate analytics or export view for agents.
Use Run with API when you want to invoke an agent from your own app, and use Testing with Chat when you want to iterate inside the editor.
Last updated