Skip to content

Commit 4435e0b

Browse files
Merge pull request #268770 from halkazwini/nw-agent
Update the steps to enable NPM
2 parents d981af9 + 0682ac0 commit 4435e0b

File tree

1 file changed

+8
-7
lines changed

1 file changed

+8
-7
lines changed

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

Lines changed: 8 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -6,9 +6,9 @@ author: halkazwini
66
ms.author: halkazwini
77
ms.service: network-watcher
88
ms.topic: how-to
9-
ms.date: 11/15/2023
9+
ms.date: 03/12/2024
1010

11-
#Customer intent: As an Azure administrator, I need use the Azure Monitor agent so I can monitor a connection using the Connection monitor.
11+
#Customer intent: As an Azure administrator, I need use the Azure Monitor agent so I can monitor a connection with a non-Azure resource using the Connection monitor.
1212
---
1313

1414
# Monitor network connectivity using Azure Monitor agent with connection monitor
@@ -61,13 +61,13 @@ To enable the Network Performance Monitor solution for on-premises machines, fol
6161

6262
1. In the Azure portal, go to **Network Watcher**.
6363

64-
1. Under **Monitoring**, select **Network Performance Monitor**. A list of workspaces with Network Performance Monitor solution enabled is displayed, filtered by **Subscriptions**.
64+
1. Under **Monitoring**, select **Connection Monitor**.
6565

66-
1. To add the Network Performance Monitor solution in a new workspace, select **Add NPM**.
66+
1. Select **+ Enable Non-Azure**.
6767

6868
1. In **Enable Non-Azure**, select the subscription and workspace in which you want to enable the solution, and then select **Create**.
6969

70-
After you've enabled the solution, the workspace takes a couple of minutes to be displayed.
70+
After you enable the solution, the workspace takes a few minutes to be displayed.
7171

7272
Unlike Log Analytics agents, the Network Performance Monitor solution can be configured to send data only to a single Log Analytics workspace.
7373

@@ -87,6 +87,7 @@ Although this coexistence allows you to begin the transition, there are certain
8787

8888
* 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.
8989

90-
## Next steps
90+
## Next step
9191

92-
- [Install the Azure Connected Machine agent](connection-monitor-connected-machine-agent.md)
92+
> [!div class="nextstepaction"]
93+
> [Install the Azure Connected Machine agent](connection-monitor-connected-machine-agent.md)

0 commit comments

Comments
 (0)