Skip to content

Commit 9537511

Browse files
v-dirichardsv-dirichards
authored
Merge pull request #278396 from EdB-MSFT/agent-migration-2
Agent migration 2
2 parents 9e215a8 + 51b4d10 commit 9537511

20 files changed

+388
-280
lines changed

‎.openpublishing.redirection.azure-monitor.json

Lines changed: 6 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -6738,9 +6738,11 @@
67386738
"source_path_from_root": "/articles/azure-monitor/essentials/pipeline-overview.md",
67396739
"redirect_url": "/azure/azure-monitor/essentials/data-collection-rule-overview",
67406740
"redirect_document_id": false
6741-
}
6742-
6743-
6744-
6741+
},
6742+
{
6743+
"source_path_from_root": "/articles/azure-monitor/agents/azure-monitor-agent-migration-tools.md",
6744+
"redirect_url": "/azure/azure-monitor/agents/azure-monitor-agent-migration",
6745+
"redirect_document_id": false
6746+
}
67456747
]
67466748
}

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

Lines changed: 20 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -57,7 +57,7 @@ Azure Monitor Agent uses [data collection rules](../essentials/data-collection-r
5757

5858
| Resource type | Installation method | More information |
5959
|:---|:---|:---|
60-
| Virtual machines and VM scale sets | [Virtual machine extension](./azure-monitor-agent-manage.md#virtual-machine-extension-details) | Installs the agent by using Azure extension framework. |
60+
| Azure Virtual Machines and Azure Virtual Machine Scale Sets | [Virtual machine extension](./azure-monitor-agent-manage.md#virtual-machine-extension-details) | Installs the agent by using Azure extension framework. |
6161
| On-premises Arc-enabled servers | [Virtual machine extension](./azure-monitor-agent-manage.md#virtual-machine-extension-details) (after installing the [Azure Arc agent](../../azure-arc/servers/deployment-options.md)) | Installs the agent by using Azure extension framework, provided for on-premises by first installing [Azure Arc agent](../../azure-arc/servers/deployment-options.md). |
6262
| Windows 10, 11 Client Operating Systems | [Client installer](./azure-monitor-agent-windows-client.md) | Installs the agent by using a Windows MSI installer. The installer works on laptops, but the agent *isn't optimized yet* for battery or network consumption. |
6363

@@ -86,7 +86,20 @@ Azure Monitor Agent uses [data collection rules](../essentials/data-collection-r
8686
8787
## Supported services and features
8888

89-
For a list of features and services that use Azure Monitor Agent for data collection, see [Migrate to Azure Monitor Agent from Log Analytics agent](../agents/azure-monitor-agent-migration.md#migrate-additional-services-and-features).
89+
Azure Monitor Agent is generally available (GA) for data collection. Most services that used Log Analytics agent for data collection have migrated to Azure Monitor Agent.
90+
91+
The following features and services now have an Azure Monitor Agent version available:
92+
93+
| Service or feature | Current state | More information |
94+
|-----------------------------------|---------------|-------------------------------------------------------|
95+
| VM insights, Service Map, and Dependency agent | GA | [Enable VM Insights](/azure/azure-monitor/vm/vminsights-enable-overview) |
96+
| Microsoft Sentinel | Public Preview| [AMA migration for Microsoft Sentinel](/azure/sentinel/ama-migrate) |
97+
| Change Tracking and Inventory | GA | [Migration for Change Tracking and inventory](/azure/automation/change-tracking/guidance-migration-log-analytics-monitoring-agent) |
98+
| Network Watcher | GA | [Monitor network connectivity using connection monitor](/azure/network-watcher/azure-monitor-agent-with-connection-monitor) |
99+
| Azure Stack HCI Insights | GA | [Monitor Azure Stack HCI with Insights](/azure-stack/hci/manage/monitor-hci-single) |
100+
| Azure Virtual Desktop (AVD) Insights | GA | [Azure Virtual Desktop Insights](/azure/virtual-desktop/insights?tabs=monitor#session-host-data-settings) |
101+
| Container Monitoring Solution | GA | [Enable Container Insights](/azure/azure-monitor/containers/container-insights-transition-solution) |
102+
| DNS Collector | GA | [Enable DNS Connector](/azure/sentinel/connect-dns-ama) |
90103

91104
## Supported regions
92105

@@ -117,7 +130,7 @@ The tables below provide a comparison of Azure Monitor Agent with the legacy the
117130
| **Data sent to** | | | |
118131
| | Azure Monitor Logs | ✓ | ✓ |
119132
| **Services and features supported** | | | |
120-
| | Microsoft Sentinel | ✓ ([View scope](./azure-monitor-agent-migration.md#migrate-additional-services-and-features)) | ✓ |
133+
| | Microsoft Sentinel | ✓ ([View scope](./azure-monitor-agent-migration.md#understand-additional-dependencies-and-services)) | ✓ |
121134
| | VM Insights | ✓ | ✓ |
122135
| | Microsoft Defender for Cloud - Only uses MDE agent | | |
123136
| | Automation Update Management - Moved to Azure Update Manager | ✓ | ✓ |
@@ -141,7 +154,7 @@ The tables below provide a comparison of Azure Monitor Agent with the legacy the
141154
| **Data sent to** | | | |
142155
| | Azure Monitor Logs | ✓ | ✓ |
143156
| **Services and features supported** | | | |
144-
| | Microsoft Sentinel | ✓ ([View scope](./azure-monitor-agent-migration.md#migrate-additional-services-and-features)) | ✓ |
157+
| | Microsoft Sentinel | ✓ ([View scope](./azure-monitor-agent-migration.md#understand-additional-dependencies-and-services)) | ✓ |
145158
| | VM Insights | ✓ | ✓ |
146159
| | Microsoft Defender for Cloud - Only use MDE agent | | |
147160
| | Automation Update Management - Moved to Azure Update Manager | ✓ | ✓ |
@@ -226,7 +239,7 @@ View [supported operating systems for Azure Arc Connected Machine agent](../../a
226239
> Machines and appliances that run heavily customized or stripped-down versions of the above distributions and hosted solutions that disallow customization by the user are not supported. Azure Monitor and legacy agents rely on various packages and other baseline functionality that is often removed from such systems, and their installation may require some environmental modifications considered to be disallowed by the appliance vendor. For instance, [GitHub Enterprise Server](https://docs.github.com/en/enterprise-server/admin/overview/about-github-enterprise-server) is not supported due to heavy customization as well as [documented, license-level disallowance](https://docs.github.com/en/enterprise-server/admin/overview/system-overview#operating-system-software-and-patches) of operating system modification.
227240
228241
> [!NOTE]
229-
> CBL-Mariner 2.0's disk size is by default around 1GB to provide storage savings, compared to other Azure VMs that are around 30GB. However, the Azure Monitor Agent requires at least 4GB disk size in order to install and run successfully. Please check out [CBL-Mariner's documentation](https://eng.ms/docs/products/mariner-linux/gettingstarted/azurevm/azurevm#disk-size) for more information and instructions on how to increase disk size before installing the agent.
242+
> CBL-Mariner 2.0's disk size is by default around 1GB to provide storage savings, compared to other Azure Virtual Machines that are around 30GB. However, the Azure Monitor Agent requires at least 4GB disk size in order to install and run successfully. Please check out [CBL-Mariner's documentation](https://eng.ms/docs/products/mariner-linux/gettingstarted/azurevm/azurevm#disk-size) for more information and instructions on how to increase disk size before installing the agent.
230243
231244
### Hardening Standards
232245

@@ -270,9 +283,9 @@ An agent is only required to collect data from the operating system and workload
270283

271284
### Does Azure Monitor Agent support data collection for the various Log Analytics solutions and Azure services like Microsoft Defender for Cloud and Microsoft Sentinel?
272285

273-
For a list of features and services that use Azure Monitor Agent for data collection, see [Migrate to Azure Monitor Agent from Log Analytics agent](../agents/azure-monitor-agent-migration.md#migrate-additional-services-and-features).
286+
Yes, Azure Monitor Agent supports data collection for various Log Analytics solutions and Azure services like Microsoft Defender for Cloud and Microsoft Sentinel.
274287

275-
Some services might install other extensions to collect more data or to transforms or process data, and then use Azure Monitor Agent to route the final data to Azure Monitor.
288+
Some services might install other extensions to collect more data or to transforms or process data, and then use Azure Monitor Agent to route the final data to Azure Monitor. For more information, see [Migrate to Azure Monitor Agent from Log Analytics agent](./azure-monitor-agent-migration.md#understand-additional-dependencies-and-services).
276289

277290
The following diagram explains the new extensibility architecture.
278291

‎articles/azure-monitor/agents/azure-monitor-agent-migration-data-collection-rule-generator.md

Lines changed: 81 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,81 @@
1+
---
2+
title: Workspace configuration to DCR config generator
3+
description: Using the Workspace configuration to DCR config generator to help migrate from MMA to AMA agents
4+
author: EdB-MSFT
5+
ms.author: edbaynash
6+
ms.reviewer: guywild
7+
ms.topic: conceptual
8+
ms.date: 06/16/2024
9+
10+
# Customer intent: As an azure administrator, I want to understand how to use the workspace configuration to DCR config generator.
11+
12+
---
13+
14+
# Convert workspace configuration to DCR configurations
15+
16+
Whereas Log Analytics Agent inherits its configuration from Log Analytics workspaces, the Azure Monitor Agent relies on data collection rules (DCRs) for configuration
17+
18+
The workspace configuration to DCR config generator is a PowerShell that reads the configuration from your workspace produce multiple DCR ARM templates, based on the MMA configurations present on the workspace.
19+
20+
## Prerequisites
21+
- PowerShell version 7.1.3 or higher is recommended (minimum version 5.1)
22+
- Az PowerShell module to pull workspace agent configuration information Az PowerShell module. To install the Az PowerShell module, see [Install Azure PowerShell on Windows](/powershell/azure/install-azps-windows)
23+
- Read/Write access to the specified workspace resource
24+
25+
## Installation and execution
26+
27+
Download the [PowerShell script](https://github.com/microsoft/AzureMonitorCommunity/tree/master/Azure%20Services/Azure%20Monitor/Agents/Migration%20Tools/DCR%20Config%20Generator) from Git Hub.
28+
29+
30+
The script retrieves the configuration of the legacy agent configurations from the workspace and generates DCR ARM templates for each supported DCR type in the specified output folder. More than one template may be created, one for each DCR type.
31+
32+
For multiple workspaces with data collections configured, you must run the script for each workspace. IIS logs the script also creates an additional data collection role as part of that configuration.
33+
34+
35+
When the script completes, it prompts you to test the deployment of the template in your environment. Choose to either let it deploy the template for you, or store the template specified output folder
36+
37+
> [!NOTE]
38+
> The script does not associate the DCRs with the workspace. You must create your own data collection rule associations (DCRAs), to associate the DCRs with the relevant servers. This allows you to control the deployment of the DCRs to the servers and test the DCRs on a sample of servers before deploying at scale.
39+
40+
41+
To run script, copy the following command and replace the parameters with your values:
42+
43+
```powershell
44+
.\WorkspaceConfigToDCRMigrationTool.ps1 -SubscriptionId $subId -ResourceGroupName $rgName -WorkspaceName $workspaceName -DCRName $dcrName -OutputFolder $outputFolderPath
45+
```
46+
47+
### Script parameters
48+
49+
50+
| Name | Required | Description |
51+
| ----------------------- |:---------:|:-----------------------------------------------------------------------------:|
52+
| `SubscriptionId` | YES | The subscription ID of the workspace |
53+
| `ResourceGroupName` | YES | The resource Group of the workspace |
54+
| `WorkspaceName` | YES | The name of the workspace (Azure resource IDs are case insensitive) |
55+
| `DCRName` | YES | The base name used for each one the outputs DCRs |
56+
| `OutputFolder` | NO | The output folder path. If not provided, the working directory path is used |
57+
58+
59+
### Outputs:
60+
- For each supported `DCR type`, the script produces a ready to be deployed DCR ARM template and a DCR payload, for users that don't need the ARM template.
61+
62+
Currently supported DCR types:
63+
64+
- **Windows** contains `WindowsPerfCounters` and `WindowsEventLogs` data sources only
65+
- **Linux** contains `LinuxPerfCounters` and `Syslog` data sources only
66+
- **Custom Logs** contains `logFiles` data sources only
67+
- **IIS Logs** contains `iisLogs` data sources only
68+
- **Extensions** contains `extensions` data sources only along with any associated perfCounters data sources
69+
- `VMInsights`
70+
71+
## Deployment
72+
73+
For information on deploying the DCRs, see [Data collection rules in Azure Monitor](/azure/azure-monitor/essentials/data-collection-rule-overview) and [Create and edit data collection rules (DCRs) in Azure Monitor](/azure/azure-monitor/essentials/data-collection-rule-create-edit)
74+
75+
76+
## Next steps
77+
78+
- [Azure Monitor Agent Migration Helper workbook](azure-monitor-agent-migration-helper-workbook.md)
79+
- [Data collection rule structure](../essentials/data-collection-rule-structure.md)
80+
- [Sample data collection rules (DCRs)](../essentials/data-collection-rule-samples.md) for sample DCRs for different data collection scenarios.
81+
- [Azure Monitor service limits](../service-limits.md#data-collection-rules) for limits that apply to each DCR.

0 commit comments

Comments
 (0)