Want to stream logs to your observability provider?

See Streaming Render Service Logs.

View, search, and filter your service's runtime logs from its Logs page in the Render Dashboard:

With a Professional workspace or higher, the log explorer also shows HTTP request logs for web services.

Use any combination of text search and supported filters to narrow results:

Separately, you can view logs for any recent deploy or one-off job.

Render does not emit logs for static sites.

Log lines in the explorer display the following information:

HTTP request logs display the request's HTTP method and status code instead of an instance ID.

When searching with the log explorer, you can filter results by the following (in addition to searching for an arbitrary string):

Wildcards and regular expressions

The log explorer supports searching with wildcards and regular expressions.

To match any number of characters, use the wildcard token (*). To match against a regular expression, enclose your search in forward slashes (/). You can then use any metacharacters supported by the RE2 syntax.

You can use wildcards and regular expressions in search strings and in filters. See the table below for some useful examples.

The log explorer supports these keyboard shortcuts:

If you have a Professional workspace or higher, Render generates a log entry for each HTTP request to your team's web services from the public internet:

This helps you debug unexpected behavior for a request, in particular by tracing its execution via the requestID field.

HTTP request logs appear alongside application logs in the explorer, and they support additional filters (such as method and status_code).

Render does not generate request logs for HTTP requests sent from other services over your private network—only for requests sent to web services over the public internet.

Tracing with requestID and Rndr-Id

In each HTTP request log entry, the value of the requestID field uniquely identifies the associated request:

Render includes this same value in the Rndr-Id HTTP header—both in the request to your web service and in the response to the requesting client:

In your web service's code, you can extract this value from the header and include it in every log you generate for a given request. If you do, you can search for this ID in the log explorer to view the corresponding request's chronological log history.

On the client's side, here's what a Rndr-Id looks like in Chrome's Network panel:

By tracing each phase of the request lifecycle with one consistent ID, you can more quickly diagnose and debug issues in collaboration with the users who encounter them.

View the logs for an individual deploy of your service from the service's Events page. Click the word Deploy in a timeline entry to open the log explorer:

⬇️

Similarly, you can view logs for the execution of a one-off job from the associated service's Jobs page.

The log explorer supports both light and dark display themes. It defaults to matching the theme that you set for the Render Dashboard.

You can independently set the explorer's theme from the Appearance section of your User Settings page:

Render's log retention period depends on your workspace's plan (see the pricing page):

Logs older than your current retention period are no longer available, even if you upgrade your plan to extend the period.

If you need to retain logs for a longer period, you can stream your logs to a syslog-compatible provider.

Render processes a maximum of 6,000 application-generated log lines per minute for each running instance of a service.

If an instance generates logs in excess of this limit, Render drops the excess log lines. Dropped log lines don't appear in the log explorer or in log streams.