> ## Documentation Index
> Fetch the complete documentation index at: https://docs.noxus.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Overview

> How metrics are collected across flows, agents, and knowledge bases, and where to access them

Noxus automatically collects metrics for every building block on the platform — flows, agents, and knowledge bases. No configuration is required: every execution, conversation, and document ingestion is tracked and made available through both the in-app dashboards and the REST API.

## What's measured

<CardGroup cols={3}>
  <Card title="Flows" icon="workflow">
    Every flow execution is tracked: run count, duration, error rate, AI model usage, token consumption, and cost — broken down by user, trigger source, and node.
  </Card>

  <Card title="Agents" icon="message-square">
    Every conversation and message is counted. Analytics include active users, messages per conversation, and full LLM cost breakdowns by model and user.
  </Card>

  <Card title="Knowledge Bases" icon="book-open">
    Every document upload and ingestion job is tracked: total documents, processing status (succeeded/failed), file types, and contributor activity.
  </Card>
</CardGroup>

<Note>
  The metrics also include extensive AI model analytics — covering LLM and embedding model usage, token consumption, estimated costs per model, and how that usage breaks down across flows, agents, nodes, and users.
</Note>

***

## Where to access analytics

### Resource-level analytics

Each individual resource has its own **Analytics** tab. Open any flow, agent, or knowledge base and click the **Analytics** tab in the top navigation to view metrics scoped to that resource.

<AccordionGroup>
  <Accordion title="Flow analytics" icon="workflow">
    Navigate to a flow and click the **Analytics** tab. Available metrics include:

    * Total runs (manual, triggered, agent-initiated)
    * Active and currently running flows
    * Error rate and error distribution over time
    * Average run time with percentile breakdown
    * Token and cost usage by model, node, and user
    * Run distribution by source type over time
  </Accordion>

  <Accordion title="Agent analytics" icon="message-square">
    Navigate to an agent (co-worker) and click the **Analytics** tab. Available metrics include:

    * Conversations started and messages sent
    * Average messages per conversation
    * Active users
    * Conversation volume over time
    * LLM token and cost breakdown by model and user
  </Accordion>

  <Accordion title="Knowledge base analytics" icon="book-open">
    Navigate to a knowledge base and click the **Analytics** tab. Available metrics include:

    * Total documents and processing status
    * Document ingestion over time
    * Documents by knowledge base, user, and file type
    * Contributor activity
  </Accordion>
</AccordionGroup>

### Workspace-level analytics

To see aggregated metrics across all resources in a workspace, navigate to **Settings → Analytics**. This view combines flow runs, agent conversations, knowledge base activity, API usage, and AI model costs into a single cross-resource dashboard.

<Note>
  Workspace analytics are scoped to the workspace you are currently in. Switch workspaces from the workspace selector to view analytics for a different workspace.
</Note>

### Billing analytics

Usage against your plan quotas is tracked separately. Navigate to **Settings → Billing → Analytics** to view:

* AI operations consumed vs. your plan limit
* Operations over time
* Usage per workspace (for tenant admins)
* Model token consumption and associated costs

<Info>
  Billing analytics reflect the constraints defined on your subscription. Contact your administrator if you need to review or adjust quota limits.
</Info>

***

## Accessing analytics programmatically

All of the metrics available in the in-app dashboards can also be retrieved via the REST API, using the same API key you use for workflows and conversations. See [Analytics API](/platform/analytics-api/overview) for the full endpoint reference and available metrics.