> For the complete documentation index, see [llms.txt](https://docs.nexos.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nexos.ai/gateway-api/gateway-logs.md).

# Gateway Logs

### Overview

The **Gateway Logs** section provides a detailed view of requests processed through the nexos.ai API Gateway. Use it to inspect individual requests, troubleshoot issues, monitor performance, and understand how models and API keys are being used.

Each log entry contains information about a specific request, such as the model used, request status, cost, duration, and API key source.

### Filter gateway logs

Use the filters at the top of the page to find specific requests or narrow down the logs you want to investigate.

You can filter logs by:

* **Time range** - Show requests from a specific period.
* **Models** - View requests sent to selected models.
* **Users** - Filter requests by user.
* **Teams** - View requests associated with specific teams.
* **Team API Keys** - Filter by the API key used to make a request.
* **Key source** - Filter requests based on where the API key comes from.

Use **Clear filters** to return to the default view.

<figure><img src="https://4112003433-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FDcOhapgXnoeDvgGQ8Jm4%2Fuploads%2FSmLZvlXk56x0STksVsG8%2Fimage.png?alt=media&amp;token=fcc19f3d-c832-4cec-bc48-a02216a10bb4" alt=""><figcaption></figcaption></figure>

### Explore request details

The logs table gives you an overview of individual Gateway requests. Use it to identify requests you want to investigate further.

Depending on the available data and selected columns, you can review information such as:

* **ID** - A unique identifier for the request.
* **Start time** - When the request was initiated.
* **Operation name** - The type of operation performed.
* **Status** - The current or final request status.
* **Model** - The model used to process the request.
* **Cost** - The cost associated with the request.
* **Duration** - How long the request took to complete.
* **API key name** - The API key associated with the request.
* **Key source** - Where the API key originated.

This information can help you investigate failed or slow requests and understand usage at the individual request level.

### Customize columns

Click **Columns** to choose which information is displayed in the Gateway Logs table. This lets you focus on the fields that are most relevant to your current task.

For example, when investigating performance, you can focus on **Status, Model, and Duration**. For usage analysis, you may want to include **API key name** and **Key source**.

<figure><img src="https://4112003433-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FDcOhapgXnoeDvgGQ8Jm4%2Fuploads%2FXCdlpWD8HP8W6dE1UDG6%2FRecording%202026-10-20%20134221.gif?alt=media&amp;token=3df517d6-8a8d-4863-8c47-10e03f8c7762" alt=""><figcaption></figcaption></figure>


---

# 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.nexos.ai/gateway-api/gateway-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.
