Skip to content

Commit f341a81

Browse files
committed
Update azure-monitor-agent-with-connection-monitor.md
1 parent dbd9a5a commit f341a81

File tree

1 file changed

+9
-7
lines changed

1 file changed

+9
-7
lines changed

articles/network-watcher/azure-monitor-agent-with-connection-monitor.md

Lines changed: 9 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -21,8 +21,10 @@ ms.custom: mvc
2121
# Monitor Network Connectivity using Azure Monitor Agent with Connection Monitor (Private Preview)
2222

2323
Connection Monitor now supports Azure Monitor Agent extension, thus eliminating the dependency on the legacy Log Analytics agent.
24+
2425
With Azure Monitor Agent, we aim to serve a single agent that will consolidate all the features necessary to address all connectivity logs and metrics data collection needs across Azure and On-premises machines as compared to running various monitoring agents.
25-
Azure Monitor Agent provides enhanced security and performance capabilities, effective cost savings with efficient data collection & ease of troubleshooting with simpler management of data collection with respect to Log Analytics agent. Learn more about [Azure Monitor Agent](../azure-monitor/agents/azure-monitor-agent-overview.md).
26+
Azure Monitor Agent provides enhanced security and performance capabilities, effective cost savings with efficient data collection & ease of troubleshooting with simpler management of data collection with respect to Log Analytics agent.
27+
Learn more about [Azure Monitor Agent](../azure-monitor/agents/azure-monitor-agent-overview.md).
2628

2729
![Diagram showing how Connection Monitor interacts with Azure VMs, non-Azure hosts, endpoints, and data storage locations.](./media/connection-monitor-2-preview/hero-graphic-new.png)
2830

@@ -56,19 +58,19 @@ To make Connection Monitor recognize your on-premises machines as sources for mo
5658

5759
#### Installing Azure Connected Machine agent to enable ARC
5860

59-
Before proceeding be sure to review the [prerequisites](../azure-arc/servers/prerequisites.md) and verify that your subscription and resources meet the requirements.
61+
Before proceeding be sure to review the [prerequisites](../azure-arc/prerequisites.md) and verify that your subscription and resources meet the requirements.
6062

6163
##### Prerequisites
6264

6365
* An Azure account with an active subscription. [Create an account for free](https://azure.microsoft.com/free/?WT.mc_id=A261C142F).
6466
* Deploying the Connected Machine agent on a machine requires that you have administrator permissions to install and configure the agent. On Linux this is done by using the root account, and on Windows, with an account that is a member of the Local Administrators group.
6567
* The Microsoft.HybridCompute, Microsoft.GuestConfiguration, and Microsoft.HybridConnectivity resource providers must be registered on your subscription. You can [register these resource providers ahead of time](../azure-arc/servers/prerequisites.md#azure-resource-providers), or while completing the steps in this quickstart.
66-
* Before you get started, be sure to review the [agent prerequisites](../prerequisites.md) and verify the following:
68+
* Before you get started, be sure to review the [agent prerequisites](../azure-arc/prerequisites.md) and verify the following:
6769
* Your target machine is running a supported [operating system](../azure-arc/servers/prerequisites.md#supported-operating-systems).
6870
* Your account has the [required Azure built-in roles](../azure-arc/servers/prerequisites.md#required-permissions).
69-
* Ensure the machine is in a [supported region](../azure-arc/server/overview.md#supported-regions).
71+
* Ensure the machine is in a [supported region](../azure-arc/overview.md#supported-regions).
7072
* Confirm that the Linux hostname or Windows computer name doesn't use a [reserved word or trademark](../azure-resource-manager/templates/error-reserved-resource-name.md).
71-
* If the machine connects through a firewall or proxy server to communicate over the Internet, make sure the URLs [listed](../azure-arc/server/network-requirements.md#urls) are not blocked.
73+
* If the machine connects through a firewall or proxy server to communicate over the Internet, make sure the URLs [listed](../azure-arc/network-requirements.md#urls) are not blocked.
7274

7375
##### Generate installation script
7476

@@ -190,7 +192,7 @@ Update-AzConnectedExtension -ResourceGroupName $env.ResourceGroupName -MachineNa
190192
```
191193
---
192194

193-
The **recommendation** is to enable automatic update of the agent by enabling the [Automatic Extension Upgrade (preview)](../azure-arc/servers/manage-automatic-vm-extension-upgrade.md#enabling-automatic-extension-upgrade-preview) feature, using the following PowerShell commands.
195+
The **recommendation** is to enable automatic update of the agent by enabling the [Automatic Extension Upgrade (preview)](../azure-arc/servers/manage-automatic-vm-extension-upgrade.md) feature, using the following PowerShell commands.
194196
# [Windows](#tab/PowerShellWindowsArc)
195197
```powershell
196198
Update-AzConnectedMachineExtension -ResourceGroup <resource-group-name> -MachineName <arc-server-name> -Name AMAWindows -EnableAutomaticUpgrade
@@ -243,7 +245,7 @@ az connectedmachine upgrade-extension --extension-targets "{\"Microsoft.Azure.Mo
243245
```
244246
---
245247

246-
The **recommendation** is to enable automatic update of the agent by enabling the [Automatic Extension Upgrade (preview)](../azure-arc/servers/manage-automatic-vm-extension-upgrade.md#enabling-automatic-extension-upgrade-preview) feature, using the following PowerShell commands.
248+
The **recommendation** is to enable automatic update of the agent by enabling the [Automatic Extension Upgrade (preview)](../azure-arc/servers/manage-automatic-vm-extension-upgrade.md) feature, using the following PowerShell commands.
247249
# [Windows](#tab/CLIWindowsArc)
248250
```azurecli
249251
az connectedmachine extension update --name AzureMonitorWindowsAgent --machine-name <arc-server-name> --resource-group <resource-group-name> --enable-auto-upgrade true

0 commit comments

Comments
 (0)