> For the complete documentation index, see [llms.txt](https://docs.uptiq.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.uptiq.ai/governance/observability.md).
# Observability
See how published apps and agents are used, and how teams build on the platform. Start here to understand adoption, volume, and outcomes before investigating quality or low-level calls.
{% columns %}
{% column %}
#### Understand adoption
Measure published-app engagement and account-wide build activity.
{% endcolumn %}
{% column %}
#### Investigate agent outcomes
Review conversation threads, durations, and execution status.
{% endcolumn %}
{% endcolumns %}
#### At a glance
| Area | Use it to | Start here |
| ---------------------- | --------------------------------------- | ----------------------------------------- |
| **App Analytics** | Track end-user engagement | [App Analytics](#app-analytics) |
| **Platform Analytics** | Track app and agent build activity | [Platform Analytics](#platform-analytics) |
| **Agent Analytics** | Review individual conversation outcomes | [Agent Analytics](#agent-analytics) |
Analytics is account-wide. You can filter by workspace. **App Analytics** and **Agent Analytics** also support date-range filters.
## App Analytics
App Analytics reports usage and engagement across the apps you've published. Open it from **Observability → App Analytics**.
App Analytics, reporting usage across published apps.
You can narrow the view to a workspace or a date range, search for a single app, and reload at any time.
For the selected period, App Analytics reports your **Unique Visitors** — the distinct people who used your apps — your **Total Page Views**, and how many **Published Apps** you have live across all environments. Each figure has a short definition on hover.
It then shows how that usage moves and where it comes from: unique visitors over time, the browsers your visitors used, and how visitors split across your apps by percentage.
Finally, each published app is listed with its **Visitors** and **Pageviews** for the period, shown under its subdomain — for example, `document-insight-ai-builderqa-352042.qa.withuptiq.app`.
## Platform Analytics
Platform Analytics reports account-wide build activity, adoption, and spend — how much is being *built* on the platform, rather than how end users engage with finished apps. Open it from **Observability → Platform Analytics**.
Platform Analytics has two parts.
* **App Events** covers the app build lifecycle — **Apps Created**, **Build Started**, **Build Completed**, and **Project Published** — with an **App build funnel** that shows the same stages as proportions. Wherever a stage has records behind it, a **View records** link takes you to the underlying list.
* **Agent Events** covers the agent lifecycle — **Agents Created**, **Build Started**, **Build Completed**, **Runs Initiated**, and **Agent Mapped** — with an **Agent build funnel** and an event-count breakdown alongside. As with App Events, stages that have records offer a **View records** link.
## Agent Analytics
Agent Analytics reports conversation volume, quality, and outcomes for your agents, one thread at a time. Open it from **Observability → Agent Analytics**.
Agent Analytics, reporting conversation outcomes one thread at a time.
You can narrow the view by workspace, by agent name or ID, by **Business ID**, or by date range.
Each conversation thread is listed with:
| Field | What it shows |
| -------------- | ------------------------------------------------------------------------------------------- |
| **Thread** | The thread's ID. |
| **Agent** | Which agent handled the thread (for example, *Universal Document Intelligence Specialist*). |
| **Started At** | When the thread began. |
| **Duration** | How long it ran (for example, `32s`, `2m 1s`, `9m 47s`). |
| **Status** | The outcome — **Completed** (green), **Waiting** (in progress), or **Aborted** (red). |
| **Actions** | A per-row menu for that thread. |
## Related
{% content-ref url="/spaces/0qmgQjJ5aArDTj2ACFHG/pages/807cab861e090edd0ce825909db3db1b28f73799" %}
[Control Center](/start-here/control-center.md)
{% endcontent-ref %}
{% content-ref url="/spaces/0qmgQjJ5aArDTj2ACFHG/pages/9cd0c4d868b97b43a234c8d0ca5c3690fa58decb" %}
[Evaluation & Quality](/governance/evaluation-and-quality.md)
{% endcontent-ref %}
{% content-ref url="/spaces/0qmgQjJ5aArDTj2ACFHG/pages/4d5234c8a07efab44ec5e24cc81c8c08bae3eafc" %}
[Logs & Data](/governance/logs-and-data.md)
{% endcontent-ref %}
{% content-ref url="/spaces/0qmgQjJ5aArDTj2ACFHG/pages/d94f394409e2ca941f1b4be707fbb3cb9db99a62" %}
[Credits & Tokens](/governance/billing.md)
{% endcontent-ref %}
---
# 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.uptiq.ai/governance/observability.md?ask=&goal=
```
`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.