FETCH HIVE
Get StartedBook a Demo
  • 👋Welcome
  • Getting Started
    • Prompt Quick Start
    • Workflow Quick Start
  • Agent Quick Start
  • 💬Running Prompts
    • Run with API
  • 🚀Building Workflows
    • Workflow Steps
      • AI
        • Prompt
        • Agent
      • Web Research
        • Google Search
        • Google News
        • Bing Search
        • Exa Search
        • Exa Similar
        • Website Scrape
      • Utility
        • Call API
        • Format JSON
      • Files
        • Document Upload to Text
        • Document URL to Text
  • Testing and Iteration
  • Publishing and Versioning
  • Error Handling
  • 🚀Running Workflows
    • Run with API
  • Retrieve a Workflow
  • 🤖AGENTS
    • Build an Agent
    • Send a Message
    • API
      • Create an Agent
      • Retrieve an Agent
      • Delete an Agent
      • Chats
        • Retrieve a Chat
        • Create a Chat
        • Update a Chat
        • Delete a Chat
        • Clear Chat Messages
      • Messages
        • List Messages
  • 💾Datasets
    • Build a Dataset
    • Test a Dataset
    • API
      • Retrieve a Dataset
      • Create a Dataset
      • Update a Dataset
      • Delete a Dataset
      • Dataset Items
        • Retrieve a Dataset Item
        • Create a Dataset Item
        • Update a Dataset Item
        • Delete a Dataset Item
        • Regenerate a Dataset Item
  • 🏢Your Workspace
    • Brand Kit
  • Settings
  • Use your own API keys
  • Team Members
  • 🔍Monitoring
    • Credit Usage
    • Analytics
    • Log History
  • 📚Resources
    • Discord
    • Changelog
  • Roadmap
  • Book a Demo
  • Get in Contact
  • Security and Compliance
Powered by GitBook
On this page
  • Overview
  • Available Log Types
  • Log Details
  • Common Fields
  • AI-Specific Fields
  • Step-Specific Data
  • Using Log History
  • Debugging and Troubleshooting
  • Performance Optimization
  • Testing and Iteration
  • Usage Analytics
  • Viewing Logs
  • Best Practices

Was this helpful?

  1. Monitoring

Log History

Monitor your Fetch Hive interactions with log history

PreviousAnalyticsNextDiscord

Last updated 2 months ago

Was this helpful?

Overview

Log history in Fetch Hive provides comprehensive insights into all interactions across your workspace. Whether you're debugging issues, optimizing performance, or analyzing usage patterns, the log history gives you detailed information about every operation performed within the platform.

Available Log Types

You can access logs for the following resources:

  • Prompts: View all executions of your AI prompts

  • Endpoints: Track usage of both Prompt and Workflow endpoints

  • Workflows: View all executions of your Workflow steps

  • Datasets: Monitor dataset operations and updates

  • Agents: Review agent interactions and responses

  • Fine Tuning: Track fine-tuning job progress and results

Log Details

Each log entry provides extensive information about the interaction, including:

Common Fields

  • Output: The result or response from the interaction

  • Inputs: Parameters and data provided to trigger the interaction

  • Credit Usage: Amount of credits consumed

  • Duration: Time taken to complete the operation

  • Provider: The service provider used (e.g., Exa, Google Search, OpenAI, Claude)

  • Owner: User who initiated the interaction

  • Status: Current state of the operation (e.g., Completed, Error, Running)

  • Timestamp: When the interaction occurred

AI-Specific Fields

For AI Prompt Steps or Prompts, additional information includes:

  • Model: The specific AI model used

  • Tokens: Number of tokens consumed

  • LLM Charge: Cost associated with the language model usage

Step-Specific Data

Workflow steps may include additional custom data fields depending on the step type, providing deeper insights into the operation.

Using Log History

Debugging and Troubleshooting

  • Identify failed operations and their error messages

  • Review input parameters that led to specific outcomes

  • Track the sequence of events in complex workflows

Performance Optimization

  • Monitor response times and resource usage

  • Analyze token consumption patterns

  • Identify opportunities for cost optimization

Testing and Iteration

Log history is invaluable for:

  • Comparing different versions of prompts or workflows

  • Understanding which approaches yield better results

  • Fine-tuning parameters based on historical performance

  • Validating changes before deploying to production

Usage Analytics

  • Track usage patterns across different resources

  • Monitor credit consumption by resource type

  • Analyze user engagement and adoption

Viewing Logs

  1. Navigate to the respective resource section (Prompts, Endpoints, Datasets, etc.)

  2. Click Activity Logs in the top right of the navbar

Best Practices

  1. Regular Monitoring: Review logs periodically to catch issues early

  2. Performance Tracking: Use log data to optimize resource usage

  3. Documentation: Reference logs when documenting successful patterns

  4. Iteration: Use historical data to inform improvements

  5. Cost Management: Monitor credit usage to optimize expenses

🔍
Viewing activity log history
Accessing activity logs for Workflows