Skip to main content
Use Fetch Hive analytics when you want a workspace-level view of cost, token usage, trace performance, and the users driving activity.

​
Overview

The main analytics view in Fetch Hive lives under Dashboard. It gives you a shared monitoring surface for spend, service mix, model mix, model reliability, trace performance, token usage, and top users over a selected time range. This page is different from the dedicated Users analytics view. Dashboard analytics is the wider workspace report, while the Users section focuses on tracked end-user activity.

​
How do I open workspace analytics?

Open Dashboard in the main sidebar, then click Analytics in the secondary navigation. Fetch Hive loads the analytics cards and charts for your current workspace. Switching workspace changes the analytics totals and charts to that workspace’s data.

​
What metrics and charts are available?

The analytics page currently shows eight monitoring panels:
  • Total Cost for workspace spend over the selected period
  • Service Costs for the mix of services that generated cost
  • Model Costs for LLM and image-generation model usage and spend
  • Model Observability for model latency percentiles and error rate
  • Trace Performance for run latency, span bottlenecks, and tool usage
  • Token Usage with totals for input, cached, reasoning, citation, image, and output tokens
  • Cache usage for prompt-cache hit rate and the dollar difference between the cached price, the uncached price, and the amount saved
  • Top Users so you can rank tracked users by activity
Use Service Costs when you want to see which services contribute to spend. Use Model Costs when you want to compare LLM and image-generation model usage, token volume, and cost in one place. Use Model Observability when you want to compare model latency and failure rate across prompt calls, agent calls, workflow prompt-step calls, and image-generation model calls. Use Trace Performance when you want to compare timed trace span groups, slow timed reasoning models, slow timed tools, slow timed workflow tools called by agents, and average tool count per run. Trace timing is observed from Fetch Hive’s platform boundary, so provider spans show Fetch Hive-observed round-trip or stream-phase timing rather than provider-internal telemetry. Structural tool markers without provider timing still count as tool usage, but they are excluded from duration shares and slow-tool rankings. Where analytics split cost into Task credits and Wallet, task credits are an estimated platform cost based on included plan tasks or purchased top-up tasks. Wallet is the hosted LLM wallet portion. Open Show all from Model Costs when you need the full model-cost table for the selected date range. Use Token Usage when you want to inspect how token volume is split across input, cached, reasoning, citation, image, and output tokens. Image tokens include image-input tokens and generated-image output tokens when the provider returns token usage. Use Cache usage when you want to see how much prompt caching changed token cost. The card compares the uncached price, the cached price, and the amount saved. Token hit rate is cache-read tokens divided by cache reads, cache writes, and uncached input. The dollar figure re-prices those tokens at the regular input rate; cache writes can cost more than regular input, so the total can be negative. This is cache pricing, not a Fetch Hive optimization total. If the workspace had no cached-token traffic in the selected range, the card shows no data for this period instead of $0.00 saved. In Top Users, you can switch between Cost and Requests.

​
How do I change the reporting window?

Use the date-range control in the header to switch between the preset ranges or choose a custom range. When you apply a new range, Fetch Hive refreshes every analytics panel for that period. The selected range stays in the address bar, so it is kept when you open Model Costs, Model Observability, or Trace Performance, and when you return to the analytics dashboard.

​
How do I drill into a user from analytics?

Use Top Users when you want to move from a workspace report into a specific tracked user. Click a user in the chart to open that user’s detail page under Users. From there, you can inspect that user’s activity and open the underlying prompt, workflow, or agent run details.

​
Analytics vs user tracking

Use this page when your question starts at the workspace level, such as:
  • Which services are driving cost?
  • Which models are responsible for the most spend?
  • Which models are slow or failing most often?
  • Which trace span types or tools are slowing down runs?
  • How much token volume did this workspace generate?
  • How much did prompt caching change provider token cost?
Use the Users section when your question starts with a specific tracked end user or a user activity trend. See also: User tracking analytics.