How to enable map within VM Insights

Question

Hi there,

I am trying to enable the map within the Insights monitoring section for my VM.

It doesn't seem to work.

When I first went to setup monitoring I clicked on 'Enable' on the Insights Onboarding page. I setup a data collection rule so that processes and dependencies (map) is enabled, which got the performance graphs working, but the map doesn't seem to work.

When I go to the VM and click on 'Insights' on the left hand side blade and then click map I just get:

'Select a machine or group to view a map'

Does anyone know how I can fix this?

Answer 1

Hi,

Please consider the following troubleshooting steps:

Ensure Dependency Agent is Installed: The VM Insights Map feature requires the Dependency Agent to be installed on the VM. If the Dependency Agent isn't installed, the Map view won't be available. To enable the Map view, you should set the enableAMA property = true in the Dependency Agent extension when installing the Dependency Agent​​.

Check Data Collection Rules: Make sure you have associated a data collection rule with the Map feature enabled on the machine. This rule is necessary for collecting information about processes running on the virtual machine and dependencies between machines, which in turn enables the Map feature in VM Insights​​.

Review VM Insights Configuration: Ensure that your VM Insights configuration is correct. This includes checking whether the Azure Monitor Agent or Log Analytics agent is correctly configured, as these are required for VM Insights to function properly.

Check for Common Issues:

• Verify if the virtual machine is sending log and performance data to Azure Monitor Logs. If no data is being collected, this could be a reason for the Map feature not working​​.
• Ensure that you are not on the Log Analytics free tier, which limits the number of unique Service Map machines and could prevent additional machines from appearing in the Service Map​​.
• If the virtual machine appears in the Map view but has missing data, check if the kernel driver for the Dependency agent is loaded. The log files on the virtual machine should provide insights into why the kernel driver might not have loaded​​.

Avoid Duplicate Data Collection: Be cautious if you have both Azure Monitor Agent and Log Analytics agent installed on the same machine, as collecting duplicate data can result in inaccuracies in the Map feature​​​​.

If these steps do not resolve the issue, consider reaching out to Azure support by opening a support ticket. They might be able to provide more specific guidance based on your Azure environment and setup.

As a reference, please review the Microsoft troubleshoot VM insights document: https://learn.microsoft.com/en-us/azure/azure-monitor/vm/vminsights-troubleshoot

If you find the provided information helpful and it resolves your query, please consider accepting the answer. Your feedback is valuable and helps ensure the quality and relevance of the responses.

Answer 2

deleted as duplicate answer due to a refresh issue

Answer 3

Hello,

I thing the original issue raised here is a discrepency between what is told in https://learn.microsoft.com/en-gb/training/modules/monitor-azure-vm-using-diagnostic-data/5-enable-vm-insights versus acual current behavior of the portal.

Indeed when enabling the VM Insight the default provided DCR is having Process and dependencies (Map) disabled:

And thus to enable it we need to create a new DCR ("Create New"):

So that we are back to what was suggested: