Skip to content

Commit 341f3a7

Browse files
committed
Added AMA log note.
1 parent ced3aed commit 341f3a7

File tree

1 file changed

+5
-1
lines changed

1 file changed

+5
-1
lines changed

articles/azure-arc/servers/concept-log-analytics-extension-deployment.md

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Deploy Azure Monitor agent on Arc-enabled servers
33
description: This article reviews the different methods to deploy the Azure Monitor agent on Windows and Linux-based machines registered with Azure Arc-enabled servers in your local datacenter or other cloud environment.
4-
ms.date: 02/17/2023
4+
ms.date: 05/08/2024
55
ms.topic: conceptual
66
ms.custom: linux-related-content
77
---
@@ -17,6 +17,10 @@ The Azure Monitor agent is required if you want to:
1717
* Perform security monitoring in Azure by using [Microsoft Defender for Cloud](../../defender-for-cloud/defender-for-cloud-introduction.md) or [Microsoft Sentinel](../../sentinel/overview.md)
1818
* Collect inventory and track changes by using [Azure Automation Change Tracking and Inventory](../../automation/change-tracking/overview.md)
1919

20+
> [!NOTE]
21+
> Azure Monitor agent logs are stored locally and are updated after temporary disconnection of an Arc-enabled machine.
22+
>
23+
2024
This article reviews the deployment methods for the Azure Monitor agent VM extension, across multiple production physical servers or virtual machines in your environment, to help you determine which works best for your organization. If you are interested in the new Azure Monitor agent and want to see a detailed comparison, see [Azure Monitor agents overview](../../azure-monitor/agents/agents-overview.md).
2125

2226
## Installation options

0 commit comments

Comments
 (0)