Azure Monitor agent Migration

Question

Hi ,

we are in the process of Migrating from Log analytics agent to AMA .

I have followed the instructions as mentioned here https://learn.microsoft.com/en-us/azure/azure-monitor/agents/azure-monitor-agent-migration

Generated DCR rules and deployed it . we are using VM insights solution and that's also using the AMA agent . But in Heartbeat it still shows 'Direct agent' in category .

AMA helper shows this for workspace

and for VM

Why does both shows different version of Agents ?

Answer 1

Racheal, thank you for reaching out to Microsoft Q&A and apologies for the delayed response.

Confirm that you have followed the entire steps as mentioned in the guide, especially the following:

1. Associate machines to your data collection rules:
   1. From the Monitor menu, select Data Collection Rules.
   2. From the Data Collection Rules screen, select your data collection rule.
   3. Select View resources > Add.
   4. Select your machines > Apply.

This step is required to be followed for all the DCRs to add VMs which are getting migrated from OMS agent to AMA.

Also, once the association in DCR is done, it may take 5-10 minutes for new data to come in.

Regarding your query for the result from Heartbeat table, I would suggest querying the data for the specific machine and verifying the result. Because, if AMA and OMS agent are both installed on the machine, duplicate data will be sent to LA workspace, which might create confusion.

Therefore, querying for a specific machine in Heartbeat table and orderd by timegenerated field should show entries from both tables - if any.

Heartbeat
| where Computer == '<Computer Name>'
| order by TimeGenerated desc

Hope this helps.

Please let us know if you are still facing this issue.