Azure Monitor
An Azure service that is used to collect, analyze, and act on telemetry data from Azure and on-premises environments.
3,285 questions
Migrate OMS agent to AMA agent (in terraform)
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(211.20000000000002, 7.000000000000001%, 30%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EDL%3C/text%3E%3C/svg%3E)
Denis L
0
Reputation points
Hi,
I have Azure resources managed in terraform. I'm not really a "good friend" with terraform, but I was chosen to migrate OMS agents to the new AMA agent. I know a migration guides exists, I went through it, but I either do not understand it or I have some weird use case.
Currently, there these resources in terraform
resource "azurerm_log_analytics_solution" "log_analytics_solution" {
solution_name = "ContainerInsights"
location = "location"
resource_group_name = "<resourceGroupName>"
workspace_resource_id = azurerm_log_analytics_workspace.aks_cluster_log_analytics.id
workspace_name = azurerm_log_analytics_workspace.aks_cluster_log_analytics.name
plan {
publisher = "Microsoft"
product = "OMSGallery/ContainerInsights"
}
tags = merge(var.default_tags)
}
I believe, this is the result of the above setup
And then, the cluster itself has this (I have omitted most of the fields)
resource "azurerm_kubernetes_cluster" "aks_cluster" {
...
oms_agent {
log_analytics_workspace_id = azurerm_log_analytics_workspace.aks_cluster_log_analytics.id
}
....
}
Regarding this and the cluster, I have found, that using oms_agent deploys the AMA agent anyway https://github.com/Azure/AKS/issues/4208 This cluster has been created some while ago, is this still true? Is there a way to find out? (I do have some doubts, because from my understanding, the AMA agent needs DCR and I have not found any DCR)
I have also tried the AMA Migration Helper workbook and MMA discovery and Removal Utility. Both of these point to one VM. When I open the VM and then Extensions, I can see this:
I believe this is the OMS agent that needs to migrated. Am I correct here? I have not found any configuration for this agent anywhere. My only assumption is, that I need to add AMA extension using terrraform
resource "azurerm_virtual_machine_extension" "ama_extension" {
name = "AzureMonitorLinuxAgent"
virtual_machine_id = azurerm_windows_virtual_machine.virtual_machine.id
publisher = "Microsoft.Azure.Monitor"
type = "AzureMonitorWindowsAgent"
type_handler_version = "1.0"
settings = jsonencode({
"dataCollectionRule" = "<dcr-id>"
})
}
But honestly, I don't know what should be included in the DCR for it to have the same "effect" as the current OMS agent.
So, overall my questions are:
- Am I correct with my assumption, that the way the cluster is setup in terraform, it does not need any changes? Meaning, it already uses the AMA agent.
- Am I correct with my assumption, that the current extension listed in the VM is indeed the OMS agent, that needs to be migrated?
{count} votes
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(268.8, 47%, 36%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ERP%3C/text%3E%3C/svg%3E)
Rahul Podila 105 Reputation points Microsoft Vendor2024-10-17T08:53:47.1833333+00:00 Hi @Denis L
Welcome to the Microsoft Q&A Platform! Thank you for asking your question here.It seems like your AKS cluster is probably already using the AMA agent, especially if it was created after AMA became the default for AKS. You can check by looking at Azure Monitor Logs—if data is being collected, it's using AMA. If you need to customize what data is collected, you'll need to set up a Data Collection Rule (DCR), but this is optional.
The VM, on the other hand, still uses the old OMS agent, which is now being replaced by AMA. You will need to switch to another AMA agent. To do this, you must uninstall the OMS agent, either manually or using automation. Then, you can use Terraform to assign the AMA extension to the VM, which will redirect to the new monitoring agent. In addition, you will need to set up a Data Collection Rule (DCR), which specifies what data the AMA agent should collect. If you want the new AMA agent to collect the same data as the OMS agent, you will need to repeat that setting in the DCR.
If the AKS cluster already uses AMA, you do not need to change it unless you want to change the collected data (which requires the use of DCR). For the VM you will need to uninstall the OMS agent, install the AMA extension through Terraform, and create a DCR to specify the data to back up.
If you have any further queries, do let us know.
If the answer is helpful, please click "Accept Answer" and "Upvote it".
-
Rahul Podila 105 Reputation points Microsoft Vendor
2024-10-18T09:17:47.43+00:00 Hi @Denis L
If you had a chance to see my comment to your question. If it was helpful, please click "Upvote" on my post let us know Thank you...!
Sign in to comment
Sign in to answer