Skip to main content
The Request Logs page shows a live audit trail of every request your gateway has processed. Logs are ordered with the most recent entries first and are paginated at 50 rows per page.

​
What each log entry shows

Additional fields are stored per log entry and available when debugging:
  • Request ID — a unique identifier for the request; see finding a specific request below
  • Auth mode — how the request was authenticated: GatelitSigned, Bearer, or GatelitKey
  • Streaming — whether the response was streamed
  • Time to first token — latency from request start to the first streamed token, in milliseconds (streaming requests only)
  • Prompt ID — the ID of the saved prompt template used, if the request was linked to one

​
Filtering logs

Use the filter controls above the table to narrow down entries:
  • Status — show only requests with a specific outcome (success or error)
  • Provider — show only requests routed to a specific provider (OpenAI, Anthropic, Google, or Mistral)
  • Subject — type a partial subject string to search for requests from a specific user or service key
Filters combine — you can filter by both status and provider at the same time. Click Clear to reset all active filters.

​
Finding a specific request

Every gateway response includes an x-gatelit-request-id header. If a client reports an issue with a specific call, copy the value of that header and paste it into the Subject filter to locate the matching log entry quickly.
Log retention is determined by your organization’s plan. Older entries may no longer appear in the dashboard after the retention window has passed. Contact support if you need access to logs beyond the visible range.