Skip to content

Commit 6b74ad5

Browse files
guywi-msguywi-ms
committed
move content from AMA overview
1 parent 194de57 commit 6b74ad5

File tree

3 files changed

+87
-88
lines changed

3 files changed

+87
-88
lines changed

‎articles/azure-monitor/agents/agents-overview.md

Lines changed: 0 additions & 87 deletions
Original file line numberDiff line numberDiff line change
@@ -85,93 +85,6 @@ Azure Monitor Agent is available in all public regions and Azure Government clou
8585

8686
There's no cost for the Azure Monitor Agent, but you might incur charges for the data ingested. For information on Log Analytics data collection and retention and for customer metrics, see [Azure Monitor pricing](https://azure.microsoft.com/pricing/details/monitor/).
8787

88-
## Networking
89-
90-
The Azure Monitor Agent supports Azure service tags. Both *AzureMonitor* and *AzureResourceManager* tags are required. It supports connecting via *direct proxies, Log Analytics gateway, and private links* as described in the following sections.
91-
92-
### Firewall requirements
93-
94-
| Cloud |Endpoint |Purpose |Port |Direction |Bypass HTTPS inspection|
95-
|------|------|------|---------|--------|--------|
96-
| Azure Commercial |global.handler.control.monitor.azure.com |Access control service|Port 443 |Outbound|Yes |
97-
| Azure Commercial |`<virtual-machine-region-name>`.handler.control.monitor.azure.com |Fetch data collection rules for specific machine |Port 443 |Outbound|Yes |
98-
| Azure Commercial |`<log-analytics-workspace-id>`.ods.opinsights.azure.com |Ingest logs data |Port 443 |Outbound|Yes |
99-
| Azure Commercial | management.azure.com | Only needed if sending time series data (metrics) to Azure Monitor [Custom metrics](../essentials/metrics-custom-overview.md) database | Port 443 | Outbound | Yes |
100-
| Azure Government | Replace '.com' above with '.us' | Same as above | Same as above | Same as above| Same as above |
101-
| Azure China | Replace '.com' above with '.cn' | Same as above | Same as above | Same as above| Same as above |
102-
103-
If you use private links on the agent, you must also add the [DCE endpoints](../essentials/data-collection-endpoint-overview.md#components-of-a-data-collection-endpoint).
104-
105-
### Proxy configuration
106-
107-
If the machine connects through a proxy server to communicate over the internet, review the following requirements to understand the network configuration required.
108-
109-
The Azure Monitor Agent extensions for Windows and Linux can communicate either through a proxy server or a [Log Analytics gateway](./gateway.md) to Azure Monitor by using the HTTPS protocol. Use it for Azure virtual machines, Azure virtual machine scale sets, and Azure Arc for servers. Use the extensions settings for configuration as described in the following steps. Both anonymous and basic authentication by using a username and password are supported.
110-
111-
> [!IMPORTANT]
112-
> Proxy configuration is not supported for [Azure Monitor Metrics (Public preview)](../essentials/metrics-custom-overview.md) as a destination. If you're sending metrics to this destination, it will use the public internet without any proxy.
113-
114-
1. Use this flowchart to determine the values of the *`Settings` and `ProtectedSettings` parameters first.
115-
116-
![Diagram that shows a flowchart to determine the values of settings and protectedSettings parameters when you enable the extension.](media/azure-monitor-agent-overview/proxy-flowchart.png)
117-
118-
1. After determining the `Settings` and `ProtectedSettings` parameter values, *provide these other parameters* when you deploy Azure Monitor Agent, using PowerShell commands, as shown in the following examples:
119-
120-
# [Windows VM](#tab/PowerShellWindows)
121-
122-
```powershell
123-
$settingsString = @{"proxy" = @{mode = "application"; address = "http://[address]:[port]"; auth = true}}
124-
$protectedSettingsString = @{"proxy" = @{username = "[username]"; password = "[password]"}}
125-
126-
Set-AzVMExtension -ExtensionName AzureMonitorWindowsAgent -ExtensionType AzureMonitorWindowsAgent -Publisher Microsoft.Azure.Monitor -ResourceGroupName <resource-group-name> -VMName <virtual-machine-name> -Location <location> -TypeHandlerVersion 1.0 -SettingString $settingsString -ProtectedSettingString $protectedSettingsString
127-
```
128-
129-
# [Linux VM](#tab/PowerShellLinux)
130-
131-
```powershell
132-
$settingsString = @{"proxy" = @{mode = "application"; address = "http://[address]:[port]"; auth = true}}
133-
$protectedSettingsString = @{"proxy" = @{username = "[username]"; password = "[password]"}}
134-
135-
Set-AzVMExtension -ExtensionName AzureMonitorLinuxAgent -ExtensionType AzureMonitorLinuxAgent -Publisher Microsoft.Azure.Monitor -ResourceGroupName <resource-group-name> -VMName <virtual-machine-name> -Location <location> -TypeHandlerVersion 1.5 -SettingString $settingsString -ProtectedSettingString $protectedSettingsString
136-
```
137-
138-
# [Windows Arc-enabled server](#tab/PowerShellWindowsArc)
139-
140-
```powershell
141-
$settingsString = @{"proxy" = @{mode = "application"; address = "http://[address]:[port]"; auth = true}}
142-
$protectedSettingsString = @{"proxy" = @{username = "[username]"; password = "[password]"}}
143-
144-
New-AzConnectedMachineExtension -Name AzureMonitorWindowsAgent -ExtensionType AzureMonitorWindowsAgent -Publisher Microsoft.Azure.Monitor -ResourceGroupName <resource-group-name> -MachineName <arc-server-name> -Location <arc-server-location> -Setting $settingsString -ProtectedSetting $protectedSettingsString
145-
```
146-
147-
# [Linux Arc-enabled server](#tab/PowerShellLinuxArc)
148-
149-
```powershell
150-
$settingsString = @{"proxy" = @{mode = "application"; address = "http://[address]:[port]"; auth = true}}
151-
$protectedSettingsString = @{"proxy" = @{username = "[username]"; password = "[password]"}}
152-
153-
New-AzConnectedMachineExtension -Name AzureMonitorLinuxAgent -ExtensionType AzureMonitorLinuxAgent -Publisher Microsoft.Azure.Monitor -ResourceGroupName <resource-group-name> -MachineName <arc-server-name> -Location <arc-server-location> -Setting $settingsString -ProtectedSetting $protectedSettingsString
154-
```
155-
156-
---
157-
158-
### Log Analytics gateway configuration
159-
160-
1. Follow the preceding instructions to configure proxy settings on the agent and provide the IP address and port number that corresponds to the gateway server. If you've deployed multiple gateway servers behind a load balancer, the agent proxy configuration is the virtual IP address of the load balancer instead.
161-
1. Add the **configuration endpoint URL** to fetch data collection rules to the allowlist for the gateway
162-
`Add-OMSGatewayAllowedHost -Host global.handler.control.monitor.azure.com`
163-
`Add-OMSGatewayAllowedHost -Host <gateway-server-region-name>.handler.control.monitor.azure.com`.
164-
(If you're using private links on the agent, you must also add the [data collection endpoints](../essentials/data-collection-endpoint-overview.md#components-of-a-data-collection-endpoint).)
165-
1. Add the **data ingestion endpoint URL** to the allowlist for the gateway
166-
`Add-OMSGatewayAllowedHost -Host <log-analytics-workspace-id>.ods.opinsights.azure.com`.
167-
1. Restart the **OMS Gateway** service to apply the changes
168-
`Stop-Service -Name <gateway-name>`
169-
`Start-Service -Name <gateway-name>`.
170-
171-
### Private link configuration
172-
173-
To configure the agent to use private links for network communications with Azure Monitor, follow instructions to [enable network isolation](./azure-monitor-agent-data-collection-endpoint.md#enable-network-isolation-for-the-azure-monitor-agent) by using [data collection endpoints](azure-monitor-agent-data-collection-endpoint.md).
174-
17588
## Compare to legacy agents
17689

17790
The tables below provide a comparison of Azure Monitor Agent with the legacy the Azure Monitor telemetry agents for Windows and Linux.

‎articles/azure-monitor/agents/azure-monitor-agent-data-collection-endpoint.md

Lines changed: 86 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -9,6 +9,92 @@ ms.custom: references_region
99
ms.reviewer: shseth
1010

1111
---
12+
## Set Azure Monitor Agent network configuration
13+
14+
The Azure Monitor Agent supports Azure service tags. Both *AzureMonitor* and *AzureResourceManager* tags are required. It supports connecting via *direct proxies, Log Analytics gateway, and private links* as described in the following sections.
15+
16+
### Firewall requirements
17+
18+
| Cloud |Endpoint |Purpose |Port |Direction |Bypass HTTPS inspection|
19+
|------|------|------|---------|--------|--------|
20+
| Azure Commercial |global.handler.control.monitor.azure.com |Access control service|Port 443 |Outbound|Yes |
21+
| Azure Commercial |`<virtual-machine-region-name>`.handler.control.monitor.azure.com |Fetch data collection rules for specific machine |Port 443 |Outbound|Yes |
22+
| Azure Commercial |`<log-analytics-workspace-id>`.ods.opinsights.azure.com |Ingest logs data |Port 443 |Outbound|Yes |
23+
| Azure Commercial | management.azure.com | Only needed if sending time series data (metrics) to Azure Monitor [Custom metrics](../essentials/metrics-custom-overview.md) database | Port 443 | Outbound | Yes |
24+
| Azure Government | Replace '.com' above with '.us' | Same as above | Same as above | Same as above| Same as above |
25+
| Azure China | Replace '.com' above with '.cn' | Same as above | Same as above | Same as above| Same as above |
26+
27+
If you use private links on the agent, you must also add the [DCE endpoints](../essentials/data-collection-endpoint-overview.md#components-of-a-data-collection-endpoint).
28+
29+
### Proxy configuration
30+
31+
If the machine connects through a proxy server to communicate over the internet, review the following requirements to understand the network configuration required.
32+
33+
The Azure Monitor Agent extensions for Windows and Linux can communicate either through a proxy server or a [Log Analytics gateway](./gateway.md) to Azure Monitor by using the HTTPS protocol. Use it for Azure virtual machines, Azure virtual machine scale sets, and Azure Arc for servers. Use the extensions settings for configuration as described in the following steps. Both anonymous and basic authentication by using a username and password are supported.
34+
35+
> [!IMPORTANT]
36+
> Proxy configuration is not supported for [Azure Monitor Metrics (Public preview)](../essentials/metrics-custom-overview.md) as a destination. If you're sending metrics to this destination, it will use the public internet without any proxy.
37+
38+
1. Use this flowchart to determine the values of the *`Settings` and `ProtectedSettings` parameters first.
39+
40+
![Diagram that shows a flowchart to determine the values of settings and protectedSettings parameters when you enable the extension.](media/azure-monitor-agent-overview/proxy-flowchart.png)
41+
42+
1. After determining the `Settings` and `ProtectedSettings` parameter values, *provide these other parameters* when you deploy Azure Monitor Agent, using PowerShell commands, as shown in the following examples:
43+
44+
# [Windows VM](#tab/PowerShellWindows)
45+
46+
```powershell
47+
$settingsString = @{"proxy" = @{mode = "application"; address = "http://[address]:[port]"; auth = true}}
48+
$protectedSettingsString = @{"proxy" = @{username = "[username]"; password = "[password]"}}
49+
50+
Set-AzVMExtension -ExtensionName AzureMonitorWindowsAgent -ExtensionType AzureMonitorWindowsAgent -Publisher Microsoft.Azure.Monitor -ResourceGroupName <resource-group-name> -VMName <virtual-machine-name> -Location <location> -TypeHandlerVersion 1.0 -SettingString $settingsString -ProtectedSettingString $protectedSettingsString
51+
```
52+
53+
# [Linux VM](#tab/PowerShellLinux)
54+
55+
```powershell
56+
$settingsString = @{"proxy" = @{mode = "application"; address = "http://[address]:[port]"; auth = true}}
57+
$protectedSettingsString = @{"proxy" = @{username = "[username]"; password = "[password]"}}
58+
59+
Set-AzVMExtension -ExtensionName AzureMonitorLinuxAgent -ExtensionType AzureMonitorLinuxAgent -Publisher Microsoft.Azure.Monitor -ResourceGroupName <resource-group-name> -VMName <virtual-machine-name> -Location <location> -TypeHandlerVersion 1.5 -SettingString $settingsString -ProtectedSettingString $protectedSettingsString
60+
```
61+
62+
# [Windows Arc-enabled server](#tab/PowerShellWindowsArc)
63+
64+
```powershell
65+
$settingsString = @{"proxy" = @{mode = "application"; address = "http://[address]:[port]"; auth = true}}
66+
$protectedSettingsString = @{"proxy" = @{username = "[username]"; password = "[password]"}}
67+
68+
New-AzConnectedMachineExtension -Name AzureMonitorWindowsAgent -ExtensionType AzureMonitorWindowsAgent -Publisher Microsoft.Azure.Monitor -ResourceGroupName <resource-group-name> -MachineName <arc-server-name> -Location <arc-server-location> -Setting $settingsString -ProtectedSetting $protectedSettingsString
69+
```
70+
71+
# [Linux Arc-enabled server](#tab/PowerShellLinuxArc)
72+
73+
```powershell
74+
$settingsString = @{"proxy" = @{mode = "application"; address = "http://[address]:[port]"; auth = true}}
75+
$protectedSettingsString = @{"proxy" = @{username = "[username]"; password = "[password]"}}
76+
77+
New-AzConnectedMachineExtension -Name AzureMonitorLinuxAgent -ExtensionType AzureMonitorLinuxAgent -Publisher Microsoft.Azure.Monitor -ResourceGroupName <resource-group-name> -MachineName <arc-server-name> -Location <arc-server-location> -Setting $settingsString -ProtectedSetting $protectedSettingsString
78+
```
79+
80+
---
81+
82+
### Log Analytics gateway configuration
83+
84+
1. Follow the preceding instructions to configure proxy settings on the agent and provide the IP address and port number that corresponds to the gateway server. If you've deployed multiple gateway servers behind a load balancer, the agent proxy configuration is the virtual IP address of the load balancer instead.
85+
1. Add the **configuration endpoint URL** to fetch data collection rules to the allowlist for the gateway
86+
`Add-OMSGatewayAllowedHost -Host global.handler.control.monitor.azure.com`
87+
`Add-OMSGatewayAllowedHost -Host <gateway-server-region-name>.handler.control.monitor.azure.com`.
88+
(If you're using private links on the agent, you must also add the [data collection endpoints](../essentials/data-collection-endpoint-overview.md#components-of-a-data-collection-endpoint).)
89+
1. Add the **data ingestion endpoint URL** to the allowlist for the gateway
90+
`Add-OMSGatewayAllowedHost -Host <log-analytics-workspace-id>.ods.opinsights.azure.com`.
91+
1. Restart the **OMS Gateway** service to apply the changes
92+
`Stop-Service -Name <gateway-name>`
93+
`Start-Service -Name <gateway-name>`.
94+
95+
### Private link configuration
96+
97+
To configure the agent to use private links for network communications with Azure Monitor, follow instructions to [enable network isolation](./azure-monitor-agent-data-collection-endpoint.md#enable-network-isolation-for-the-azure-monitor-agent) by using [data collection endpoints](azure-monitor-agent-data-collection-endpoint.md).
1298

1399
# Enable network isolation for the Azure Monitor agent
14100
By default, Azure Monitor agent will connect to a public endpoint to connect to your Azure Monitor environment. You can enable network isolation for your agents by creating [data collection endpoints](../essentials/data-collection-endpoint-overview.md) and adding them to your [Azure Monitor Private Link Scopes (AMPLS)](../logs/private-link-configure.md#connect-azure-monitor-resources).

‎articles/azure-monitor/toc.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -482,7 +482,7 @@ items:
482482
- name: Collect text and IIS Logs
483483
displayName: data collection rule,Azure Monitor agent
484484
href: agents/data-collection-text-log.md
485-
- name: Enable network isolation
485+
- name: Set network configuration
486486
href: agents/azure-monitor-agent-data-collection-endpoint.md
487487
- name: Migrate from Log Analytics Agent
488488
items:

0 commit comments

Comments
 (0)