> 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/ai-workbench-qore/control-center/observe/request-logs.md).

# Request Logs

Inspect HTTP requests received by the platform and sent to external services.

Request Logs records HTTP requests received by the platform and sent to external services.

## Incoming request logs

Incoming Request Logs records the requests received by the platform API. Open **Observe → Request Logs**, then **Incoming Request Logs**.

<figure><img src="https://1326225582-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0qmgQjJ5aArDTj2ACFHG%2Fuploads%2Fgit-blob-0fa83e8b8a81f3ced85af1cf7998ea04b7f1f3f4%2Fqore_control-center_control-centre-observability-incoming-request-logs_rounded_shadow.png?alt=media" alt="The Incoming Request Logs screen, listing requests with method, URL, and timestamp columns"><figcaption><p>Incoming Request Logs, the default view.</p></figcaption></figure>

<figure><img src="https://1326225582-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0qmgQjJ5aArDTj2ACFHG%2Fuploads%2Fgit-blob-5fa342279e4e26d3f4e1f52ce4896553f0672868%2Fqore_control-center_control-centre-controls-logs-data-incoming-request-logs-all-methods_rounded_shadow.png?alt=media" alt="Incoming Request Logs with the HTTP method filter open, showing GET, POST, PUT, PATCH, and DELETE options"><figcaption><p>Filtering Incoming Request Logs by HTTP method.</p></figcaption></figure>

<figure><img src="https://1326225582-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0qmgQjJ5aArDTj2ACFHG%2Fuploads%2Fgit-blob-ce91126f92ac1cb93c25356128708d9e6849c505%2Fqore_control-center_control-centre-controls-logs-data-incoming-request-logs-all-modules_rounded_shadow.png?alt=media" alt="Incoming Request Logs with the module filter open, showing Agent, App, Skill, Integrations, Marketplace, and Platform options"><figcaption><p>Filtering Incoming Request Logs by module.</p></figcaption></figure>

You can narrow by project and date range. You can also search the log. Filter by these modules:

* **Agent**
* **App**
* **Skill**
* **Integrations**
* **Marketplace**
* **Platform**

Filter by **GET**, **POST**, **PUT**, **PATCH**, or **DELETE**. Each row shows the request's **Method**, **URL**, and **When**. Select a row for the full request detail.

## Outgoing request logs

Outgoing Request Logs records the requests the platform made to external services. Open **Observe → Request Logs**, then **Outgoing Request Logs**.

<figure><img src="https://1326225582-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0qmgQjJ5aArDTj2ACFHG%2Fuploads%2Fgit-blob-33cb1ea11555ef087844cb0b481c5a0572c9dc2d%2Fqore_control-center_control-centre-observability-outgoing-request-logs_rounded_shadow.png?alt=media" alt="The Outgoing Request Logs screen, listing requests with method, status, URL, response time, and when columns"><figcaption><p>Outgoing Request Logs, the default view.</p></figcaption></figure>

The same filters apply: project, module, method, and date range. You can also search the log. Each row includes these fields:

| Field             | What it shows                                                                                                     |
| ----------------- | ----------------------------------------------------------------------------------------------------------------- |
| **Method**        | The request method, such as **GET** or **DELETE**. **CUSTOM** identifies calls that can't map to a standard verb. |
| **Status**        | The HTTP response status.                                                                                         |
| **URL**           | The destination the platform called.                                                                              |
| **Response Time** | How long the external call took, in milliseconds.                                                                 |
| **When**          | When the call was made.                                                                                           |

***

{% columns %}
{% column width="83.33333333333334%" %}

<p align="right"><em>Maintained by</em> <mark style="color:green;">Abhishek Paul</mark><br><code>AI-assisted, human-approved</code></p>
{% endcolumn %}

{% column width="16.666666666666664%" %}

<div align="left"><img src="https://1326225582-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0qmgQjJ5aArDTj2ACFHG%2Fuploads%2Fgit-blob-d034645b4f8f8ee661985f5306b60ded3289653c%2Fmaintainer-abhishek-paul.png?alt=media" alt="" width="60"></div>
{% endcolumn %}
{% endcolumns %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.uptiq.ai/ai-workbench-qore/control-center/observe/request-logs.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
