Logs in the Render Dashboard

Use Render’s log explorer to view and search recent logs generated by your service. The explorer is available from your service’s Logs page in the Render Dashboard:

Log explorer in the Render Dashboard

In addition to searching for a particular string, you can filter by details like log level and time range.

When you identify a log line of interest, mouse over it and click View in context to jump to its original location:

If you have a team account, the explorer also displays HTTP request logs for your web services.

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

Render does not emit logs for static sites or Redis instances.

Log filters

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

Time range

You can limit results to a predefined range (such as Last 24 hours), specify a custom range, or select Live tail to view a live feed of recent logs. Available ranges depend on your account’s log retention period.

Specify using the dropdown in the upper right of the log explorer.


The log level, such as debug, warning, or error.

Specify in the search box.


HTTP request logs only. The HTTP method of a particular request (such as GET or POST).

Specify in the search box.


HTTP request logs only. The response code for a particular request (such as 200, 404, or 500).

Specify in the search box.


HTTP request logs only. The originating domain of a particular request (such as my-web-service.onrender.com).

Specify in the search box.

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.



Returns logs that contain foo followed by bar using wildcard search.


Returns logs that contain foo followed by bar using a regular expression.


Returns logs that contain foo or bar.


Returns request logs with a 4xx status code.


Returns request logs with a GET or POST method.


Returns request logs with a path that starts with api/resource/ and ends with /subresource.


Returns request logs with a response time greater than one second.

Keyboard shortcuts

The log explorer supports these keyboard shortcuts:

Focus search bar/
Enable fullscreenm
Exit fullscreenm or Esc
Scroll (slow)Arrow Up / Arrow Down
Scroll (fast)Page Up / Page Down
Jump to topHome
Jump to bottomEnd

HTTP request logs

If you have a team account, Render generates a log entry for each HTTP request to your team’s web services from the public internet:

HTTP request logs in the Render Dashboard

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:

Nov 2 2:47:04 PM [GET] 400 clientIP="" requestID="542c7b8b-c833-4b3c" ...

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:

Rndr-Id: 542c7b8b-c833-4b3c

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:

Viewing the Rndr-Id header in Chrome

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.

Logs for an individual deploy or job

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 viewer:

Selecting a deploy to view logs


Viewing logs for a single deploy

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

Log retention period

Render’s log retention period depends on your account and plan type (see the pricing page):

Account / Plan TypeRetention Period
Individual7 days
Team14 days
Organization / Enterprise30 days

Logs that are older than your current rentention 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.