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

# Analytics

The **Analytics** section covers two admin-only screens: the **Platform Analytics** dashboard (usage/cost/ticket metrics across the whole platform) and **Observability** (an embedded LangFuse view for agent traces).

{% hint style="info" %}
This is distinct from [AI Dashboards](/docs/armor/ai-dashboards.md), which are agent-built dashboards over your connected cloud/infra providers. Platform Analytics is a fixed, built-in view over DuploCloud's own usage data — it isn't agent-generated and isn't scoped to a provider.
{% endhint %}

## Platform Analytics Dashboard

Go to **AI Admin → Analytics → Platform Analytics**. The **Overview** tab shows platform-wide totals — users, active users in the last 30 days, groups, tickets, projects, workspaces, providers, skills, and personas.

![Platform Analytics overview](/files/6KeNOCKVCN7K4k5z2FqW)

The remaining tabs break these totals down further:

* **Tickets** — status distribution (Open/In Progress/Closed), top workspaces by ticket volume, and tickets by user

![Tickets tab](/files/vyZZBeGAc6OKv4W2Z5dO)

* **Cost** — total and average cost, and cost broken down by workspace and by user

![Cost tab](/files/Byb5ErIs74lo0fme5irQ)

* **Quotas** — every quota definition, its current spend against its limit, and how many mappings apply it

![Quotas tab](/files/AleW6juSb0TkY1Kwo45r)

* **Projects** — project counts by workspace and by scope

![Projects tab](/files/Rm1P38OvFqJityx7PCrt)

* **Users** — active vs. inactive users (based on login in the last 30 days), plus breakdowns by group and by permission set

![Users tab](/files/mgme1VwXUkXDwP71keRy)

{% hint style="info" %}
Nothing needs to be configured for this dashboard — it's computed from data that already exists (workspaces, tickets, users, quotas, and so on), so it populates automatically as your platform is used.
{% endhint %}

## Observability

Go to **AI Admin → Analytics → Observability → LangFuse**. This page embeds [LangFuse](https://langfuse.com), a third-party, open-source LLM observability tool, so you can inspect detailed agent traces — it isn't hosted or provided by DuploCloud.

To use it, you need your own LangFuse project (LangFuse Cloud or self-hosted) and set its URL as the `langfuse-url` [System Setting](/docs/armor/settings.md#system-settings). Until that's set, the page shows an empty state with a link that jumps straight to the Add System Setting form, pre-filled to `langfuse-url` — save it there and the page embeds that URL directly.

Setting the URL only controls what's *displayed*; it doesn't make trace data appear. For traces to actually reach your LangFuse project, the underlying agent runtime deployment also needs LangFuse API credentials configured — a separate, deployment-level setup step, not something done from this page. Once that's in place, each trace is automatically tagged with the originating ticket, workspace, user, and model, so a trace in LangFuse can be traced back to the exact ticket that produced it.


---

# 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, and the optional `goal` query parameter:

```
GET https://docs.duplocloud.com/docs/armor/analytics.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.