You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/network-watcher/azure-monitor-agent-with-connection-monitor.md
+10-10Lines changed: 10 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,7 +12,7 @@ ms.service: network-watcher
12
12
ms.topic: how-to
13
13
ms.tgt_pltfrm: na
14
14
ms.workload: infrastructure-services
15
-
ms.date: 01/04/2021
15
+
ms.date: 09/06/2022
16
16
ms.author: mjha
17
17
ms.custom: mvc
18
18
#Customer intent: I need to monitor communication between one endpoint and another using Azure Monitor Agent with Connection Monitor.
@@ -46,15 +46,15 @@ Connection Monitor relies on lightweight executable files to run connectivity ch
46
46
47
47
Refer [here](./connection-monitor-overview.md#agents-for-azure-virtual-machines-and-virtual-machine-scale-sets) to learn how to install agents for Azure virtual machines and scale sets.
48
48
49
-
### Agents for On-premises machines
49
+
### Agents for on-premises machines
50
50
51
51
To make Connection Monitor recognize your on-premises machines as sources for monitoring
52
52
* Enable your hybrid endpoints to [ARC Enabled Servers](../azure-arc/overview.md)
53
-
1. To connect hybrid machines, you install the [Azure Connected Machine agent](../azure-arc/servers/agent-overview.md) on each machine.
54
-
2. This agent does not deliver any other functionality, and it doesn't replace the Azure Monitor Agent. The Azure Connected Machine agent simply enables you to manage your Windows and Linux machines hosted outside of Azure on your corporate network or other cloud providers.
53
+
* To connect hybrid machines, you install the [Azure Connected Machine agent](../azure-arc/servers/agent-overview.md) on each machine.
54
+
* This agent does not deliver any other functionality, and it doesn't replace the Azure Monitor Agent. The Azure Connected Machine agent simply enables you to manage your Windows and Linux machines hosted outside of Azure on your corporate network or other cloud providers.
55
55
56
56
* Install the [Azure Monitor Agent](../azure-monitor/agents/azure-monitor-agent-overview.md) to enable the Network Watcher extension.
57
-
1. The agent collects monitoring logs and data from the hybrid sources and delivers it to Azure Monitor
57
+
* The agent collects monitoring logs and data from the hybrid sources and delivers it to Azure Monitor
58
58
59
59
#### Installing Azure Connected Machine agent to enable ARC
60
60
@@ -132,21 +132,21 @@ Follow the steps below for the operating system of your server.
132
132
133
133
After you install the agent and configure it to connect to Azure Arc-enabled servers, go to the Azure portal to verify that the server has successfully connected. View your machine in the [Azure portal](https://aka.ms/hybridmachineportal).
##### Connect hybrid machines to Azure by using PowerShell
138
138
139
139
For servers enabled with Azure Arc, you can take manual steps mentioned above to enable them forone or more Windows or Linux machinesin your environment. Alternatively, you can use the PowerShell cmdlet Connect-AzConnectedMachine to download the Connected Machine agent, install the agent, and register the machine with Azure Arc. The cmdlet downloads the Windows agent package (Windows Installer) from the Microsoft Download Center, and the Linux agent package from the Microsoft package repository.
140
-
Refer to the linked document to discover the required steps to install the [ARC agent via Powershell](../azure-arc/servers/onboard-powershell.md)
140
+
Refer to the linked document to discover the required steps to install the [ARC agent via PowerShell](../azure-arc/servers/onboard-powershell.md)
141
141
142
142
##### Connect hybrid machines to Azure from Windows Admin Center
143
143
144
-
You can enable Azure Arc-enabled servers forone or more Windows machinesin your environment by performing a set of steps manually, as mentioned above. Or you can use Windows Admin Center to deploy the Connected Machine agent and register your on-premises servers without having to perform any steps outside of this tool. Refer to the linked document to discover the steps to [install ARC agent via Windows Admin Centre](../azure-arc/servers/onboard-windows-admin-center.md)
144
+
You can enable Azure Arc-enabled servers forone or more Windows machinesin your environment by performing a set of steps manually, as mentioned above. Or you can use Windows Admin Center to deploy the Connected Machine agent and register your on-premises servers without having to perform any steps outside of this tool. Refer to the linked document to discover the steps to [install ARC agent via Windows Admin Center](../azure-arc/servers/onboard-windows-admin-center.md)
145
145
146
146
#### Installing Azure Monitor Agent
147
147
148
148
The Azure Monitor agent is implemented as an Azure VM extension with the details in the following table. It can be installed using any of the methods to install virtual machine extensions including those described in this article. Refer to [Azure Monitor overview](../azure-monitor/agents/azure-monitor-agent-overview.md) to learn more.
149
-
The following section covers installing Azure Monitor Agent on Arc Enabled Servers using Powershell and Azure CLI. Refer to [Manage the Azure Monitor Agent](../azure-monitor/agents/azure-monitor-agent-manage.md) to learn the rest.
149
+
The following section covers installing Azure Monitor Agent on Arc Enabled Servers using PowerShell and Azure CLI. Refer to [Manage the Azure Monitor Agent](../azure-monitor/agents/azure-monitor-agent-manage.md) to learn the rest.
150
150
151
151
##### Using PowerShell
152
152
You can install the Azure Monitor agent on Azure virtual machines and on Azure Arc-enabled servers using the PowerShell commandfor adding a virtual machine extension.
@@ -268,7 +268,7 @@ The Azure Monitor agent can coexist (run side by side on the same machine) with
268
268
* Besides data duplication, this would also generate more charges for data ingestion and retention.
269
269
* Running two telemetry agents on the same machine would result in double the resource consumption, including but not limited to CPU, memory, storage space and network bandwidth
270
270
271
-
#### Create connection monitor
271
+
## Next steps
272
272
273
273
After the successful installation of monitoring agents, proceed to [Creation a Connection Monitor](./connection-monitor-overview.md#create-a-connection-monitor).
274
274
Upon the successful creation of Connection Monitor, analyze monitoring data and set alerts. Diagnose issues in your connection monitor and your network.
0 commit comments