Search code examples
azureazure-aksazure-monitoringazure-monitor

Is the legacy oms_agent addon required for ama container insights for AKS?

This documentation page describes the addon 'oms_agent' for AKS.

https://learn.microsoft.com/en-us/azure/azure-monitor/containers/kubernetes-monitoring-enable?tabs=terraform#enable-container-insights

However, it only deploys the ama deployment (ama-logs-rs), which seems to use the new Azure Monitor Agent (AMA), and not the depricated Log Analytics Agent (OMS).

What is the relation between the oms_agent addon and ama? Will the oms_agent addon also be retired once Log Analytics agent is depricated?

Solution

  • The oms_agent addon is not required anymore for Azure Monitor Agent (AMA) container insights for AKS. The documentation page you linked to only deploys the AMA deployment (ama-logs-rs), which uses the new Azure Monitor Agent. The oms_agent addon is related to the deprecated Log Analytics Agent (OMS), and it will also be retired once the Log Analytics agent is deprecated.

    For AKS, if you're setting up container insights on a new cluster (specifically using the latest versions example 1.27 or 29) or migrating from the legacy OMS agent, you should use the Azure Monitor Agent. enter image description here

    The legacy OMS agent is only needed if you have specific dependencies on it or are running workloads that have not yet been tested or certified to work with the AMA.

    Plus, you don't have to go through all this hassle, you can simply enable container insight via portal while setting up the cluster.

    enter image description here

    or through CLI

    az aks enable-addons -a monitoring -n <cluster-name> -g <cluster-resource-group-name> --workspace-resource-id "/subscriptions/my-subscription/resourceGroups/my-resource-group/providers/Microsoft.OperationalInsights/workspaces/my-workspace"

    enter image description here

    References: