Cloud Monitoring overview in GCP - Commands & Configuration

Introduction

Cloud Monitoring helps you watch your applications and services in the cloud. It collects data about how your systems are working and shows it in easy-to-understand charts and alerts. This helps you find and fix problems quickly.

When you want to see how much CPU or memory your cloud servers are using.

When you need to get alerts if your website goes down or slows down.

When you want to track the number of users visiting your app over time.

When you want to check if your cloud database is responding fast enough.

When you want to create dashboards to share system health with your team.

Commands

This command creates a new monitoring dashboard in Google Cloud using the settings defined in the dashboard.json file. Dashboards help you visualize metrics in one place.

Terminal

gcloud monitoring dashboards create --config-from-file=dashboard.json

Expected Output

Created dashboard: projects/my-project/dashboards/1234567890abcdef

→

--config-from-file - Specifies the JSON file that contains the dashboard configuration.

This command lists all available metrics you can monitor in your Google Cloud project. It helps you find what data you can track.

Terminal

gcloud monitoring metrics list

Expected Output

NAME

compute.googleapis.com/instance/cpu/utilization

compute.googleapis.com/instance/disk/read_bytes_count

compute.googleapis.com/instance/network/received_bytes_count

...

This command creates an alerting policy that sends notifications when CPU usage on a virtual machine goes above 80% for more than 60 seconds.

Terminal

gcloud monitoring policies create --notification-channels=projects/my-project/notificationChannels/1234567890abcdef --condition-display-name="High CPU Usage" --condition-filter="metric.type=\"compute.googleapis.com/instance/cpu/utilization\" AND resource.type=\"gce_instance\"" --condition-threshold-value=0.8 --condition-comparison=COMPARISON_GT --condition-duration=60s

Expected Output

Created alerting policy: projects/my-project/alertPolicies/abcdef1234567890

→

--notification-channels - Specifies where to send alerts, like email or SMS.

→

--condition-filter - Defines which metric and resource to watch.

→

--condition-threshold-value - Sets the value that triggers the alert.

This command shows all the monitoring dashboards you have created in your project. It helps you check your visual monitoring setups.

Terminal

gcloud monitoring dashboards list

Expected Output

NAME                                    DISPLAY_NAME

projects/my-project/dashboards/1234567890abcdef  My CPU Dashboard

projects/my-project/dashboards/abcdef1234567890  Network Stats

Key Concept

If you remember nothing else from this pattern, remember: Cloud Monitoring collects and shows data about your cloud resources so you can keep them healthy and fix problems fast.

Common Mistakes

Not specifying the correct project or resource in commands.

The commands will apply to the wrong project or resource, so you won't see or affect the data you want.

Always check and set the correct project with 'gcloud config set project my-project' before running monitoring commands.

Creating alert policies without notification channels.

Alerts will trigger but no one will be notified, so problems can go unnoticed.

Create and specify notification channels like email or SMS before creating alert policies.

Summary

Use 'gcloud monitoring dashboards create' with a JSON file to set up visual dashboards.

List available metrics with 'gcloud monitoring metrics list' to know what you can track.

Create alert policies with 'gcloud monitoring policies create' to get notified about issues.

Check your dashboards anytime with 'gcloud monitoring dashboards list' to monitor system health.

Practice

1. What is the main purpose of Cloud Monitoring in Google Cloud Platform?

easy

A. To watch and track the health and performance of cloud resources

B. To create virtual machines automatically

C. To store large amounts of data securely

D. To manage user permissions and roles

Solution

1. Step 1: Understand Cloud Monitoring's role

   Cloud Monitoring is designed to observe and report on the status and performance of cloud resources.

2. Step 2: Compare options with this role

   Options B, C, and D describe other services like Compute Engine, Cloud Storage, and IAM, not monitoring.

3. Final Answer:

   To watch and track the health and performance of cloud resources -> Option A

4. Quick Check:

   Cloud Monitoring = watch cloud health [OK]

Hint: Monitoring means watching resource health and performance [OK]

Common Mistakes:

• Confusing monitoring with storage or VM creation
• Thinking monitoring manages user access
• Assuming monitoring creates resources automatically

2. Which command correctly lists all alert policies using the gcloud tool?

easy

A. gcloud alert-policies show

B. gcloud monitoring alerts list

C. gcloud monitoring alert-policies list

D. gcloud monitoring policies get

Solution

1. Step 1: Recall gcloud command structure for alert policies

   The correct command to list alert policies is under 'monitoring alert-policies list'.

2. Step 2: Verify each option's correctness

   gcloud monitoring alert-policies list matches the correct syntax. Options A, B, and D use incorrect verbs or resource names.

3. Final Answer:

   gcloud monitoring alert-policies list -> Option C

4. Quick Check:

   List alert policies = gcloud monitoring alert-policies list [OK]

Hint: Use 'gcloud monitoring alert-policies list' to see alerts [OK]

Common Mistakes:

• Using 'alerts' instead of 'alert-policies'
• Using 'show' instead of 'list' to list policies
• Mixing command verbs and resource names

3. What will be the output of this command?

gcloud monitoring metrics list --filter="metric.type=compute.googleapis.com/instance/cpu/utilization" --limit=1

medium

A. Deletes the CPU utilization metric

B. Shows an error because the filter syntax is wrong

C. Lists all metrics without filtering

D. Lists one metric descriptor for CPU utilization of Compute Engine instances

Solution

1. Step 1: Understand the command components

   The command lists metric descriptors filtered by CPU utilization metric type, limiting output to one.

2. Step 2: Analyze expected output

   The output will show one metric descriptor matching the filter. No deletion or error occurs.

3. Final Answer:

   Lists one metric descriptor for CPU utilization of Compute Engine instances -> Option D

4. Quick Check:

   Filter + limit = one matching metric listed [OK]

Hint: Filter with --filter and limit results with --limit [OK]

Common Mistakes:

• Assuming filter syntax is invalid
• Expecting all metrics without filter
• Confusing list with delete command

4. You tried to create an alert policy with this command:

gcloud monitoring alert-policies create --notification-channels=1234567890 --condition-display-name="High CPU" --condition-filter="metric.type=compute.googleapis.com/instance/cpu/utilization" --condition-threshold-value=0.8

But it failed. What is the likely error?

medium

A. Missing required flag --condition-aggregations

B. Notification channel ID is invalid or missing

C. Condition filter syntax is incorrect

D. Threshold value must be a string, not a number

Solution

1. Step 1: Check notification channel usage

   The notification channel ID must be a valid existing channel; '1234567890' is likely a placeholder or invalid.

2. Step 2: Verify other flags

   Flags like condition filter and threshold value are syntactically correct; aggregation is optional.

3. Final Answer:

   Notification channel ID is invalid or missing -> Option B

4. Quick Check:

   Invalid notification channel causes failure [OK]

Hint: Check notification channel IDs exist before using [OK]

Common Mistakes:

• Assuming aggregation is always required
• Misformatting condition filter
• Using wrong data type for threshold

5. You want to create a dashboard that shows CPU utilization and memory usage for your Compute Engine instances. Which steps should you follow?

hard

A. Use Cloud Console to create a dashboard, add widgets for CPU and memory metrics, then save

B. Run gcloud commands to create a dashboard and add metrics in one command

C. Create alert policies for CPU and memory, then dashboards are created automatically

D. Use Cloud Storage to upload a JSON file with dashboard configuration

Solution

1. Step 1: Understand dashboard creation process

   Dashboards are created in Cloud Console by adding widgets for desired metrics.

2. Step 2: Evaluate options for dashboard creation

   Use Cloud Console to create a dashboard, add widgets for CPU and memory metrics, then save describes the correct manual process. Run gcloud commands to create a dashboard and add metrics in one command is incorrect as gcloud does not support full dashboard creation in one command. Create alert policies for CPU and memory, then dashboards are created automatically confuses alerts with dashboards. Use Cloud Storage to upload a JSON file with dashboard configuration misuses Cloud Storage.

3. Final Answer:

   Use Cloud Console to create a dashboard, add widgets for CPU and memory metrics, then save -> Option A

4. Quick Check:

   Dashboards made via Console with widgets [OK]

Hint: Create dashboards in Console by adding metric widgets [OK]

Common Mistakes:

• Thinking gcloud can create dashboards fully
• Confusing alert policies with dashboards
• Uploading dashboard configs to Cloud Storage