Has anyone else observed inconsistencies with the Log Analytics installation and reporting status?

Question

Log Analytics reporting status shows four agents not reporting status. Log Analytics installation status shows one agent not installed. Machines not reporting to LA Workspace lists three resources while Security status shows one agent not installed. It appears that the Log Analytics agent installation status is consistent, at least in a couple of places. Why is the Log Analytics agent reporting status in the overview show different number of servers than the Machines not reporting to the LA Workspace?

I've turned autorefresh on and set it to the lowest setting hoping these number sync but no success... yet.

Note the above observations were made in the Azure Workbook Security tab. The Defender for Cloud Overview under the Advisor Security tab shows seven unmonitored VMs.

Are other people or clients experiencing these inconsistencies?

Answer 1

Hi,

I have couple of tenants and dont see any issues, what happens when you click the connect workload to the workspace from the Log Analytics console? Are all the servers in same Resource Groups and VNET? Can you check the troubleshooting steps and follow the process to analyse the server - https://learn.microsoft.com/en-us/azure/azure-monitor/agents/agent-windows-troubleshoot

Hope this helps.

JS

==

Please Accept the answer if the information helped you. This will help us and others in the community as well.

Answer 2

Good problem isolation recommendations provided which led me to open a support ticket on reporting inconsistencies specifically with the Log Analytics agent for Linux (OMSLinuxAgent)