Log Explorer and queries in GCP - Mini Project: Build & Apply

Log Explorer and queries

📖 Scenario: You are a cloud administrator for a company using Google Cloud Platform (GCP). You want to learn how to use the Log Explorer tool to find specific logs from your cloud resources. This will help you quickly identify issues and monitor your applications.

🎯 Goal: Build a simple Log Explorer query step-by-step to filter logs from a specific GCP project and resource type, then refine the query to find error logs only.

📋 What You'll Learn

Create a basic log query filtering by project ID

Add a filter for a specific resource type

Refine the query to show only error severity logs

Complete the query with a time range filter

💡 Why This Matters

🌍 Real World

Cloud administrators use Log Explorer queries to monitor and troubleshoot cloud resources efficiently.

💼 Career

Knowing how to write and refine log queries is essential for roles like Cloud Engineer, Site Reliability Engineer, and DevOps Specialist.

1

Create a basic log query filtering by project ID

Write a Log Explorer query that filters logs from the project with ID my-sample-project. Use the exact syntax resource.project_id="my-sample-project".

GCP

# Your code here

Hint

Start by specifying the project ID in your query using resource.project_id.

2

Add a filter for a specific resource type

Extend the query to filter logs from the resource type gce_instance. Add resource.type="gce_instance" to the existing query using AND.

GCP

resource.project_id="my-sample-project"
# Add resource type filter below

Hint

Use AND to combine filters for project ID and resource type.

3

Refine the query to show only error severity logs

Add a filter to show only logs with severity ERROR. Use severity="ERROR" combined with AND in your query.

GCP

resource.project_id="my-sample-project" AND resource.type="gce_instance"
# Add severity filter below

Hint

Filter logs by severity to focus on errors only.

4

Complete the query with a time range filter

Add a time range filter to show logs from the last 24 hours. Use timestamp >= "2023-01-01T00:00:00Z" format with AND. Replace the date with the exact ISO 8601 timestamp for 24 hours ago, for example timestamp >= "2023-01-01T00:00:00Z".

GCP

resource.project_id="my-sample-project" AND resource.type="gce_instance" AND severity="ERROR"
# Add timestamp filter below

Hint

Use the timestamp field to filter logs by time range in ISO 8601 format.

Practice

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

easy

A. To manage user permissions

B. To create virtual machines

C. To search and filter logs generated by cloud resources

D. To deploy applications automatically

Solution

1. Step 1: Understand Log Explorer's role

   Log Explorer is designed to help users find specific log entries by searching and filtering logs.

2. Step 2: Compare with other options

   Creating VMs, managing permissions, and deploying apps are done by other GCP services, not Log Explorer.

3. Final Answer:

   To search and filter logs generated by cloud resources -> Option C

4. Quick Check:

   Log Explorer = Search and filter logs [OK]

Hint: Log Explorer is for logs, not for VMs or permissions [OK]

Common Mistakes:

• Confusing Log Explorer with Compute Engine
• Thinking it manages user roles
• Assuming it deploys apps automatically

2. Which of the following is the correct syntax to filter logs for entries where the severity is ERROR in Log Explorer?

easy

A. severity = "ERROR"

B. severity == "ERROR"

C. severity="ERROR"

D. severity = ERROR

Solution

1. Step 1: Recall Log Explorer filter syntax

   Log Explorer uses single equals (=) with quotes around string values.

2. Step 2: Check each option

   severity = "ERROR" uses correct syntax: single equals (=) with quotes around string values. Omitting quotes, using double equals, or missing spaces around the operator are incorrect.

3. Final Answer:

   severity = "ERROR" -> Option A

4. Quick Check:

   Use = and quotes for strings [OK]

Hint: Use = and quotes for string filters in Log Explorer [OK]

Common Mistakes:

• Using == instead of =
• Omitting quotes around string values
• Missing spaces around =

3. Given the query resource.type = "gce_instance" AND severity = "WARNING", what kind of log entries will this return?

medium

A. All logs from any resource with severity WARNING

B. Logs from Google Compute Engine instances with any severity

C. Logs from any resource with severity ERROR or WARNING

D. Logs from Google Compute Engine instances with severity WARNING

Solution

1. Step 1: Analyze the query conditions

   The query filters logs where resource.type equals "gce_instance" AND severity equals "WARNING".

2. Step 2: Understand the AND operator effect

   Both conditions must be true, so logs must be from GCE instances and have WARNING severity.

3. Final Answer:

   Logs from Google Compute Engine instances with severity WARNING -> Option D

4. Quick Check:

   AND means both conditions true [OK]

Hint: AND means both filters must match logs [OK]

Common Mistakes:

• Thinking OR is used instead of AND
• Ignoring resource.type filter
• Assuming severity includes ERROR

4. You wrote this query in Log Explorer: resource.type = "gce_instance" OR severity = "ERROR" AND timestamp > "2024-01-01T00:00:00Z". Why might this not return expected results?

medium

A. Because AND has higher precedence than OR, so the query groups incorrectly

B. Because timestamp filter syntax is invalid

C. Because severity cannot be combined with resource.type

D. Because OR operator is not supported in Log Explorer

Solution

1. Step 1: Understand operator precedence in Log Explorer

   AND has higher precedence than OR, so the query is read as resource.type = "gce_instance" OR (severity = "ERROR" AND timestamp > ...).

2. Step 2: Identify grouping issue

   This means logs with resource.type "gce_instance" are included regardless of timestamp or severity, which may not be intended.

3. Final Answer:

   Because AND has higher precedence than OR, so the query groups incorrectly -> Option A

4. Quick Check:

   AND binds tighter than OR [OK]

Hint: Use parentheses to group AND/OR conditions correctly [OK]

Common Mistakes:

• Ignoring operator precedence
• Assuming OR has higher precedence
• Thinking OR is unsupported

5. You want to find logs from Compute Engine instances that either have severity ERROR or occurred after March 1, 2024. Which query correctly expresses this in Log Explorer?

hard

A. (resource.type = "gce_instance" AND severity = "ERROR") OR timestamp > "2024-03-01T00:00:00Z"

B. resource.type = "gce_instance" AND (severity = "ERROR" OR timestamp > "2024-03-01T00:00:00Z")

C. resource.type = "gce_instance" OR severity = "ERROR" AND timestamp > "2024-03-01T00:00:00Z"

D. resource.type = "gce_instance" AND severity = "ERROR" OR timestamp > "2024-03-01T00:00:00Z"

Solution

1. Step 1: Understand the requirement

   We want logs from GCE instances where severity is ERROR or logs from GCE instances after March 1, 2024.

2. Step 2: Analyze each option's logic

   resource.type = "gce_instance" AND (severity = "ERROR" OR timestamp > "2024-03-01T00:00:00Z") groups severity and timestamp with OR inside parentheses combined with resource.type using AND, matching the requirement.

3. Step 3: Check other options

   (resource.type = "gce_instance" AND severity = "ERROR") OR timestamp > "2024-03-01T00:00:00Z" includes logs after March 1 from any resource, not just GCE instances. The remaining options lack parentheses, causing wrong precedence.

4. Final Answer:

   resource.type = "gce_instance" AND (severity = "ERROR" OR timestamp > "2024-03-01T00:00:00Z") -> Option B

5. Quick Check:

   Use parentheses to combine OR inside AND [OK]

Hint: Use parentheses to group OR inside AND correctly [OK]

Common Mistakes:

• Missing parentheses causing wrong logic
• Including timestamp filter outside resource.type scope
• Assuming OR has same precedence as AND