Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/outray-tunnel/outray/llms.txt

Use this file to discover all available pages before exploring further.

OutRay captures detailed information about every request that passes through your tunnels. You can monitor traffic in real time from the terminal while a tunnel is running, or review historical data from the dashboard.

​
Real-time logs in the CLI

When you start a tunnel, OutRay prints a log line for each incoming HTTP request directly in your terminal: 
GET  /api/users          200  42ms
POST /api/orders         201  118ms
GET  /api/users/42       404  9ms
Each line shows:
  • HTTP method — GET, POST, PUT, DELETE, etc.
  • Path — the request path and query string.
  • Status code — quickly spot 4xx and 5xx errors.
  • Duration — time taken for your local service to respond.

​
Suppressing CLI output

In automated or CI environments where log output is unwanted, use the --no-logs flag: 
outray 3000 --no-logs
The tunnel continues to function normally — only the per-request log lines are suppressed.

​
Dashboard: traffic analytics

The OutRay dashboard provides an aggregate view of your tunnel’s traffic over time. Navigate to a tunnel’s detail page to see:
  • Request count — total number of requests received.
  • Bandwidth usage — ingress and egress data transfer.
  • Success rate — ratio of 2xx responses to total requests.
  • Response times — average and percentile latency for your local service.

​
Dashboard: request history

The request history view lists individual requests with their method, path, status code, and duration. Use this to trace specific requests, identify patterns in errors, or replay webhooks.
Request history retention varies by subscription plan. See the pricing page for current retention limits per plan.

​
Dashboard: tunnel status

The dashboard shows the current status of each tunnel — whether it is active, idle, or offline. This is useful for confirming that a long-running tunnel in a CI or staging environment is still connected.

Build docs developers (and LLMs) love

Get started for freeTalk to us