arrow_back

Monitoring and Logging for Cloud Run Functions

Accedi Partecipa
Quick tip: Review the prerequisites before you run the lab
Use an Incognito or private browser window to run this lab. This prevents any conflicts between your personal account and the student account, which may cause extra charges incurred to your personal account.
Metti alla prova le tue conoscenze e condividile con la nostra community.
done
Accedi a oltre 700 lab pratici, badge delle competenze e corsi

Monitoring and Logging for Cloud Run Functions

Lab 45 minuti universal_currency_alt 1 credito show_chart Introduttivi
info Questo lab potrebbe incorporare strumenti di AI a supporto del tuo apprendimento.
Metti alla prova le tue conoscenze e condividile con la nostra community.
done
Accedi a oltre 700 lab pratici, badge delle competenze e corsi

GSP092

Google Cloud self-paced labs logo

Overview

In this lab you use Cloud Monitoring to view Cloud Run functions details in the Google Cloud console. The Cloud Run function details include execution times and counts, and memory usage.

Objectives

In this lab, you learn how to perform the following tasks:

  • Create a Cloud Run function.
  • Create logs-based metric for a Cloud Run function.
  • Use Metrics Explorer to view data for your Cloud Run function.
  • Create charts on the Monitoring Overview window.

Setup and requirements

Before you click the Start Lab button

Read these instructions. Labs are timed and you cannot pause them. The timer, which starts when you click Start Lab, shows how long Google Cloud resources are made available to you.

This hands-on lab lets you do the lab activities in a real cloud environment, not in a simulation or demo environment. It does so by giving you new, temporary credentials you use to sign in and access Google Cloud for the duration of the lab.

To complete this lab, you need:

  • Access to a standard internet browser (Chrome browser recommended).
Note: Use an Incognito (recommended) or private browser window to run this lab. This prevents conflicts between your personal account and the student account, which may cause extra charges incurred to your personal account.
  • Time to complete the lab—remember, once you start, you cannot pause a lab.
Note: Use only the student account for this lab. If you use a different Google Cloud account, you may incur charges to that account.

How to start your lab and sign in to the Google Cloud console

  1. Click the Start Lab button. If you need to pay for the lab, a dialog opens for you to select your payment method. On the left is the Lab Details pane with the following:

    • The Open Google Cloud console button
    • Time remaining
    • The temporary credentials that you must use for this lab
    • Other information, if needed, to step through this lab
  2. Click Open Google Cloud console (or right-click and select Open Link in Incognito Window if you are running the Chrome browser).

    The lab spins up resources, and then opens another tab that shows the Sign in page.

    Tip: Arrange the tabs in separate windows, side-by-side.

    Note: If you see the Choose an account dialog, click Use Another Account.
  3. If necessary, copy the Username below and paste it into the Sign in dialog.

    {{{user_0.username | "Username"}}}

    You can also find the Username in the Lab Details pane.

  4. Click Next.

  5. Copy the Password below and paste it into the Welcome dialog.

    {{{user_0.password | "Password"}}}

    You can also find the Password in the Lab Details pane.

  6. Click Next.

    Important: You must use the credentials the lab provides you. Do not use your Google Cloud account credentials. Note: Using your own Google Cloud account for this lab may incur extra charges.
  7. Click through the subsequent pages:

    • Accept the terms and conditions.
    • Do not add recovery options or two-factor authentication (because this is a temporary account).
    • Do not sign up for free trials.

After a few moments, the Google Cloud console opens in this tab.

Note: To access Google Cloud products and services, click the Navigation menu or type the service or product name in the Search field. Navigation menu icon and Search field

Activate Cloud Shell

Cloud Shell is a virtual machine that is loaded with development tools. It offers a persistent 5GB home directory and runs on the Google Cloud. Cloud Shell provides command-line access to your Google Cloud resources.

  1. Click Activate Cloud Shell Activate Cloud Shell icon at the top of the Google Cloud console.

  2. Click through the following windows:

    • Continue through the Cloud Shell information window.
    • Authorize Cloud Shell to use your credentials to make Google Cloud API calls.

When you are connected, you are already authenticated, and the project is set to your Project_ID, . The output contains a line that declares the Project_ID for this session:

Your Cloud Platform project in this session is set to {{{project_0.project_id | "PROJECT_ID"}}}

gcloud is the command-line tool for Google Cloud. It comes pre-installed on Cloud Shell and supports tab-completion.

  1. (Optional) You can list the active account name with this command:
gcloud auth list
  1. Click Authorize.

Output:

ACTIVE: * ACCOUNT: {{{user_0.username | "ACCOUNT"}}} To set the active account, run: $ gcloud config set account `ACCOUNT`
  1. (Optional) You can list the project ID with this command:
gcloud config list project

Output:

[core] project = {{{project_0.project_id | "PROJECT_ID"}}} Note: For full documentation of gcloud, in Google Cloud, refer to the gcloud CLI overview guide.

Task 1. Viewing Cloud Run function logs & metrics in Cloud Monitoring

Before you collect logs and alerts, you need something to monitor. In this section, you create a Hello World Cloud Run function to monitor.

  1. In the Cloud console, select Navigation menu (Navigation menu icon) > Cloud Run, and then click Write a Function.

  2. Set the following:

    • Service Name: helloworld
    • Region:
    • Runtime: Node.js 22
    • Authentication: select radio button next to Allow unauthenticated invocations
  3. Expand Container(s), Volumes, Networking, Security and set the following:

    • Execution environment: select second generation.

    • Revision scaling, set the Maximum number of instances to 5.

  4. Leave the rest of the fields as default. Click Create.

Note: A helpful popup may appear to validate the required APIs are enabled in the project. Click the Enable button when requested.
  1. Click Save and Redeploy.

The function automatically deploys and is listed on the Cloud Run function page. This takes a few minutes. When you see a green check mark next to the name, the Cloud Run function is complete.

Test completed task

Click Check my progress to verify your performed task. If you have completed the task successfully you will be granted an assessment score.

Creating a Cloud Run function
  1. Open a new Cloud Shell window by clicking the Activate Cloud Shell Activate Cloud Shell icon at the top of the Google Cloud console.

  2. In Cloud Shell, run the following to get a tool called vegeta that will let you send some test traffic to your Cloud Run function:

curl -LO 'https://github.com/tsenart/vegeta/releases/download/v12.12.0/vegeta_12.12.0_linux_386.tar.gz'
  1. Unpack the vegeta tool by running the following:
tar -xvzf vegeta_12.12.0_linux_386.tar.gz
  1. On the Cloud Run page, click your function name, then click the helloworld URL for your function.

If you see Hello World! in the new browser tab that opens, you're up and running!

  1. Set and verify the Cloud Run URL link:
CLOUD_RUN_URL=$(gcloud run services describe helloworld --region={{{ project_0.default_region }}} --format='value(status.url)') echo $CLOUD_RUN_URL
  1. Now send traffic to your Cloud Run function:
echo "GET $CLOUD_RUN_URL" | ./vegeta attack -duration=300s -rate=200 > results.bin
  1. Keep this running in the background while you complete the next sections.

Task 2. Create a logs-based metric

Now you'll create a Distribution type logs based metric to extract the value of latency from the log entries httpRequest.latency field.

  1. In the console, select Navigation menu > View All Products > Observability > Logging > Logs Explorer. The Cloud Logging opens in the console.

  2. To look at just the logs from your Cloud Run function, in the All resources dropdown, select Cloud Run Revision > helloWorld then click Apply.

  3. Click Run query.

  4. In Actions dropdown click Create metric.

  5. In the Create log-based metric form:

  • Change the Metric Type to Distribution.
  • In Log-based metric name enter CloudRunFunctionLatency-Logs.
  • Enter httpRequest.latency for Field name.

The log-based metric should look like this:

Create logs metric page

  1. Click Create metric.

Now you'll see your user-defined metric added to your Logs-based Metrics page.

Test completed task

Click Check my progress to verify your performed task. If you have completed the task successfully you will be granted an assessment score.

Create logs-based metric

Task 3. Metrics Explorer

Next, you'll use Metrics Explorer to look at the data for your Cloud Run function.

Create a Monitoring Metrics Scope

Set up a Monitoring Metrics Scope that's tied to your Google Cloud Project. The following steps create a new account that has a free trial of Monitoring.

  • In the Cloud Console, click Navigation menu (Navigation menu icon) > View All Products > Observability > Monitoring.

When the Monitoring Overview page opens, your metrics scope project is ready.

  1. In the left menu, click Metrics explorer.

  2. Click on Select a metric dropdown. Deselect the Active button.

  3. Type CloudRunFunctionLatency-Logs in filter by resource or metric name and then select Cloud Run Revision > Logs-based metric > Logging/user/CloudRunFunctionLatency-Logs from the suggested metrics and click Apply.

Note: If Cloud Run Revision is not visible in the dropdown, uncheck Active. Logs-based metrics may initially show as 'Not Active' in the Metrics Explorer. This means that the metric has not yet received enough data to be considered active. It may take several minutes (or more) and sufficient traffic generation for the metric to become active.

If you encounter issues:

  • Double-check that you have selected the correct resource and metric in Cloud Monitoring.
  • Ensure that there are no filters applied in Cloud Monitoring.
  • Verify that the time range is set correctly in Cloud Monitoring.
  • Generate more traffic with the vegeta tool (increase the duration or rate).
  • Wait for a longer period, as there may be delays in log processing.
  1. On the top right corner change the widget type to Stacked bar chart using the dropdown menu.

  2. Explore other graph options and try a different metric. For example, click your current Cloud Run Revision metric to open the dropdown, select Cloud Run Revision > Request Count, and change the widget type to Stacked area chart.

  3. Continue to explore and experiment. For example, go back to the Cloud Run Revision metric and change the Aggregation to the 95th percentile. Select the widget type Line chart.

Task 4. Create charts on the Monitoring Overview window

Creating charts on the Monitoring Overview window is a great way to track metrics that are important to you. In this section, you set up the same charts you created in the previous section, but now they'll be saved into the Monitoring Overview window.

  1. In the left menu, click Dashboards.

  2. Click Create Custom Dashboard.

  3. Click on Add widget.

  4. Under Visualization, select Stacked bar.

  5. Under Select a metric dropdown select the default Cloud Run Revision > Request Count metric to open the dropdown and change the metric. Click Apply on the top right.

  6. Click Add widget. Under Visualization, select Heatmap.

  7. Start typing Cloud Run Revision into the Select a metric dropdown, and then select Cloud Run Revision > Logs-based metric > Logging/user/CloudRunFunctionLatency-Logs from the suggested metrics and click Apply.

Note: If CloudRunFunctionLatency-Logs metric is not visible in the dropdown, uncheck Active.
  1. Click Add widget. Under Visualization, select Line.

  2. Start typing Cloud Run Revision into the Select a metric dropdown, and then select Cloud Run Revision > Request_latency from the suggested metrics. Set the Aggregation to Mean and click Apply.

  3. Click Add widget. Under Visualization, select Stacked bar.

  4. Start typing Cloud Run Revision into the Select a metric dropdown, and then select Cloud Run Revision > Container > Container CPU Allocation from the suggested metrics. Click Apply.

By default, the charts name themselves after the metric you're using, but you can rename them.

  1. Click the Dashboard name at the top it should start with New Dashboard - and rename it to Cloud Run Function Custom Dashboard.

For a quick reference, to see these charts click Dashboards in the left panel of the Monitoring page.

Task 5. Test your understanding

Below are multiple-choice questions to reinforce your understanding of this lab's concepts. Answer them to the best of your abilities.

Congratulations!

Congratulations! In this lab, you created a Cloud Run function, created a logs-based metric, used Metrics Explorer, and created charts on the Monitoring Overview window.

Google Cloud training and certification

...helps you make the most of Google Cloud technologies. Our classes include technical skills and best practices to help you get up to speed quickly and continue your learning journey. We offer fundamental to advanced level training, with on-demand, live, and virtual options to suit your busy schedule. Certifications help you validate and prove your skill and expertise in Google Cloud technologies.

Manual Last Updated March 5, 2025

Lab Last Tested March 5, 2025

Copyright 2025 Google LLC All rights reserved. Google and the Google logo are trademarks of Google LLC. All other company and product names may be trademarks of the respective companies with which they are associated.

Before you begin

  1. Labs create a Google Cloud project and resources for a fixed time
  2. Labs have a time limit and no pause feature. If you end the lab, you'll have to restart from the beginning.
  3. On the top left of your screen, click Start lab to begin

Use private browsing

  1. Copy the provided Username and Password for the lab
  2. Click Open console in private mode

Sign in to the Console

  1. Sign in using your lab credentials. Using other credentials might cause errors or incur charges.
  2. Accept the terms, and skip the recovery resource page
  3. Don't click End lab unless you've finished the lab or want to restart it, as it will clear your work and remove the project

Questi contenuti non sono al momento disponibili

Ti invieremo una notifica via email quando sarà disponibile

Bene.

Ti contatteremo via email non appena sarà disponibile

One lab at a time

Confirm to end all existing labs and start this one

Use private browsing to run the lab

Use an Incognito or private browser window to run this lab. This prevents any conflicts between your personal account and the Student account, which may cause extra charges incurred to your personal account.