View logs and metrics

Logging and metrics are important tools for debugging and monitoring code. App Hosting provides quick access to view logs and metrics for the Google Cloud services powering your web app: Cloud Run , Cloud Build and Cloud CDN.

Using standard logging syntax like Node.js' console.log , you can write log entries to Cloud Logging .

View usage in the console

Each backend has an Overviewtab, with a summary of your app's traffic (request count) and error rate over the past seven days.

Each backend also has a Usagetab with several usage graphs for activity and usage of your app. The data represented includes CDN bandwidth and requests, Cloud Run CPU and memory utilization, and more.

You can find additional utilization metrics for Cloud Run (such as CPU utilization and Memory utilization), in the Google Cloud console.

View logs in the console

From the Firebase console context menu (a 3-dot menu at upper right) for a rollout, you can get quick access to view the Cloud Run revision details and errors as well as build logs.

These logs contain helpful information for debugging your App Hosting deployments. For example, the Cloud Run log notes when package.json is not found.

The build log displays your build output, allowing you to triage whether errors occurred in configuration in your framework, or in App Hosting configuration. It also displays your basic runConfig settings, and indicates when settings are missing or when apphosting.yaml does not exist:

 > next build

   ▲ Next.js 14.1.4
   -   Environments: .env

   ...

Route (app)                              Size     First Load JS
┌ λ /                                    4.79 kB         214 kB
├ λ /_not-found                          882 B          85.3 kB
└ λ /restaurant/[id]                     5.28 kB         207 kB
+   First Load JS shared by all            84.4 kB
  ├ chunks/69-6678c81190a8fe82.js        29 kB
  ├ chunks/fd9d1056-51920e345d2966e8.js  53.4 kB
  └ other shared chunks (total)          1.98 kB 

Write logs to Cloud Logging

If you want to log custom events, you can write to Cloud Logging from Cloud Run , where your server-rendered code runs. Use standard JavaScript logging calls such as console.log and console.error . For example, to write a custom entry from code for a Next.js route handler , you would do something like this:

• console.log() commands have the INFOlog level.
• console.info() commands have the INFOlog level.
• console.warn() commands have the ERRORlog level.
• console.error() commands have the ERRORlog level.
• Internal system messages have the DEBUGlog level.

Note that console.log pipes through to Cloud Logging in the server-rendered code for your app. Events related to static rendering are sent to Cloud Build logs, while server rendering are sent to Cloud Run logs.

View server errors

Cloud Error Reporting consolidates errors from your App Hosting Cloud Run instance. You can optionally configure Cloud Error Reporting to notify you when new errors arise .