Runtime Logs

The Logs tab allows you to view, search, inspect, and share your runtime logs without any third-party integration. You can also filter and group your runtime logs based on the relevant fields.

Runtime logs include all logs generated by Serverless and Edge Function invocations. These log results provide information about the output for your functions as well as the console.log output.

You can use the Logs tab to debug and analyze the information provided by the logs.

To view runtime logs, click the Logs tab from your project overview in the dashboard. From here you can view, filter, and search through the runtime logs. Each log row shares basic info about the request like execution, domain name, HTTP status, function type, and RequestId.

You can view runtime logs for both preview and production deployments.

You can use the following filters from the left sidebar to get a refined search experience.

You can filter runtime logs based on a specific timeline. It can vary from the past hour, last 3 days, or a custom timespan depending on your account type. You can use the Live mode option to follow the logs in real-time.

You can filter runtime logs by three kinds of levels: Info, Warning, and Error.

• Edge logs with an output stdout are marked as Info (for example, console.log)
• Edge logs with an output stderr are marked as Error (for example, console.error)
• Requests with a status code of 4xx are considered a Warning
• Requests with a status code of 5xx are considered Error
• All other requests are considered Info

These levels are highlighted with different colors for example, yellow for warnings and red for errors. This color coding is beneficial with debugging; you can identify the failed requests and the reason behind the failure.

You can filter and analyze logs for one or more functions defined in your project. The log output is generated for the Serverless Functions, Edge Functions, and Edge Middleware.

You can view logs for one or more domains and subdomains attached to your team’s project. Alternatively, you can use the Search hosts... field to navigate to the desired host.

Like host and functions, you can filter your logs based on deployments URLs.

Using the type filter, you can search for four logs types generated as a result of:

You can filter your logs based on the request method used by a function such as GET or POST.

You can filter your logs based on the cache behavior such as HIT or MISS.

Log Presets allow you to save your selected filters for later use. You can save presets to either My Project Presets (related to your personal account) or Team Project Presets. Personal presets can only be viewed and edited by the user who created them.

To save a preset, make a change to the filters in the left sidebar and select the Save button. You can then choose the scoping group to save the preset to, either Personal or Team.

You can use the main search field to filter logs by their messages. In the current search state, filtered log results are sorted chronologically, with the most recent first. Filtered values can also be searched from the main search bar.

You can view details for each generated runtime log to analyze and improve your debugging experience. When you click a log from the list, the following details appear in the right sidebar:

Towards the end of the log results window is a button called Show New Logs. By default, it is set to display log results for the past 30 minutes.

Click this button, and it loads new log rows. The latest entries are added based on the selected filters.

You can share a log entry with other team members to view the particular log and context you are looking at. Click on the log you want to share, copy the current URL of your browser, and send it to team members through the medium of your choice.

Unlike build logs that are stored indefinitely for each deployment, runtime logs are stored with the following limits: