> 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/llm-logs.md).

# LLM Logs

Trace model calls, token use, cost, and latency.

LLM Logs records every LLM completion and embedding call the platform made. Open **Observability → LLM Logs**, on either the **Gateway Logs** or **Embedding Logs** tab.

## Gateway Logs

Gateway Logs records every completion call, with its model, target, tokens, and cost.

<figure><img src="https://1326225582-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0qmgQjJ5aArDTj2ACFHG%2Fuploads%2Fgit-blob-e7baa872484e095f8a54e6895a9a1ac2f266afb8%2Fqore_control-center_control-centre-observability-llm-logs-gateway_rounded_shadow.png?alt=media" alt="The LLM Logs Gateway Logs tab, listing model calls with tokens, cost, latency, and status"><figcaption><p>Gateway Logs, tracing every completed model call.</p></figcaption></figure>

You can narrow by project and model. You can also search by model or agent. Each row is one completed model call:

| Field       | What it shows                               |
| ----------- | ------------------------------------------- |
| **Model**   | The model that ran, such as `gpt-4.1-mini`. |
| **For**     | The target the call was made for.           |
| **Tokens**  | Tokens consumed by the call.                |
| **Cost**    | The credit cost of the call.                |
| **Latency** | How long the call took, in milliseconds.    |
| **When**    | The completion time.                        |
| **Status**  | The call outcome, such as **Success**.      |

## Embedding Logs

Embedding Logs records every embedding call — the queries used to build or search knowledge, not completions.

<figure><img src="https://1326225582-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0qmgQjJ5aArDTj2ACFHG%2Fuploads%2Fgit-blob-3bbf3ba987076c8982fe9af2e0454c5abfa14c51%2Fqore_control-center_control-centre-observability-llm-logs-embedding_rounded_shadow.png?alt=media" alt="The LLM Logs Embedding Logs tab, listing embedding queries with model, when, and status"><figcaption><p>Embedding Logs, tracing every embedding call.</p></figcaption></figure>

You can narrow by project and model. You can also search by query or model. Each row is one embedding call:

| Field      | What it shows                                                                     |
| ---------- | --------------------------------------------------------------------------------- |
| **Query**  | The text that was embedded — a document chunk, a search query, or an instruction. |
| **Model**  | The embedding model that ran, such as `OpenAI Text Embedding Ada 002`.            |
| **When**   | The completion time.                                                              |
| **Status** | The call outcome, such as **Success**.                                            |

Select a row on either tab to see the call's full detail.


---

# 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/llm-logs.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.