Forum Discussion
Why no AMA Gateway (like log analytics gateway) ?
Is there something I don't understand about how the Azure Monitor Agent works? Shouldn't there be a local collector or gateway/proxy or something for on-prem devices, like the log analytics gateway a...
If they all already have HTTPS access to the internet, let them connect out anyway. But that has limited applications, you aren't going to be deploying to devices with that lax network controls.
I believe that the Log Analytics Gateway is compatible with the AMA, at least the documentation says so here: https://docs.microsoft.com/en-us/azure/azure-monitor/agents/azure-monitor-agent-overview?tabs=PowerShellWindows#networking
I believe that the Log Analytics Gateway is compatible with the AMA, at least the documentation says so here: https://docs.microsoft.com/en-us/azure/azure-monitor/agents/azure-monitor-agent-overview?tabs=PowerShellWindows#networking
Also, there are no signs that the LAG will be deprecated any time soon. The Azure monitor is in place because it does more than the LAA did, while also doing what it did, so why support both? I can't see that happening with the LAG.
The LAA and AMA used to coexist. One was chosen over the other and became de facto, The fact is that there is nothing in Microsoft's tooling at the moment which does the job of the LAG, so it is safe.
The LAA and AMA used to coexist. One was chosen over the other and became de facto, The fact is that there is nothing in Microsoft's tooling at the moment which does the job of the LAG, so it is safe.