Skip to main content
We record four kinds of data about your , with nothing to install in your code:
  • Every request the gateway passes to your app.
  • Everything your instances print to stdout and stderr.
  • CPU, memory, disk, and network for each instance.
  • Each build step and its output.

Request logs

One row per proxied request: method, path, status, and the split between gateway and instance latency. Headers and bodies on request.

Runtime logs

stdout and stderr from every instance, parsed into severity, message, and searchable attributes.

Metrics

Requests per second, latency percentiles, CPU, memory, disk, network, instance count, and instance events.

Build logs

Each step of a build, whether it was cached, and its output.

​
Where to look in the dashboard

  • Request and runtime logs: open a and click Requests or Logs in the sidebar. Filter by app, , , or region.
  • Metrics and build steps: open the app, click Deployments, and open a deployment. Its overview has the traffic and resource charts and the build steps. Its Network view shows regions and instances with live request rates.

​
Rejected requests aren’t in the request log

The request log only has requests that reached your app. Requests rejected by a policy, or that the gateway couldn’t route (an unknown hostname, or no running instance), aren’t there. So your request log can show less traffic than your callers sent. See Request logs.

​
Retention

Each kind of data is kept for a fixed time, shown below. The dashboard can show all of it. The analytics API has a second limit: your plan’s log query range, 3 days on Starter, 7 on Pro, and 14 on Business. You can read back whichever is shorter. A query that reaches further fails with err:user:bad_request:query_range_exceeds_retention instead of returning partial results. For example, on Starter the analytics API reaches back 3 days into runtime logs that are kept for 90. On Business it reaches 7 days of request logs, not 14, because that’s how long they’re kept. See Compute limits.

​
Query the data yourself

You can query request and runtime logs with SQL through the analytics API, using the gateway_requests_v1 and runtime_logs_v1 tables, to build your own dashboards or alerts. See Query gateway requests and runtime logs. Read build logs through the API with deployments.listBuildLogs. See Build logs. Resource metrics are only in the dashboard.
Last modified on October 22, 2026