> 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/control-center/observe.md).

# Observe

Monitor platform activity and investigate operational data.

Observability is a [Control Center](/start-here/control-center.md) module for governance and operations. Use it to understand platform activity and investigate operational issues. Track adoption, inspect agent runs, audit changes, analyze requests, and export data for reporting.

### Explore observability

* [Runs & Traces](/control-center/observe/runs-and-traces.md) — Investigate an agent or app execution step by step.
* [Analytics](/control-center/observe/analytics.md) — Measure app engagement, build activity, and agent outcomes.
* [Audit Trails](/control-center/observe/audit-trails.md) — Review account configuration and access changes.
* [LLM Logs](/control-center/observe/llm-logs.md) — Analyze model calls, tokens, costs, and latency.
* [Request Logs](/control-center/observe/request-logs.md) — Inspect HTTP requests received and sent by the platform.
* [DB Query Logs](/control-center/observe/db-query-logs.md) — Review database operations executed by the platform.
* [Export](/control-center/observe/export.md) — Deliver observability data as scheduled or one-time files.

### Coverage and access

Observe records account activity from Qore apps, agents, model calls, HTTP requests, database operations, and account changes.

| Area                                                 | Recorded activity                                                                                 | Scope and filters                                                            | Known limits                                                                                                                             | Access and retention                                                                                   |
| ---------------------------------------------------- | ------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------ |
| Runs & Traces                                        | Agent and app executions, including logged LLM calls, tool calls, guardrails, inputs, and outputs | Account-wide. Filter by project, agent, identifier, or date range            | Short, aborted, or incompletely logged runs might not have reconstructed spans. `No traces to display` doesn't mean the execution failed | Your Control Center role determines available data and actions. Retention is not defined here          |
| Analytics, Audit Trails, LLM Logs, and DB Query Logs | App and agent activity, account changes, model calls, and database operations                     | Most views support project and date filters                                  | Each screen shows its own activity type. Use the relevant screen for the question you need to answer                                     | Your Control Center role determines available data and actions. Retention is not defined here          |
| Request Logs                                         | HTTP requests received by Qore and requests Qore sends to external services                       | Filter by project, module, method, and date range                            | They don't record traffic that doesn't pass through Qore                                                                                 | Your Control Center role determines available data and actions. Retention is not defined here          |
| Export                                               | Selected observability datasets, delivered as CSV, JSON, or PDF files                             | Export every project or one project. Choose a one-time or scheduled delivery | Each selected dataset creates a separate file                                                                                            | Use [Export](/control-center/observe/export.md) to retain records required for reporting or compliance |

### Related

{% content-ref url="/pages/807cab861e090edd0ce825909db3db1b28f73799" %}
[Control Center](/start-here/control-center.md)
{% endcontent-ref %}

{% content-ref url="/pages/9cd0c4d868b97b43a234c8d0ca5c3690fa58decb" %}
[Evals](/control-center/evals.md)
{% endcontent-ref %}

{% content-ref url="/pages/eIjuTBKGdEo5Aq2Akkal" %}
[Cost Control](/control-center/cost-control.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/control-center/observe.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.