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 in both preview and production deployments. These log results provide information about the output for your functions as well as the console.log output.

With runtime logs:

• Logs are shown in realtime and grouped as per request.
• Each action of writing to standard output, such as using console.log, results in a separate log entry.
• The maximum number of logs is 256 lines per request
• Each of those logs can be up to 256 KB per line
• The sum of all log lines can be up to 1 MB per request

You can view the following log types in the Logs tab:

To view runtime logs:

1. From the dashboard, select the project that you wish to see the logs for
2. Select the Logs tab from your project overview
3. 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 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 requests that contain Warning, and Error logs. A request can contain both types of logs at the same time. Streaming Functions will always preserve the original intent:

Additionally:

• Requests with a status code of 4xx are marked with Warning amber
• Requests with a status code of 5xx are marked with Error red
• All other individual log lines are considered Info

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 resource filter, you can search for requests containing logs generated as a result of:

You can filter your logs based on framework-defined mechanism or rendering strategy used such as API routes, Incremental Static Regeneration (ISR), and cron jobs.

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 request path used by a function such as /api/my-function.

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

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 request 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.

Logs are streamed. Each log output can be up to 256KB, and each request can log up to 1MB of data in total, with a limit of 256 individual log lines per request. If you exceed the log entry limits, you can only query the most recent logs.

Runtime logs are stored with the following observability limits: