Skip to main content
The gateway logs every request to Supabase. You can view, filter, and search logs in the dashboard under Logs.

What’s logged

Filtering

Filter logs by:
  • Date range — last hour, 24h, 7d, or custom
  • Status — success or error
  • Model — filter to a specific provider/model
  • Org — filter by organisation (admin only)
  • End user — filter by the endUserId header value
  • Search — full-text search across request bodies and responses

Streaming view

The logs page supports a live streaming view — new requests appear as they’re logged, useful for debugging during development.

Cost tracking

The gateway estimates cost using the model catalog’s pricing data. This is an estimate, not billing-grade — use your provider’s dashboard for exact numbers. Cost is calculated as:
Prices are stored in the model catalog and updated when the catalog syncs.

Request body inspection

Click any log entry to see the full request and response payloads. This is useful for:
  • Debugging prompt variable interpolation
  • Inspecting structured output results
  • Verifying fallback chain behaviour
  • Checking what the gateway sent to the upstream provider

Retention

Logs are stored in Supabase. Retention depends on your Supabase plan and database size. For high-volume deployments, consider archiving older logs to external storage.
Request logs