Log Analytics workspace in Azure - Mini Project: Build & Apply

Create an Azure Log Analytics Workspace

📖 Scenario: You are setting up monitoring for your cloud resources. To collect and analyze logs, you need to create a Log Analytics workspace in Azure.

🎯 Goal: Build an Azure Log Analytics workspace using Infrastructure as Code with exact configuration values.

📋 What You'll Learn

Create a resource group named monitoring-rg

Create a Log Analytics workspace named monitoring-workspace

Set the workspace location to eastus

Set the workspace SKU to PerGB2018

Enable retention of logs for 30 days

💡 Why This Matters

🌍 Real World

Log Analytics workspaces collect and analyze logs from Azure resources, helping teams monitor and troubleshoot cloud environments.

💼 Career

Cloud engineers and DevOps professionals often create and manage Log Analytics workspaces to enable centralized logging and monitoring.

1

Create the resource group

Create a resource group named monitoring-rg in the eastus location.

Azure

# Your code here to create resource group monitoring-rg in eastus

Hint

Use the azurerm_resource_group resource with the exact name monitoring_rg.

2

Define the Log Analytics workspace configuration

Create a variable called workspace_name and set it to monitoring-workspace.

Azure

resource "azurerm_resource_group" "monitoring_rg" {
  name     = "monitoring-rg"
  location = "eastus"
}

# Define workspace_name variable
# Your code here

Hint

Use a Terraform variable named workspace_name with the default value monitoring-workspace.

3

Create the Log Analytics workspace resource

Create an azurerm_log_analytics_workspace resource named log_analytics using the resource group monitoring_rg, workspace name from var.workspace_name, location eastus, SKU PerGB2018, and retention in days set to 30.

Azure

resource "azurerm_resource_group" "monitoring_rg" {
  name     = "monitoring-rg"
  location = "eastus"
}

variable "workspace_name" {
  default = "monitoring-workspace"
}

# Create Log Analytics workspace resource
# Your code here

Hint

Use the azurerm_log_analytics_workspace resource with the exact name log_analytics.

4

Finalize the Log Analytics workspace configuration

Add the tags block to the azurerm_log_analytics_workspace resource with a tag environment set to production.

Azure

resource "azurerm_resource_group" "monitoring_rg" {
  name     = "monitoring-rg"
  location = "eastus"
}

variable "workspace_name" {
  default = "monitoring-workspace"
}

resource "azurerm_log_analytics_workspace" "log_analytics" {
  name                = var.workspace_name
  location            = azurerm_resource_group.monitoring_rg.location
  resource_group_name = azurerm_resource_group.monitoring_rg.name
  sku                 = "PerGB2018"
  retention_in_days   = 30

  # Add tags block here
  # Your code here
}

Hint

Add a tags block inside the workspace resource with the key environment and value production.

Practice

1. What is the main purpose of a Log Analytics workspace in Azure?

easy

A. To provide a user interface for managing Azure subscriptions

B. To host virtual machines and databases

C. To collect and store logs and metrics from cloud resources

D. To create backups of your data automatically

Solution

1. Step 1: Understand the role of Log Analytics workspace

   A Log Analytics workspace is designed to gather and keep logs and metrics from various Azure resources.

2. Step 2: Compare with other Azure services

   Hosting VMs, managing subscriptions, or backups are handled by other Azure services, not Log Analytics workspace.

3. Final Answer:

   To collect and store logs and metrics from cloud resources -> Option C

4. Quick Check:

   Log Analytics workspace = log and metric collection [OK]

Hint: Logs and metrics collection is the key function [OK]

Common Mistakes:

• Confusing Log Analytics workspace with VM hosting
• Thinking it manages subscriptions
• Assuming it handles backups

2. Which of the following is the correct way to specify the retention period when creating a Log Analytics workspace in Azure CLI?

easy

A. --retention 30

B. --retention-time 30

C. --retention-days 30

D. --retention-period 30

Solution

1. Step 1: Recall Azure CLI parameter for retention

   The correct parameter to set retention period in days is --retention-time.

2. Step 2: Verify other options

   Options like --retention, --retention-days, or --retention-period are not valid Azure CLI parameters for this setting.

3. Final Answer:

   --retention-time 30 -> Option B

4. Quick Check:

   Retention period uses --retention-time [OK]

Hint: Retention period uses --retention-time flag [OK]

Common Mistakes:

• Using incorrect parameter names
• Confusing retention-time with retention-days
• Omitting the unit (days)

3. Given the following Azure CLI command to create a Log Analytics workspace, what will be the retention period in days?

az monitor log-analytics workspace create --resource-group MyGroup --workspace-name MyWorkspace --location eastus --retention-time 45

medium

A. 45 days

B. 30 days

C. 90 days

D. Default retention period

Solution

1. Step 1: Identify the retention parameter in the command

   The command uses --retention-time 45, which sets the retention period explicitly to 45 days.

2. Step 2: Understand retention period effect

   This means logs and metrics will be kept for 45 days before automatic deletion.

3. Final Answer:

   45 days -> Option A

4. Quick Check:

   --retention-time 45 means 45 days retention [OK]

Hint: Look for --retention-time value in command [OK]

Common Mistakes:

• Assuming default retention instead of specified
• Confusing retention-time with other parameters
• Ignoring the explicit retention-time flag

4. You tried to create a Log Analytics workspace with this command but got an error:

az monitor log-analytics workspace create --resource-group MyGroup --workspace-name MyWorkspace --location eastus --retention 30

What is the likely cause of the error?

medium

A. The location eastus is not supported

B. The resource group MyGroup does not exist

C. The workspace name is too short

D. The parameter --retention is invalid; it should be --retention-time

Solution

1. Step 1: Check the parameter names in the command

   The command uses --retention, which is not a valid parameter for retention period in Azure CLI.

2. Step 2: Identify the correct parameter

   The correct parameter to specify retention days is --retention-time. Using the wrong parameter causes a syntax error.

3. Final Answer:

   The parameter --retention is invalid; it should be --retention-time -> Option D

4. Quick Check:

   Use --retention-time, not --retention [OK]

Hint: Retention parameter must be --retention-time [OK]

Common Mistakes:

• Using --retention instead of --retention-time
• Assuming location eastus is invalid
• Ignoring resource group existence

5. You want to create a Log Analytics workspace that stores logs for 60 days and is located in the same region as your Azure virtual machines in westus2. Which Azure CLI command correctly achieves this?

hard

A. az monitor log-analytics workspace create --resource-group MyGroup --workspace-name MyWorkspace --location westus2 --retention-time 60

B. az monitor log-analytics workspace create --resource-group MyGroup --workspace-name MyWorkspace --location eastus --retention-time 60

C. az monitor log-analytics workspace create --resource-group MyGroup --workspace-name MyWorkspace --location westus2 --retention 60

D. az monitor log-analytics workspace create --resource-group MyGroup --workspace-name MyWorkspace --location westus2

Solution

1. Step 1: Match location with VM region

   The workspace must be in westus2 to match the VM region.

2. Step 2: Set retention period correctly

   The retention period must be 60 days, so use --retention-time 60.

3. Step 3: Verify command correctness

   The command az monitor log-analytics workspace create --resource-group MyGroup --workspace-name MyWorkspace --location westus2 --retention-time 60 uses the correct location and retention parameter. The command with --location eastus uses wrong location. The command with --retention 60 uses invalid retention parameter. The command without retention omits the period setting.

4. Final Answer:

   az monitor log-analytics workspace create --resource-group MyGroup --workspace-name MyWorkspace --location westus2 --retention-time 60 -> Option A

5. Quick Check:

   Location and retention-time must match requirements [OK]

Hint: Match location and use --retention-time for retention [OK]

Common Mistakes:

• Using wrong location
• Using --retention instead of --retention-time
• Omitting retention period