Skip to content

Commit 8250eff

Browse files
Add files via upload
1 parent 5d86a0b commit 8250eff

File tree

1 file changed

+34
-0
lines changed

1 file changed

+34
-0
lines changed
Lines changed: 34 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,34 @@
1+
---
2+
title: Data Field Differences between MMA and AMA
3+
description: Documents that field lever data changes made in the migration.
4+
author: jeffwo-MSFT
5+
ms.author: jeffwo
6+
ms.reviewer: guywild
7+
ms.topic: reference
8+
ms.date: 06/21/2024
9+
10+
# Customer intent: As an azure administrator, I want to understand which Log Analytics Workspace queries I may need to update after AMA migration.
11+
12+
---
13+
14+
# Purpose
15+
[Azure Monitor Agent (AMA)](./agents-overview.md) replaces the Log Analytics agent, also known as Microsoft Monitor Agent (MMA) and OMS, for Windows and Linux machines, in Azure and non-Azure environments, on-premises and other clouds. The agent introduces a simplified, flexible method of configuring data collection using [Data Collection Rules (DCRs)](../essentials/data-collection-rule-overview.md). This article provides information on the data fields that will change in a log Analytics Workspace after the migration to AMA. This provides critical information to you for the migration of LAW data queries.
16+
Each of the data changes was carefully considered and the rational for each change is provided in the table below. If you encounter a date element change that is not in the tables in this article, please file a support request. This will help us keep the tables current and complete.
17+
# Log Analytics Workspace Tables
18+
## W3CIISLog Table
19+
This table collects log data from the Internet Information Service on Window systems.
20+
|LAW Field | Difference | Reason| Additional Information |
21+
| sSiteName | may not be populated | depends on customer data collection configuration | The MMA agent could turn on collection by default, but the AMA is prevented by principle from making configuration changes in other services.<p>Enable the `Service Name (s-sitename)` field in W3C logging of IIS, see [Select W3C Fields to Log](/iis/manage/provisioning-and-managing-iis/configure-logging-in-iis#select-w3c-fields-to-log).|
22+
| Fileuri | No longer populated | not required for MMA parity | This field was only populated for IIS logs collected from Azure Cloud Services through the Azure Diagnostics Extension. It was not collected by MMA and thus is not collected by AMA|
23+
24+
> [!IMPORTANT]
25+
> The
26+
27+
## Before
28+
29+
## High level guidance
30+
31+
## Next steps
32+
- [Azure Monitor Agent migration helper workbook](./azure-monitor-agent-migration-helper-workbook.md)
33+
- [DCR Config Generator](./azure-monitor-agent-migration-data-collection-rule-generator.md)
34+
- [MMA Discovery and Removal tool](/azure/azure-monitor/agents/azure-monitor-agent-mma-removal-tool?tabs=single-tenant%2Cdiscovery)

0 commit comments

Comments
 (0)