> For the complete documentation index, see [llms.txt](https://docs.fetchhive.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fetchhive.com/monitoring/analytics.md).

# Analytics

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? <a href="#open-workspace-analytics" id="open-workspace-analytics"></a>

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? <a href="#available-metrics-and-charts" id="available-metrics-and-charts"></a>

The analytics page currently shows seven 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
* **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, 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.

In **Top Users**, you can switch between **Cost** and **Requests**.

## How do I change the reporting window? <a href="#change-reporting-window" id="change-reporting-window"></a>

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.

## How do I drill into a user from analytics? <a href="#drill-into-user" id="drill-into-user"></a>

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?

Use the **Users** section when your question starts with a specific tracked end user or a user activity trend.

See also: [User tracking analytics](/user-tracking/analytics.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.fetchhive.com/monitoring/analytics.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.