Skip to main content
Unkey Deploy is currently in private beta. To get access, reach out on Discord or email support@unkey.com.
The Requests tab in your project shows every HTTP request that Sentinel processes on behalf of your deployments. Use it to debug failed requests, trace slow responses, and understand traffic patterns.

​
Request fields

Each row in the table shows the timestamp, the region that handled the request, the HTTP status code (color-coded by class), the HTTP method, the hostname, the request path, and the total end-to-end latency.

​
Filter requests

Combine filters to narrow results by status code, HTTP method, path, deployment, environment, and time range. Filters persist in the URL, so you can bookmark or share a filtered view.

​
Status code filter

The status code filter lets you narrow requests by HTTP response status. You can filter by class or by a specific code. Filter by class — select one or more status code ranges to show all requests in that class:
RangeLabel
2xxSuccess
3xxRedirect
4xxWarning
5xxError
Use the Select All checkbox to toggle every range at once. Filter by specific code — enter an exact status code (100–599) in the custom code input to isolate a single response type, for example 429 for rate-limited requests or 503 for service unavailable responses. When you type a custom code, range selections are cleared automatically. Click Apply Filter to update the results.
Requests page

​
Live mode

Toggle Live in the top-right corner to stream incoming requests in real time. New requests appear at the top of the table as they arrive. Toggle it off to freeze the view and browse historical data.

​
Request detail panel

Click any row to open the detail panel on the right side. The panel shows:
  • Request headers and body
  • Response headers and body
  • Latency breakdown (see below)
  • Deployment info: deployment ID, git branch, commit SHA, commit author, commit message, environment, and deployment status
  • Meta: request ID, timestamp, client IP, user agent, host, region, query string, and query parameters

​
Latency breakdown

The detail panel splits total latency into two components. Instance latency is the time your app spent processing the request. Sentinel latency is the time Sentinel spent on routing, policy evaluation, and proxying. If instance latency dominates, the bottleneck is in your application code. If Sentinel latency is high relative to total latency, the overhead is in the gateway layer. This distinction helps you focus debugging in the right place.

​
Retention

Request logs are retained for 30 days.
Last modified on April 16, 2026