AKS monitoring with Container Insights in Azure - Step-by-Step Execution

Process Flow - AKS monitoring with Container Insights

Enable Container Insights on AKS Cluster

↓

Deploy Monitoring Agent (via Azure Monitor)

↓

Collect Metrics & Logs from Containers

↓

Send Data to Log Analytics Workspace

↓

Visualize & Analyze in Azure Portal

↓

Set Alerts & Diagnose Issues

This flow shows how enabling Container Insights on AKS deploys agents to collect container data, sends it to Azure Monitor, and allows visualization and alerting.

Execution Sample

Azure

az aks enable-addons --resource-group myResourceGroup --name myAKSCluster --addons monitoring --workspace-resource-id <workspaceResourceId>

This command enables Container Insights monitoring addon on an AKS cluster, linking it to a Log Analytics workspace.

Process Table

Step	Action	Command/Process	Result/Output
1	Enable monitoring addon	az aks enable-addons --resource-group myResourceGroup --name myAKSCluster --addons monitoring --workspace-resource-id <workspaceResourceId>	Monitoring agent deployed to AKS cluster
2	Agent collects data	Container Insights agent runs inside AKS nodes	Metrics and logs collected from containers
3	Send data	Agent sends data to Log Analytics workspace	Data available in workspace for analysis
4	Visualize data	Open Azure Portal > Monitor > Logs	Container metrics and logs visible in dashboard
5	Set alerts	Create alert rules in Azure Monitor	Alerts trigger on specified conditions
6	Exit	Monitoring enabled and running	AKS cluster monitored continuously

💡 Monitoring addon enabled and data collection started; system runs continuously

Status Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	Final
MonitoringAddonStatus	Disabled	Enabled	Enabled	Enabled	Enabled
AgentStatus	Not Deployed	Deployed	Running	Running	Running
DataInWorkspace	None	None	Partial	Available	Available

Key Moments - 3 Insights

Why do we need to specify the Log Analytics workspace resource ID when enabling monitoring?

Because the monitoring agent sends collected data to that workspace; without specifying it, data has nowhere to go. See execution_table step 1 and 3.

Does enabling Container Insights immediately show data in Azure Portal?

No, data appears after the agent collects and sends it, which takes some time. See execution_table steps 2 and 4.

Can alerts be set before enabling monitoring?

No, alerts depend on data collected by monitoring; you must enable monitoring first. See execution_table step 5.

Visual Quiz - 3 Questions

Look at the execution_table, what is the status of the monitoring addon after step 1?

A Disabled

B Enabled

C Running

D Not Deployed

💡 Hint

Check the 'MonitoringAddonStatus' variable in variable_tracker after Step 1

At which step does the agent start sending data to the Log Analytics workspace?

A Step 3

B Step 1

C Step 2

D Step 4

💡 Hint

See execution_table row where data is sent to workspace

If the Log Analytics workspace ID is not specified, what will happen?

A Monitoring addon will enable but no data sent

B Agent will not deploy

C Command will fail

D Data will be sent to a default workspace

💡 Hint

Refer to key_moments about specifying workspace resource ID

Concept Snapshot

Enable Container Insights on AKS with az CLI
Deploys monitoring agent to collect container metrics and logs
Data sent to specified Log Analytics workspace
Visualize data in Azure Portal Monitor section
Set alerts based on collected data
Continuous monitoring runs after setup

Full Transcript

To monitor an AKS cluster with Container Insights, you enable the monitoring addon using the Azure CLI, specifying the Log Analytics workspace resource ID. This deploys an agent inside the cluster nodes that collects container metrics and logs. The agent sends this data to the workspace, where it can be viewed and analyzed in the Azure Portal. You can also set alerts to notify you of issues. The process runs continuously after enabling, providing ongoing monitoring.

Practice

1. What is the primary purpose of enabling Container Insights on an AKS cluster?

easy

A. To increase the number of nodes in the cluster automatically

B. To deploy applications faster on AKS

C. To monitor the health and performance of the AKS cluster

D. To secure the AKS cluster with firewall rules

Solution

1. Step 1: Understand Container Insights role

   Container Insights is designed to collect and display health and performance data for AKS clusters.

2. Step 2: Compare options with Container Insights function

   Only monitoring health and performance matches Container Insights' purpose; other options relate to scaling, deployment, or security.

3. Final Answer:

   To monitor the health and performance of the AKS cluster -> Option C

4. Quick Check:

   Container Insights = Monitoring AKS health [OK]

Hint: Container Insights is about monitoring, not scaling or security [OK]

Common Mistakes:

• Confusing monitoring with scaling features
• Thinking it deploys apps faster
• Assuming it manages security rules

2. Which Azure CLI command correctly enables Container Insights monitoring on an existing AKS cluster named myCluster in resource group myGroup?

easy

A. az aks update --enable-monitoring --name myCluster --resource-group myGroup

B. az aks enable-addons --addons monitoring --name myCluster --resource-group myGroup

C. az aks create --addons monitoring --name myCluster --resource-group myGroup

D. az monitor enable --resource-group myGroup --name myCluster

Solution

1. Step 1: Identify the correct command to enable addons

   The command to enable addons on an existing AKS cluster is az aks enable-addons with the --addons monitoring flag.

2. Step 2: Verify command syntax and parameters

   az aks enable-addons --addons monitoring --name myCluster --resource-group myGroup uses the correct command and parameters: cluster name and resource group are specified properly.

3. Final Answer:

   az aks enable-addons --addons monitoring --name myCluster --resource-group myGroup -> Option B

4. Quick Check:

   Enable addons command = az aks enable-addons --addons monitoring --name myCluster --resource-group myGroup [OK]

Hint: Use 'az aks enable-addons' with '--addons monitoring' [OK]

Common Mistakes:

• Using 'az aks create' instead of enable-addons
• Trying 'az aks update' with wrong flags
• Confusing Azure Monitor commands with AKS commands

3. After enabling Container Insights on your AKS cluster, you run this command:

az aks show --name myCluster --resource-group myGroup --query addonProfiles

What output indicates that monitoring is enabled?

medium

A. {"omsagent": {"enabled": true}}

B. {"monitoring": {"status": "active"}}

C. {"containerInsights": {"enabled": false}}

D. {"omsagent": {"enabled": false}}

Solution

1. Step 1: Understand addonProfiles output for monitoring

   The monitoring addon in AKS is called 'omsagent'. When enabled, its 'enabled' property is true.

2. Step 2: Match output with enabled monitoring

   {"omsagent": {"enabled": true}} shows 'omsagent' with 'enabled': true, indicating monitoring is active.

3. Final Answer:

   {"omsagent": {"enabled": true}} -> Option A

4. Quick Check:

   omsagent enabled = true means monitoring active [OK]

Hint: 'omsagent' enabled true means Container Insights is on [OK]

Common Mistakes:

• Looking for 'monitoring' or 'containerInsights' keys instead of 'omsagent'
• Confusing enabled false as active
• Misreading JSON structure

4. You enabled monitoring on your AKS cluster but do not see any logs or metrics in Azure Monitor. Which of the following is the most likely cause?

medium

A. Container Insights only works with Windows nodes, not Linux

B. The AKS cluster nodes are running an unsupported Kubernetes version

C. The Azure CLI command used was missing the --resource-group parameter

D. The Log Analytics workspace was not linked or created during monitoring setup

Solution

1. Step 1: Identify key requirement for Container Insights data

   Container Insights requires a Log Analytics workspace to collect and store logs and metrics.

2. Step 2: Analyze why no data appears

   If the workspace was not linked or created, no data will flow to Azure Monitor, causing empty logs and metrics.

3. Final Answer:

   The Log Analytics workspace was not linked or created during monitoring setup -> Option D

4. Quick Check:

   Missing workspace = no logs in Azure Monitor [OK]

Hint: Check Log Analytics workspace linkage if no monitoring data shows [OK]

Common Mistakes:

• Assuming Kubernetes version blocks monitoring data
• Thinking missing CLI parameters always cause no data
• Believing Container Insights only supports Windows nodes

5. You want to set up alerts in Azure Monitor for your AKS cluster using Container Insights to notify you when CPU usage exceeds 80% for 5 minutes. Which steps should you follow?

hard

A. Create a Log Analytics query for CPU usage, then create an alert rule based on that query with a 5-minute evaluation period

B. Enable monitoring with az aks enable-addons, then configure alerts directly in AKS cluster settings

C. Install a custom agent on each node to send CPU metrics, then configure alerts in Azure Monitor

D. Use Azure CLI to scale the cluster automatically when CPU exceeds 80%

Solution

1. Step 1: Use Log Analytics to query CPU metrics

   Container Insights sends metrics to Log Analytics, where you can write queries to analyze CPU usage.

2. Step 2: Create an alert rule in Azure Monitor

   Set an alert rule using the query with a condition for CPU > 80% sustained over 5 minutes to trigger notifications.

3. Final Answer:

   Create a Log Analytics query for CPU usage, then create an alert rule based on that query with a 5-minute evaluation period -> Option A

4. Quick Check:

   Alerts need queries + rules in Azure Monitor [OK]

Hint: Use Log Analytics queries to create alerts in Azure Monitor [OK]

Common Mistakes:

• Thinking alerts are configured directly in AKS without Azure Monitor
• Assuming custom agents are needed for CPU metrics
• Confusing scaling actions with alert setup