⚠️ Repo Archive Notice

As of Nov 13, 2020, charts in this repo will no longer be updated. For more information, see the Helm Charts Deprecation and Archive Notice, and Update.

Azure Monitor – Containers

DEPRECATION NOTICE

This chart is deprecated and no longer supported.

Introduction

This article describes how to set up and use Azure Monitor - Containers to monitor the health and performance of your workloads deployed to Kubernetes and OpenShift v4 environments.

Monitoring your Kubernetes cluster and containers is critical, especially when running a production cluster, at scale, with multiple applications.

Pre-requisites

Kubernetes versions and support policy same as AKS supported versions
You will need to create a location to store your monitoring data.

Create Azure Log Analytics Workspace

You will need to add AzureMonitor-Containers solution to your workspace from #1 above

Add the 'AzureMonitor-Containers' Solution to your Log Analytics workspace.
For AKS-Engine or ACS-Engine K8S cluster hosted in Azure, add required tags on cluster resources, to be able to use Azure Container monitoring User experience (aka.ms/azmon-containers)

Note: Pre-requisite #3 not applicable for the AKS-Engine or ACS-Engine clusters hosted in Azure Stack or On-premise.

Installing the Chart

Note: --name flag not required in Helm3 since this flag is deprecated

Note: use omsagent.proxy parameter to set the proxy endpoint if your K8s cluster configured behind the proxy. Refer to configure proxy for more details about proxy.

To Use Azure Log Analytics Workspace in Public Cloud

bash

$ helm repo add incubator https://kubernetes-charts-incubator.storage.googleapis.com/
$ helm install --name azmon-containers-release-1 \
--set omsagent.secret.wsid=<your_workspace_id>,omsagent.secret.key=<your_workspace_key>,omsagent.env.clusterName=<my_prod_cluster>  incubator/azuremonitor-containers

To Use Azure Log Analytics Workspace in Azure China Cloud

bash

$ helm repo add incubator https://kubernetes-charts-incubator.storage.googleapis.com/
$ helm install --name azmon-containers-release-1 \
--set omsagent.domain=opinsights.azure.cn,omsagent.secret.wsid=<your_workspace_id>,omsagent.secret.key=<your_workspace_key>,omsagent.env.clusterName=<your_cluster_name>  incubator/azuremonitor-containers

To Use Azure Log Analytics Workspace in Azure US Government Cloud

bash

$ helm repo add incubator https://kubernetes-charts-incubator.storage.googleapis.com/
$ helm install --name azmon-containers-release-1 \
--set omsagent.domain=opinsights.azure.us,omsagent.secret.wsid=<your_workspace_id>,omsagent.secret.key=<your_workspace_key>,omsagent.env.clusterName=<your_cluster_name>  incubator/azuremonitor-containers

Upgrading an existing Release to a new version

If the previous version of the chart installed with Helm2, it can be upgraded successfully to current version using Helm2. But, if the previous version of chart installed with the Helm3 or release migrated to Helm3,then chart can’t be upgraded to latest version due to issues in Helm3 with regards to upgrading the existing release to new version, as described in Helm issue #6850

Uninstalling the Chart

To uninstall/delete the azmon-containers-release-1 release:

Note: --purge flag not required in Helm3 since this flag deprecated

bash


$ helm del --purge azmon-containers-release-1

The command removes all the Kubernetes components associated with the chart and deletes the release.

Configuration

The following table lists the configurable parameters of the MSOMS chart and their default values.

Parameter	Description	Default
`omsagent.image.tag`	image tag for Linux Agent.	Most recent release
`omsagent.image.tagWindows`	image tag for Windows Agent.	Most recent release
`omsagent.image.imagerepo`	image repo for Liunx & Windows.	For Public and US Govt cloud: mcr.microsoft.com/azuremonitor/containerinsights/ciprod and For China Cloud: mcr.azk8s.cn/azuremonitor/containerinsights/ciprod
`omsagent.image.pullPolicy`	image pull policy for the agent.	IfNotPresent
`omsagent.secret.wsid`	Azure Log analytics workspace id	Does not have a default value, needs to be provided
`omsagent.secret.key`	Azure Log analytics workspace key	Does not have a default value, needs to be provided
`omsagent.domain`	Azure Log analytics cloud domain (public,china, us govt)	opinsights.azure.com (Public cloud as default), opinsights.azure.cn (China Cloud), opinsights.azure.us (US Govt Cloud)
`omsagent.env.clusterName`	Name of your cluster	Does not have a default value, needs to be provided
`omsagent.rbac`	rbac enabled/disabled	true (i.e.enabled)
`omsagent.proxy`	Proxy endpoint	Doesnt have default value. Refer to configure proxy

Note: For Azure Manage K8s clusters such as Azure Arc K8s and ARO v4, omsagent.env.clusterId with fully qualified azure resource id of the cluster should be used instead of omsagent.env.clusterName

Note

Parameter omsagent.env.doNotCollectKubeSystemLogs has been removed starting chart version 1.0.0. Refer to 'Agent data collection settings' section below to configure it using configmap.
onboarding of multiple clusters with the same cluster name to same log analytics workspace not supported. If need this configuration, use the cluster FQDN name rather than cluster dns prefix to avoid collision with clusterName

Agent data collection settings

Staring with chart version 1.0.0, agent data collection settings are controlled thru a config map. Refer to documentation about agent data collection settings here

You can create a Azure Loganalytics workspace from portal.azure.com and get its ID & PRIMARY KEY from 'Advanced Settings' tab in the Ux.

Specify each parameter using the --set key=value[,key=value] argument to helm install. For example,

bash


$ helm install --name myrelease-1 \
--set omsagent.secret.wsid=<your_workspace_id>,omsagent.secret.key=<your_workspace_key>,omsagent.env.clusterName=<your_cluster_name>
  incubator/azuremonitor-containers

Alternatively, a YAML file that specifies the values for the parameters can be provided while installing the chart. For example,

bash


$ helm install --name myrelease-1 -f values.yaml incubator/azuremonitor-containers

After you successfully deploy the chart, you will be able to see your data in

azure public cloud portal for the clusters in Azure Public Cloud
azure china cloud portal for the clusters in Azure China Cloud
azure us government cloud portal for the clusters in Azure US Government Cloud

If you need help with this chart, please reach us out through this email.

Custom resource

Starting with chart version 2.0.0, chart will create a CRD (healthstates.azmon.container.insights) in kube-system namespace. This is used by the agent for cluster health monitoring.

Container Runtime(s)

Starting with chart version 2.7.0, chart will support Container Runtime Interface(CRI) compatiable runtimes such as CRI-O and ContainerD etc. in addition to Docker/Moby.

Configuring Proxy Endpoint

Starting with chart version 2.7.1, chart will support specifying the Proxy endpoint via omsagent.proxy chart parameter so that all remote outbound traffic will be routed via configured proxy endpoint.

Communication between the Azure Monitor for containers agent and Azure Monitor backend can use an HTTP or HTTPS proxy server.

Both anonymous and basic authentication (username/password) proxies are supported.

The proxy configuration value has the following syntax: [protocol://][user:password@]proxyhost[:port]

Property	Description
Protocol	http or https
user	username for proxy authentication
password	password for proxy authentication
proxyhost	Address or FQDN of the proxy server
port	port number for the proxy server

For example: omsagent.proxy=http://user01:[email protected]:8080

Note: Although you do not have any user/password set for the proxy, you will still need to add a psuedo user/password. This can be any username or password.

The Azure Monitor for containers agent only creates secure connection over http. Even if you specify the protocol as http, please note that http requests are created using SSL/TLS secure connection so the proxy must support SSL/TLS.

Support for Windows Container Logs

Starting with chart version 2.7.1, chart deploys the daemonset on windows nodes which collects std{out;err} logs of the containers running on windows nodes.

Ux

Once the Azure Monitor for containers chart successfully onboarded, you should be able to view insights of your cluster Azure Portal

Contact

If you have any questions or feedback regarding the container monitoring addon, please reach us out through this email.