> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.fabricgateway.ai/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.fabricgateway.ai/_mcp/server.

# See your requests

> Find a request in traces, check which model or provider answered, and give your admin the details they need.

Fabric AI Gateway writes an access log record for every request that reaches your configuration, so you can check what happened to one of yours. A trace exists only if the request was sampled and the data plane exports traces. Traces show how the gateway handled a request, including which plugins ran and which provider answered. This topic shows you how to get a request's ID, find it in traces, and share it with an admin if you can't see traces yourself.

## Prerequisites

Before you begin, make sure you have the following:

* A request that you already sent through a route.
* Access to **Traces** in the console. If you can't see it, ask your admin to look up the request for you, as the last section describes.

## Get the request ID

Every response, including errors, carries an `X-Request-Id` header. In cURL, add `-i` to print the response headers.

```bash
curl -i "BASE_URL/v1/models" \
  -H "fg-api-key: GATEWAY_KEY"
```

## Find the request in traces

To find the request, do the following:

1. In the console sidebar, select **Traces** to see requests for the current namespace. If you're an admin, you can also select **Admin** and then **Traces** to see requests across your whole organization.
2. Select a time range, and filter by **Route**, **Connection**, or **Status**.
3. Select the row that matches your request, and open its span view.

On a route with a model router, you can also read the `x-fabric-model` response header to see which provider and model answered. To read the details of a trace, including plugin timing and the upstream attempt, see [Inspect traces](/use/monitor/traces).

## Ask an admin to look it up

If you can't open **Traces**, send your admin the `X-Request-Id` value, the time you sent the request, and the route. They can find the trace and tell you why the request failed or what a plugin did to it.

## Next steps

* [Troubleshoot access](/use/troubleshoot-access)
* [Troubleshoot Fabric AI Gateway](/help/troubleshooting)
* [Handle errors and retries](/use/errors-and-retries)