> 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/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 **Logs & Data → Incoming Request Logs**.
The Incoming Request Logs screen, listing requests with method, URL, and timestamp columns

Incoming Request Logs, the default view.

Incoming Request Logs with the HTTP method filter open, showing GET, POST, PUT, PATCH, and DELETE options

Filtering Incoming Request Logs by HTTP method.

Incoming Request Logs with the module filter open, showing Agent, App, Skill, Integrations, Marketplace, and Platform options

Filtering Incoming Request Logs by module.

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 **Logs & Data → Outgoing Request Logs**.
The Outgoing Request Logs screen, listing requests with method, status, URL, response time, and when columns

Outgoing Request Logs, the default view.

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