arrow_back

Cloud Monitoring: Qwik Start

Join Sign in

Cloud Monitoring: Qwik Start

50 minutes 1 Credit

GSP089

Google Cloud selp-paced labs logo

Overview

Cloud Monitoring provides visibility into the performance, uptime, and overall health of cloud-powered applications. Cloud Monitoring collects metrics, events, and metadata from Google Cloud, Amazon Web Services, hosted uptime probes, application instrumentation, and a variety of common application components including Cassandra, Nginx, Apache Web Server, Elasticsearch, and many others. Cloud Monitoring ingests that data and generates insights via dashboards, charts, and alerts. Cloud Monitoring alerting helps you collaborate by integrating with Slack, PagerDuty, HipChat, Campfire, and more.

This hands-on lab shows you how to monitor a Compute Engine virtual machine (VM) instance with Cloud Monitoring. You'll also install monitoring and logging agents for your VM which collects more information from your instance, which could include metrics and logs from 3rd party apps.

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 will be made available to you.

This hands-on lab lets you do the lab activities yourself in a real cloud environment, not in a simulation or demo environment. It does so by giving you new, temporary credentials that 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 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.
  • Time to complete the lab---remember, once you start, you cannot pause a lab.
Note: If you already have your own personal Google Cloud account or project, do not use it for this lab to avoid extra charges to your 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 pop-up opens for you to select your payment method. On the left is the Lab Details panel with the following:

    • The Open Google 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 Console. 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 from the Lab Details panel and paste it into the Sign in dialog. Click Next.

  4. Copy the Password from the Lab Details panel and paste it into the Welcome dialog. Click Next.

    Important: You must use the credentials from the left panel. Do not use your Google Cloud Skills Boost credentials. Note: Using your own Google Cloud account for this lab may incur extra charges.
  5. 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 Cloud Console opens in this tab.

Note: You can view the menu with a list of Google Cloud Products and Services by clicking the Navigation menu at the top-left. Navigation menu icon

Create a Compute Engine instance

  1. In the Cloud Console dashboard, go to Navigation menu > Compute Engine > VM instances, then click Create instance.

nav_compute.png

  1. Fill in the fields as follows, leaving all other fields at the default value:

    Field Value
    Name lamp-1-vm
    Region us-west1
    Zone us-west1-b
    Series N1
    Machine type n1-standard-2
    Boot disk Click Change. Select version Debian GNU/Linux 10 (buster) for Debian OS and click Select.
    Firewall check Allow HTTP traffic
  2. Click Create.

Wait a couple of minutes, you'll see a green check when the instance has launched.

Click Check my progress below. A green check confirms you're on track.

Create a Compute Engine instance (zone: us-west1-b)

Add Apache2 HTTP Server to your instance

  1. In the Console, click SSH to open a terminal to your instance.

    vmstatus.png

  2. Click Connect.

    If prompted, click Connect without Identity-Aware Proxy.

  3. Run the following commands in the SSH window to set up Apache2 HTTP Server:

sudo apt-get update sudo apt-get install apache2 php7.0

When asked if you want to continue, enter Y.

sudo service apache2 restart

Click Check my progress below. A green check confirms you're on track.

Add Apache2 HTTP Server to your instance
  1. Return to the Cloud Console, on the VM instances page. Click the External IP for lamp-1-vm instance to see the Apache2 default page for this instance.

externalip.png

d1b14dc18bc7a72d.png

Click Check my progress below. A green check confirms you're on track.

Get a success response over External IP of VM instance

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

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

Install the Ops agents

The Ops Agent collects logs and metrics on Compute Engine instances, sending your logs to Cloud Logging and your metrics to Cloud Monitoring.

  1. Run the Monitoring agent install script command in the SSH terminal of your VM instance to install the Cloud Monitoring agent.

curl -sSO https://dl.google.com/cloudagents/add-google-cloud-ops-agent-repo.sh sudo bash add-google-cloud-ops-agent-repo.sh --also-install
  1. Verify that the agent is working as expected:

sudo systemctl status google-cloud-ops-agent"*"

Create an uptime check

Uptime checks verify that a resource is always accessible. For practice, create an uptime check to verify your VM is up.

  1. In the Cloud Console, in the left menu, click Uptime checks, and then click +Create Uptime Check.

uptime.png

  1. Set the following fields:

Title: Lamp Uptime Check, then click Next.

Protocol: HTTP

Resource Type: Instance

Applies to: Single, lamp-1-vm

Path: leave at default

Check Frequency: 1 min

  1. Click on Next to leave the other details to default and click Test to verify that your uptime check can connect to the resource.

uptimecheck.png

  1. When you see a green check mark everything can connect. Click Create.

The uptime check you configured takes a while for it to become active. Continue with the lab, you'll check for results later. While you wait, create an alerting policy for a different resource.

Create an alerting policy

Use Cloud Monitoring to create one or more alerting policies.

  1. In the left menu, click Alerting, and then click +Create Policy.
Note: If required, click Try It! to use the updated alert creation flow.
  1. Click on Select a metric dropdown. Disable the Show only active resources & metrics.

  2. Type Network traffic in filter by resource and metric name and click on VM instance > interface. Select Network traffic (agent.googleapis.com/interface/traffic) and click Apply. Leave all other fields at the default value.

select_metric.png

  1. Click Next.

  2. Set the Threshold position to Above threshold, Threshold value to 500 and Advanced Options > Retest window to 1 min. Click Next.

  3. Click on drop down arrow next to Notification Channels, then click on Manage Notification Channels.

email.png

A Notification channels page will open in new tab.

  1. Scroll down the page and click on ADD NEW for Email.

add_email.png

  1. In Create Email Channel dialog box, enter your personal email address in the Email Address field and a Display name.

  2. Click on Save.

  3. Go back to the previous Create alerting policy tab.

  4. Click on Notification Channels again, then click on the Refresh icon to get the display name you mentioned in the previous step.

  5. Click on Notification Channels again if necessary, select your Display name and click OK.

  6. Add a message in documentation, which will be included in the emailed alert.

  7. Mention the Alert name as Inbound Traffic Alert.

  8. Click Next.

  9. Review the alert and click Create Policy.

You've created an alert! While you wait for the system to trigger an alert, create a dashboard and chart, and then check out Cloud Logging.

Click Check my progress below. A green check confirms you're on track.

Create an uptime check and alerting policy

Create a dashboard and chart

You can display the metrics collected by Cloud Monitoring in your own charts and dashboards. In this section you create the charts for the lab metrics and a custom dashboard.

  1. In the left menu select Dashboards, and then +Create Dashboard.

  2. Name the dashboard Cloud Monitoring LAMP Qwik Start Dashboard.

Add the first chart

  1. Click Line option in Chart library.

  2. Name the chart title CPU Load.

  3. Click on Resource & Metric dropdown. Disable the Show only active resources & metrics.

  4. Type CPU load (1m) in filter by resource and metric name and click on VM instance > Cpu. Select CPU load (1m) and click Apply. Leave all other fields at the default value. Refresh the tab to view the graph.

Add the second chart

  1. Click + Add Chart and select Line option in Chart library.

  2. Name this chart Received Packets.

  3. Click on Resource & Metric dropdown. Disable the Show only active resources & metrics.

  4. Type Received packets in filter by resource and metric name and click on VM instance > Instance. Select Received packets and click Apply. Refresh the tab to view the graph.

  5. Leave the other fields at their default values. You see the chart data.

Chart.png

View your logs

Cloud Monitoring and Cloud Logging are closely integrated. Check out the logs for your lab.

  1. Select Navigation menu > Logging > Logs Explorer.

  2. Select the logs you want to see, in this case, you select the logs for the lamp-1-vm instance you created at the start of this lab:

  • Click on Resource.

Resource.png

  • Select VM Instance > lamp-1-vm in the Resource drop-down menu.

lamp_1_vm.png

  • Click Apply.
  • Leave the other fields with their default values.
  • Click the Stream logs.

Stream.png

You see the logs for your VM instance:

Stream2.png

Check out what happens when you start and stop the VM instance.

To best see how Cloud Monitoring and Cloud Logging reflect VM instance changes, make changes to your instance in one browser window and then see what happens in the Cloud Monitoring, and then Cloud Logging windows.

  1. Open the Compute Engine window in a new browser window. Select Navigation menu > Compute Engine, right-click VM instances > Open link in new window.

  2. Move the Logs Viewer browser window next to the Compute Engine window. This makes it easier to view how changes to the VM are reflected in the logs

  3. In the Compute Engine window, select the lamp-1-vm instance, click the three vertical dots at the top of the screen and then click Stop, and then confirm to stop the instance.

stop-vm.png

It takes a few minutes for the instance to stop.

  1. Watch in the Logs View tab for when the VM is stopped.

Stop.png

  1. In the VM instance details window, click the three vertical dots at the top of the screen and then click Start/resume, and then confirm. It will take a few minutes for the instance to re-start. Watch the log messages to monitor the start up.

Start.png

Check the uptime check results and triggered alerts

  1. In the Cloud Logging window, select Navigation menu > Monitoring > Uptime checks. This view provides a list of all active uptime checks, and the status of each in different locations.

You will see Lamp Uptime Check listed. Since you have just restarted your instance, the regions are in a failed status. It may take up to 5 minutes for the regions to become active. Reload your browser window as necessary until the regions are active.

  1. Click the name of the uptime check, Lamp Uptime Check.

Since you have just restarted your instance, it may take some minutes for the regions to become active. Reload your browser window as necessary.

Check if alerts have been triggered

  1. In the left menu, click Alerting.

  2. You see incidents and events listed in the Alerting window.

  3. Check your email account. You should see Cloud Monitoring Alerts.

(Optional) Remove your alerting policy

If you set up an email alert as part of your alerting policy, there is a chance that you will receive a few emails about your resources even after the lab is completed.

To avoid this, remove the alerting policy before you complete your lab.

Congratulations!

You have successfully set up and monitored a VM with Cloud Monitoring.

Finish your Quest

This self-paced lab is part of the Google Cloud's Operations Suite, Baseline: Infrastructure, Cloud Engineering, Cloud Development, and Optimizing Your Google Cloud Costs quests. A quest is a series of related labs that form a learning path. Completing this quest earns you the badge above, to recognize your achievement. You can make your badge public and link to them in your online resume or social media account. Enroll in a quest and get immediate completion credit if you've taken this lab. See other available quests.

Take your next lab

This lab is also part of a series of labs called Qwik Starts. These labs are designed to give you a little taste of the many features available with Google Cloud. Search for "Qwik Starts" in Cloud Skills Boost to find the next lab you'd like to take!

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.

Lab last tested Aug 5, 2022

Manual last updated Aug 5, 2022

Copyright 2022 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.