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.