Operational excellence pillar in Azure - Commands & Configuration

Introduction

Operational excellence helps you run your cloud systems smoothly and improve them over time. It focuses on monitoring, automation, and responding quickly to problems to keep services reliable and efficient.

When you want to track how well your cloud applications are performing and spot issues early.

When you need to automate routine tasks to reduce manual work and errors.

When you want to create a culture of continuous improvement in your cloud operations.

When you need to respond quickly to incidents to minimize downtime.

When you want to document and share best practices for running your cloud environment.

Commands

This command creates a Log Analytics workspace in Azure Monitor to collect and analyze logs and metrics from your cloud resources.

Terminal

az monitor log-analytics workspace create --resource-group example-rg --workspace-name example-workspace --location eastus

Expected Output

{

  "customerId": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",

  "location": "eastus",

  "name": "example-workspace",

  "resourceGroup": "example-rg",

  "sku": {

    "name": "PerGB2018"

  },

  "type": "Microsoft.OperationalInsights/workspaces"

}

→

--resource-group - Specifies the Azure resource group to create the workspace in

→

--workspace-name - Names the Log Analytics workspace

→

--location - Sets the Azure region for the workspace

This command enables diagnostic logs and metrics for a virtual machine and sends them to the Log Analytics workspace for monitoring.

Terminal

az monitor diagnostic-settings create --resource /subscriptions/00000000-0000-0000-0000-000000000000/resourceGroups/example-rg/providers/Microsoft.Compute/virtualMachines/example-vm --name example-diagnostics --workspace example-workspace --logs '[{"category": "Administrative", "enabled": true}]' --metrics '[{"category": "AllMetrics", "enabled": true}]'

Expected Output

{

  "id": "/subscriptions/00000000-0000-0000-0000-000000000000/resourceGroups/example-rg/providers/Microsoft.Compute/virtualMachines/example-vm/providers/microsoft.insights/diagnosticSettings/example-diagnostics",

  "name": "example-diagnostics",

  "type": "Microsoft.Insights/diagnosticSettings"

}

→

--resource - Specifies the resource to monitor

→

--workspace - Sends logs and metrics to this Log Analytics workspace

→

--logs - Enables specific log categories

This command creates an alert rule that triggers when the average CPU usage of the virtual machine goes above 80%, helping you respond quickly to performance issues.

Terminal

az monitor metrics alert create --name example-alert --resource-group example-rg --scopes /subscriptions/00000000-0000-0000-0000-000000000000/resourceGroups/example-rg/providers/Microsoft.Compute/virtualMachines/example-vm --condition "avg Percentage CPU > 80" --description "Alert when CPU usage is high" --action example-action-group

Expected Output

{

  "id": "/subscriptions/00000000-0000-0000-0000-000000000000/resourceGroups/example-rg/providers/microsoft.insights/metricAlerts/example-alert",

  "name": "example-alert",

  "type": "Microsoft.Insights/metricAlerts"

}

→

--scopes - Defines which resource the alert monitors

→

--condition - Sets the metric condition that triggers the alert

→

--action - Specifies the action group to notify when alert fires

This command creates an action group that defines who gets notified when alerts happen, such as sending emails to the operations team.

Terminal

az monitor action-group create --name example-action-group --resource-group example-rg --short-name exag --email-receivers name=OpsTeam email=[e-mail]

Expected Output

{

  "id": "/subscriptions/00000000-0000-0000-0000-000000000000/resourceGroups/example-rg/providers/microsoft.insights/actionGroups/example-action-group",

  "name": "example-action-group",

  "type": "Microsoft.Insights/actionGroups"

}

→

--short-name - Sets a short name for the action group

→

--email-receivers - Defines email recipients for alerts

Key Concept

If you remember nothing else from this pattern, remember: monitoring and automated alerts help you catch and fix problems before they affect users.

Common Mistakes

Not linking diagnostic settings to a Log Analytics workspace

Without linking, logs and metrics are not collected centrally, so you cannot analyze or alert on them.

Always specify the --workspace flag when creating diagnostic settings to send data to a Log Analytics workspace.

Creating alerts without action groups

Alerts will trigger but no one will be notified, so issues may go unnoticed.

Create and attach an action group to alerts to ensure notifications reach the right people.

Using vague alert conditions

Alerts may fire too often or miss important issues, causing alert fatigue or blind spots.

Define clear, specific metric conditions that reflect real operational thresholds.

Summary

Create a Log Analytics workspace to collect monitoring data.

Enable diagnostic settings on resources to send logs and metrics to the workspace.

Set up alerts with clear conditions and link them to action groups for notifications.

Use these tools to monitor your cloud environment and respond quickly to issues.

Practice

1. What is the main goal of the Operational excellence pillar in Azure cloud?

easy

A. To run cloud systems smoothly and improve them continuously

B. To reduce cloud costs by shutting down services

C. To secure cloud data with encryption only

D. To build new cloud applications from scratch

Solution

1. Step 1: Understand the definition of operational excellence

   Operational excellence focuses on running cloud systems smoothly and improving them over time.

2. Step 2: Compare options with this definition

   Only To run cloud systems smoothly and improve them continuously matches this goal. Other options focus on cost, security, or development, which are different pillars.

3. Final Answer:

   To run cloud systems smoothly and improve them continuously -> Option A

4. Quick Check:

   Operational excellence = smooth running and improvement [OK]

Hint: Operational excellence means smooth running and improvement [OK]

Common Mistakes:

• Confusing operational excellence with security or cost management
• Thinking it only means fixing problems, not improving
• Assuming it is about building new apps

2. Which Azure service is primarily used for monitoring and alerting to support operational excellence?

easy

A. Azure DevOps

B. Azure Monitor

C. Azure Blob Storage

D. Azure Functions

Solution

1. Step 1: Identify the service for monitoring and alerting

   Azure Monitor is designed to collect, analyze, and act on telemetry data from cloud resources.

2. Step 2: Eliminate other options

   Azure DevOps is for development pipelines, Blob Storage is for data storage, and Functions is for serverless compute, so they don't focus on monitoring.

3. Final Answer:

   Azure Monitor -> Option B

4. Quick Check:

   Monitoring and alerting = Azure Monitor [OK]

Hint: Monitoring and alerting in Azure? Think Azure Monitor [OK]

Common Mistakes:

• Choosing Azure DevOps for monitoring
• Confusing storage services with monitoring
• Selecting compute services instead of monitoring tools

3. Consider this Azure CLI command to create an alert rule:

az monitor metrics alert create --name HighCPUAlert --resource-group MyGroup --scopes /subscriptions/123/resourceGroups/MyGroup/providers/Microsoft.Compute/virtualMachines/MyVM --condition "avg Percentage CPU > 80" --description "Alert when CPU is high"

What will happen when the average CPU usage goes above 80%?

medium

A. The CPU usage will be throttled to 80%

B. The virtual machine will automatically shut down

C. An alert named HighCPUAlert will trigger notifying the user

D. Nothing happens because the command syntax is incorrect

Solution

1. Step 1: Understand the alert creation command

   The command creates a metric alert named HighCPUAlert that triggers when average CPU usage exceeds 80% on the specified VM.

2. Step 2: Analyze the effect of the alert

   Alerts notify users or systems but do not automatically shut down or throttle resources. The command syntax is correct.

3. Final Answer:

   An alert named HighCPUAlert will trigger notifying the user -> Option C

4. Quick Check:

   Metric alert triggers notification, not shutdown [OK]

Hint: Alerts notify; they don't auto-shutdown or throttle [OK]

Common Mistakes:

• Thinking alerts auto-shutdown resources
• Assuming alerts change resource behavior automatically
• Believing the command has syntax errors

4. You wrote this Azure Resource Manager (ARM) template snippet to enable diagnostics:

{
  "type": "Microsoft.Insights/diagnosticSettings",
  "name": "myDiagnostics",
  "properties": {
    "logs": [
      { "category": "AuditLogs", "enabled": true }
    ],
    "metrics": [
      { "category": "AllMetrics", "enabled": true }
    ]
  }
}

But diagnostics are not enabled after deployment. What is the likely error?

medium

A. The type should be Microsoft.Compute/diagnosticSettings

B. The name property must be omitted

C. The enabled fields should be false to activate diagnostics

D. Missing the scope property to specify the resource to monitor

Solution

1. Step 1: Check required properties for diagnosticSettings

   The scope property is required to specify which resource the diagnostics apply to.

2. Step 2: Validate other properties

   Name is required, enabled should be true to activate, and type is correctly set to Microsoft.Insights/diagnosticSettings.

3. Final Answer:

   Missing the scope property to specify the resource to monitor -> Option D

4. Quick Check:

   Diagnostics need scope property to work [OK]

Hint: Diagnostics require scope property to target resource [OK]

Common Mistakes:

• Forgetting to add scope property
• Setting enabled to false by mistake
• Changing the resource type incorrectly

5. You want to improve operational excellence by automating recovery when a web app becomes unhealthy. Which Azure feature combination best supports this goal?

hard

A. Azure Monitor alerts + Azure Logic Apps to restart the web app automatically

B. Azure Blob Storage + Azure Functions to store logs

C. Azure DevOps pipelines + Azure Key Vault for deployment security

D. Azure Virtual Machines + Azure Backup for manual recovery

Solution

1. Step 1: Identify automation for recovery

   Azure Monitor alerts detect unhealthy states, and Azure Logic Apps can automate actions like restarting the web app.

2. Step 2: Evaluate other options

   Blob Storage and Functions store logs but don't automate recovery; DevOps and Key Vault focus on deployment security; VMs and Backup support manual recovery, not automated.

3. Final Answer:

   Azure Monitor alerts + Azure Logic Apps to restart the web app automatically -> Option A

4. Quick Check:

   Alerts + automation = automated recovery [OK]

Hint: Combine alerts with automation for recovery [OK]

Common Mistakes:

• Choosing storage or deployment tools for recovery automation
• Confusing manual backup with automated recovery
• Ignoring the need for alert-triggered automation