Monitoring data collection error using OMS Agent

Question

Hi,

Our company has several Azure virtual machines running MySQL DB.
OMS Agent is installed on each server to collect monitoring data in log Analytics workspace.

7~8 days ago, the oms agent of each server was sequentially stopped collecting.

The problem occurred only in Ubuntu-based virtual machines, and monitoring data such as DB (ex. MS-SQL) operating in Windows-based virtual machines are being collected normally.
We need to check the detailed cause more, but is it possible to check if there is a recent history of the same issue?
(For example, a patch due to a recent vulnerability issue...)

Answer 1

Hi @Dongjun Lee (이동준)

Welcome to Microsoft Q&A! Thanks for posting the question.

I did not see any recent trend for similar issue being reported. However, based on the symptoms (all these machines stopped sending heartbeat around the same time), can you please check:

1. If there was a recent change in the machines/Network that could have impacted the log collection from these machines (probably on the same network?)

2. If these machines along with the OMS agent are running.

---

Here are some of the troubleshooting guidelines that should help you resolve or investigate this issue further:

a. I notice that the version of the OMS agent installed is old. The current version is 1.13.40. Please upgrade the agents on these machines so that they have the latest patch/fix.

b. In case the issue persists even after the upgrade, please use the troubleshooting tool available here to identify the root cause and fix accordingly.

Please let me know if you have any questions.

---
Please 'Accept as answer' and ‘Upvote’ if it helped so that it can help others in the community looking for help on similar topics.

Answer 2

Dear @AnuragSingh-MSFT

Thanks for the reply.

As a result of checking the logs on each server,
it was confirmed that the oms-agent installed in the three subscriptions and in-house virtual machine infrastructure was sequentially stopped between December 5 ~ 6.
The agent could not take up external issues that were stopped sequentially for two days, and after checking a few things as a troubleshooter, the collection problem was solved by restarting the agent.

I haven't been able to find out exactly why the agents were stopped sequentially across multiple subscriptions and on-premises infrastructure,
but I appreciate the information you have provided to address the issue.