Forum Discussion
Solved
OMS Agent for Linux Agent and multi homing
According to the official documentation, the OMS agent for linux does not support multi homing.
https://docs.microsoft.com/en-us/azure/azure-monitor/platform/log-analytics-agent#workspace-and-management-group-limitations
Yet I do see some logs/hints as the below.
INFO: Scripts/nxOMSPlugin.pyc(113):
OMSAgent is multi-homed and resource is updating workspace xyz
I would like to check if the agent I am checking on is multi homed though I could not find any other workspace reference in file paths.
Is this feasible now and if so where can I read further about this or is this work in progress and if so are these logs wrong.
- Hi,
It is correct that OMS Agent for Linux does not support multi-homing.
There is a new agent called Azure Monitor Agent, which will allow it, replace three other agents, and add more granular control over what telemetry is being collected, but it is currently in Preview and has several limitations. You could still try it out.
More info: https://docs.microsoft.com/en-us/azure/azure-monitor/platform/azure-monitor-agent-overview
4 Replies
- Hi,
It is correct that OMS Agent for Linux does not support multi-homing.
There is a new agent called Azure Monitor Agent, which will allow it, replace three other agents, and add more granular control over what telemetry is being collected, but it is currently in Preview and has several limitations. You could still try it out.
More info: https://docs.microsoft.com/en-us/azure/azure-monitor/platform/azure-monitor-agent-overview- Unfortunately the AMA agent doesn't (yet) really support log file collection, at least in Linux VM's.
While there are instructions documented to setup a file log collection manually, using API and custom ARM templates, in the target custom logs tables there are missing columns, for example, the "Computer" column is not created, and as such you cannot match the log against whichever VM it originated from. I don't mind the manual setup, but this limitation with the columns was unexpected.- And this in 2022 now...
pazdedav Thank you, will check this option.
