Azure Monitoring Agent sends no Heartbeat to the Log analytics Workspace

Behnam Bamavadat 0 Reputation points

Dear Community,

I am currently trying to build a monitoring tool with Azure Workbook and Log Analytics Workspace. I have installed AzureMonitorWindowsAgent on the Windows VMs and connected it to the Log Analytics Workspace. The problem is that some of our VMs located in Germany West Central do not send a heartbeat to the respective Log Analytics Workspace, although the server is not overloaded and I can access the server. I get a heartbeat from time to time, but sometimes no heartbeat for days. I have tried simple thing by unistalling and installing the agent again it did not help.

I have opened a case with Microsoft and checked the following criteria:

NSG rule: I have AzureMonitor service tag open for inbound and outbound rule.

Proxy server: I have added new Microsoft Azure Monitoring links to the list.

Microsoft took the network path from the server and told me that it may be a network issue. but I am not sure if it is a network issue because every now and then I get the heartbeat and it is not completely blocked.

After analyzing in depth with Microsoft Network Engineer, we found that the packet from the VM is successfully sent up to the Express Route IPs and we have TLS handshake up to that part.

I would like to know if anyone may have the same issue with Heartbeat? or maybe a tip to better understand the issue.

Windows Server
Windows Server
A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.
12,568 questions
0 comments No comments
{count} votes