question

MarkRothfield-9210 avatar image
0 Votes"
MarkRothfield-9210 asked jv-msft answered

Start using the Azure Monitor agent instead of the Log Analytics agent before 31 August 2024

Since we use Azure Sentinel and it relies upon aggregating data into a Log Analytics workspace, what will the impact be upon Sentinel (if any) when the Log Analytics agent is retired?

fasttrack-azure
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

AlanKinane avatar image
0 Votes"
AlanKinane answered

This is just the VM agent that needs to be replaced. If you are monitoring virtual machines with Azure Sentinel then you need to replace the log analytics agent with the azure monitor agent on each of the VMs. Log Analytics itself is not affected by this.

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

jv-msft avatar image
0 Votes"
jv-msft answered

The Azure Monitor Agent is replacing the Log Analytics Agent for Azure Monitor, Azure Sentinel and Azure Security Center. The Azure Monitor Agent is generally available for Azure Monitor, and in private preview for Azure Sentinel and Azure Security Center at present. For more details refer to: https://docs.microsoft.com/en-us/azure/azure-monitor/agents/azure-monitor-agent-overview?tabs=PowerShellWindows#supported-services-and-features

The Log Analytics Agent on VMs connected to a Log Analytics workspace used for Sentinel should be replaced with the Azure Monitor Agent before it is retired.

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.