Cloud Logging overview in GCP - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is Cloud Logging in Google Cloud Platform?

Cloud Logging is a service that collects and stores logs from applications and services running on Google Cloud. It helps you monitor, analyze, and troubleshoot your systems.

beginner

What types of logs can Cloud Logging collect?

Cloud Logging collects system logs, application logs, audit logs, and custom logs from Google Cloud resources and applications.

intermediate

How does Cloud Logging help in troubleshooting?

By centralizing logs, Cloud Logging allows you to search, filter, and analyze logs quickly to find errors or unusual behavior in your applications or infrastructure.

intermediate

What is a log sink in Cloud Logging?

A log sink exports logs from Cloud Logging to destinations like Cloud Storage, BigQuery, or Pub/Sub for long-term storage or further analysis.

beginner

How can you view logs in Cloud Logging?

You can view logs using the Google Cloud Console Logs Explorer, the gcloud command-line tool, or the Cloud Logging API.

What is the primary purpose of Cloud Logging?

A To store database backups

B To collect and analyze logs from cloud resources

C To manage user permissions

D To deploy virtual machines

Cloud Logging collects and analyzes logs to help monitor and troubleshoot cloud resources.

Which of the following is NOT a destination for log sinks in Cloud Logging?

A Cloud Functions

B Cloud Storage

C Pub/Sub

D BigQuery

Cloud Functions is not a direct destination for log sinks; sinks export logs to storage or messaging services.

How can you access logs in Cloud Logging?

A All of the above

B gcloud command-line tool

C Cloud Logging API

D Google Cloud Console Logs Explorer

Logs can be accessed via the Console, gcloud CLI, or API.

Which log type records actions taken by users or services in Google Cloud?

A System logs

B Application logs

C Custom logs

D Audit logs

Audit logs record user and service activity for security and compliance.

Why is centralizing logs important in Cloud Logging?

A It deletes old logs automatically

B It makes logs harder to find

C It helps quickly identify and fix issues

D It encrypts logs for security

Centralized logs make it easier to search and analyze data to troubleshoot problems.

Explain what Cloud Logging is and how it helps manage logs in Google Cloud.

Think about how logs from different sources come together in one place.

Describe what a log sink is and why you might use one in Cloud Logging.

Consider what happens when you want to keep logs longer or analyze them elsewhere.

Practice

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

easy

A. To store large files in the cloud

B. To create virtual machines automatically

C. To manage user permissions and roles

D. To collect and display logs from cloud resources in one place

Solution

1. Step 1: Understand Cloud Logging's role

   Cloud Logging collects logs from various cloud resources and shows them centrally.

2. Step 2: Compare options with this role

   Only To collect and display logs from cloud resources in one place describes collecting and displaying logs; others describe unrelated services.

3. Final Answer:

   To collect and display logs from cloud resources in one place -> Option D

4. Quick Check:

   Cloud Logging = centralized log collection [OK]

Hint: Cloud Logging is about logs, not VMs or storage [OK]

Common Mistakes:

• Confusing logging with VM creation
• Thinking it manages user permissions
• Mixing it up with storage services

2. Which of the following is the correct gcloud command to read logs from Cloud Logging?

easy

A. gcloud logging read "resource.type=gae_app"

B. gcloud compute instances list

C. gcloud storage buckets create my-bucket

D. gcloud iam roles describe admin

Solution

1. Step 1: Identify the command for reading logs

   The command to read logs uses 'gcloud logging read' followed by a filter.

2. Step 2: Check each option

   gcloud logging read "resource.type=gae_app" uses 'gcloud logging read' correctly; others relate to compute, storage, or IAM.

3. Final Answer:

   gcloud logging read "resource.type=gae_app" -> Option A

4. Quick Check:

   Log reading command starts with 'gcloud logging read' [OK]

Hint: Look for 'logging read' in the command to find logs [OK]

Common Mistakes:

• Using compute or storage commands instead of logging
• Missing the 'read' keyword after 'logging'
• Confusing IAM commands with logging commands

3. What will be the output of this command?
gcloud logging read "severity=ERROR" --limit 2 --format json

medium

A. A JSON list of the 2 most recent ERROR severity log entries

B. A list of all logs regardless of severity

C. An error message about invalid command syntax

D. A list of 2 logs with severity INFO

Solution

1. Step 1: Understand the command parameters

   The command reads logs filtered by severity=ERROR, limits output to 2 entries, and formats output as JSON.

2. Step 2: Analyze expected output

   It returns a JSON list of the 2 most recent logs with ERROR severity, not all logs or INFO logs.

3. Final Answer:

   A JSON list of the 2 most recent ERROR severity log entries -> Option A

4. Quick Check:

   Filter + limit + JSON format = filtered JSON logs [OK]

Hint: Filter by severity and limit controls output count [OK]

Common Mistakes:

• Ignoring the severity filter
• Expecting all logs instead of limited ones
• Confusing severity levels

4. You run this command but get no output:
gcloud logging read "severity=CRITICAL" --limit 5
What is the most likely reason?

medium

A. The command syntax is incorrect

B. There are no logs with severity CRITICAL in the selected time range

C. The gcloud tool is not installed

D. The limit flag cannot be used with severity filters

Solution

1. Step 1: Check command syntax

   The command syntax is correct; 'gcloud logging read' supports severity filters and limit.

2. Step 2: Consider reasons for no output

   No output usually means no matching logs exist for severity CRITICAL in the default time range.

3. Final Answer:

   There are no logs with severity CRITICAL in the selected time range -> Option B

4. Quick Check:

   No output often means no matching logs [OK]

Hint: No output? Check if logs exist for that severity [OK]

Common Mistakes:

• Assuming syntax error without checking
• Thinking limit flag is invalid with filters
• Ignoring that no logs might exist

5. You want to monitor your app's logs for errors and send alerts only when ERROR or higher severity logs appear. Which Cloud Logging feature should you use?

hard

A. Create a VM instance to process logs locally

B. Use Cloud Storage to save logs and check manually

C. Create a log-based metric with a filter for severity >= ERROR and set up an alerting policy

D. Run gcloud logging read manually every hour

Solution

1. Step 1: Identify monitoring and alerting needs

   You want automatic alerts on ERROR or higher severity logs.

2. Step 2: Match features to needs

   Log-based metrics with filters and alerting policies automate monitoring and alerts.

3. Step 3: Evaluate other options

   Manual checks or storing logs without alerts do not meet the requirement.

4. Final Answer:

   Create a log-based metric with a filter for severity >= ERROR and set up an alerting policy -> Option C

5. Quick Check:

   Log-based metrics + alerts = automated error monitoring [OK]

Hint: Use log-based metrics and alerts for automatic error notifications [OK]

Common Mistakes:

• Relying on manual log checks
• Using storage without alerting
• Creating unrelated VM instances