VM Insights shows no data

Copper Contributor

Hi,

 

we have a windows vm with a installed azure monitor agent via a data collection rule.

we get in the azure portal in the VM > Monitoring > Insights > Performance the error "no data"

the Heartbeat from the agent to the log analytics workspace is good.

 

i see the following errors in the log files C:\WindowsAzure\Resources\AMADataStore.VMName\Configuration\MonAgentHost.207.log:

 

Can someone help me?


Info (2024-01-03T07:48:20Z): MonAgentManager.exe - Attempting to create a new job object
Info (2024-01-03T07:48:20Z): MonAgentManager.exe - Starting agent: 'C:\Packages\Plugins\Microsoft.Azure.Monitor.AzureMonitorWindowsAgent\1.21.0.0\Monitoring\Agent\MonAgentCore.exe -deploymentdir "C:\Packages\Plugins\Microsoft.Azure.Monitor.AzureMonitorWindowsAgent\1.21.0.0\Monitoring\Agent" -LocalPath "C:\WindowsAzure\Resources\AMADataStore.VMName" -mcsmode -InitializedEvent "AzureMonitorAgentExtension-StartAgentEventName" -managerver 1 -parent 2364 -ShutDownEvent AzureMonitorAgentExtension-ShutdownEventName10780 -TotalShutDownEvent AzureMonitorAgentExtension-TotalShutdownEventName10780 -ConfigFile "C:\WindowsAzure\Resources\AMADataStore.VM-Name\mcs\mcsconfig.lkg.xml" '
Info (2024-01-03T07:48:20Z): MonAgentManager.exe - Could not start the agent with breaking away from its parent job object; will start the agent inside its parent job object
Info (2024-01-03T07:48:20Z): MonAgentManager.exe - Successfully starting MA without breaking away from it's parent job object; some or all of MA's usage restrictions are determined by the parent job object and outside the control of MA, but the agent will attempt to apply your configured resource settings.
Info (2024-01-03T07:48:22Z): MonAgentManager.exe - Dumping MA error and warning events from C:\WindowsAzure\Resources\AMADataStore.VMName\Tables\MAEventTable; use the summary logs or node diagnostics to get all of the events.
Info (2024-01-03T07:48:22Z): MonAgent - MA is running with original configuration file 'C:\WindowsAzure\Resources\AMADataStore.VMName\mcs\mcsconfig.lkg.xml'; this file is part of the role deployment
Info (2024-01-03T07:48:22Z): MonAgent - The configuration identity is 'AzureMonitorAgentVer0v0'
Error (2024-01-03T07:48:22Z): MonAgent - MAEventTable: Level:1 ActivityId:00-175fcc7137fb4997b7dead5849d88604-a3ab753cf2a2db3f-00 MDRESULT:0x80010003 ErrorCode(0): Message:Multiple instances of the monitoring agent are running with their local directory set to C:\WindowsAzure\Resources\AMADataStore.VMName. This is not supported. Please allocate a separate local directory for each instance of the agent.
Info (2024-01-03T07:48:22Z): MonAgentManager.exe - MonAgentCore has exited.
Error (2024-01-03T07:48:22Z): MonAgentManager.exe - Agent core process terminated with code: 0x80010008
Info (2024-01-03T07:48:22Z): MonAgentManager.exe - Dumping MA error and warning events from C:\WindowsAzure\Resources\AMADataStore.VMName\Tables\MAEventTable; use the summary logs or node diagnostics to get all of the events.
Error (2024-01-03T07:48:22Z): MonAgentCore.exe - MAEventTable: Level:2 ActivityId:00-175fcc7137fb4997b7dead5849d88604-a3ab753cf2a2db3f-00 MDRESULT:0x80010008 ErrorCode(0): Message:Could not start the monitoring agent: mdresult:80010008.
Error (2024-01-03T07:48:22Z): ErrorExit - MAEventTable: Level:2 ActivityId:00-728f6bee41224cbca2f88ca0586d001b-d7aaff7263a1c69f-00 MDRESULT:0x00000000 ErrorCode(0): Message:Agent core process terminated with code: 0x80010008
Error (2024-01-03T07:48:27Z): MonAgentManager.exe - Failed to start C:\Packages\Plugins\Microsoft.Azure.Monitor.AzureMonitorWindowsAgent\1.21.0.0\Monitoring\Agent\MonAgentCore.exe after 4 tries
Info (2024-01-03T07:48:27Z): MonAgentManager.exe - Stopping thread for Agent core start telemetry on Manager shut down.
Info (2024-01-03T07:48:27Z): MonAgentManager.exe - shutting down Mcsmanager
Info (2024-01-03T07:48:27Z): MonAgentManager.exe - McsManager shutting down
Info (2024-01-03T07:48:27Z): MonAgentManager.exe - stopping Mcsmanager
Info (2024-01-03T07:48:27Z): MonAgentManager.exe - Abandoning MCS call to honor shutdown request
Info (2024-01-03T07:48:27Z): MonAgentManager.exe - Failed to post health report to https://log-endpoint-bag-5utk.westeurope-1.handler.control.monitor.azure.com on first round of tries. No fallback will be attempted. Error:
Info (2024-01-03T07:48:27Z): MonAgentManager.exe - McsManager stopped
Info (2024-01-03T07:48:27Z): MonAgentManager.exe - McsManager resources released
Info (2024-01-03T07:48:27Z): MonAgentHost.exe - MonAgentManager has exited.
Error (2024-01-03T07:48:32Z): MonAgentHost.exe - Failed to start C:\Packages\Plugins\Microsoft.Azure.Monitor.AzureMonitorWindowsAgent\1.21.0.0\Monitoring\Agent\MonAgentManager.exe after 6 tries

1 Reply

Whether any extend log can be retrieved?