Skip to main content
Knowledge base logs show processing activity for knowledge base items. Use them to review custom text, document upload, and website scrape runs after content is processed.

​
Overview

Knowledge base logs live under Logs in the knowledge bases section menu. The page centers on a paginated table of runs. Click a row to open the run detail sheet and inspect the selected run. This page covers item processing logs. For search testing, use Testing a Knowledge Base.

​
How do I open knowledge base logs?

  1. Open Knowledge Bases from the sidebar.
  2. Click Logs in the knowledge bases section menu.
Fetch Hive opens the knowledge base logs table.

​
What’s tracked in the logs table?

The main logs table shows summary fields for each processing run, including:
  • Started
  • Knowledge Base
  • Item
  • Type
  • Status
  • Total Tokens
  • Total Cost
  • Duration
  • API Key
  • Collaborator
The Type column shows whether the run processed Custom, Document, or Website content. The Status column shows whether the run is pending, running, completed, or failed.

​
How do I filter knowledge base logs?

Use the date range control in the header to choose the time window you want to inspect. Use Knowledge Base to filter the table to one knowledge base. Use API Keys to filter runs by the API key associated with the run. Use the Type section in the sidebar to filter by:
  • All Types
  • Custom
  • Document
  • Website
Click Clear filters when you want to reset active table filters. Use Columns when you want to hide or restore table columns.

​
How do I inspect a processing run?

Click a row in the logs table. Fetch Hive opens the run detail sheet. The sheet shows the run status, request details, cost and token usage, related completions, and any error message for a failed run. When trace data is available, the detail sheet includes a waterfall timeline for the processing run. Select spans such as document loading, website scraping, PII removal, chunking, or embedding to inspect timing, metadata, request details, and related completion output. If the related knowledge base or item still exists, the detail sheet links back to that knowledge base or item editor. Use the detail sheet when you need to understand why processing failed, which step took time, how many tokens it used, or which item generated the run.

​
Notes

  • Logs are for processing runs, not every search query.
  • Date range availability can depend on your workspace plan.
  • Document uploads can also appear in the Media library as account assets.
  • Workflow writes can create knowledge base items. See Write to Knowledge Base for the workflow path.