Skip to content

Commit 2c6407f

Browse files
authored
Merge pull request #279259 from JeffreyWolford/patch-22
New data difference page
2 parents 7c82c85 + 48844e4 commit 2c6407f

File tree

2 files changed

+35
-0
lines changed

2 files changed

+35
-0
lines changed
Lines changed: 33 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,33 @@
1+
---
2+
title: Data field differences between MMA and AMA
3+
4+
description: Documents that field lever data changes made in the migration.
5+
author: JeffreyWolford
6+
ms.author: jeffwo
7+
ms.reviewer: guywild
8+
ms.topic: reference
9+
ms.date: 06/21/2024
10+
11+
Customer intent: As an azure administrator, I want to understand which Log Analytics Workspace queries I may need to update after AMA migration.
12+
13+
---
14+
15+
# AMA agent data field differences from MMA
16+
[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). The article provides information on the data fields that change when collected by AMA, which is critical information for you to migrate your LAW queries.
17+
18+
Each of the data changes was carefully considered and the rational for each change is provided in the table. If you encounter a data field that isn't in the tables file a support request. Your help keeping the tables current and complete is appreciated.
19+
20+
## Log analytics workspace tables
21+
### W3CIISLog Table for Internet Information Services (IIS)
22+
This table collects log data from the Internet Information Service on Window systems.
23+
24+
|LAW Field | Difference | Reason| Additional Information |
25+
|---|---|---|---|
26+
| sSiteName | Not be populated | depends on customer data collection configuration | The MMA agent could turn on collection by default, but by principle is restricted 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).|
27+
| Fileuri | No longer populated | not required for MMA parity | MMA doesn't collect this field. This field was only populated for IIS logs collected from Azure Cloud Services through the Azure Diagnostics Extension.|
28+
29+
30+
## Next steps
31+
- [Azure Monitor Agent migration helper workbook](./azure-monitor-agent-migration-helper-workbook.md)
32+
- [DCR Config Generator](./azure-monitor-agent-migration-data-collection-rule-generator.md)
33+

articles/azure-monitor/toc.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -752,6 +752,8 @@ items:
752752
href: agents/azure-monitor-agent-migration-data-collection-rule-generator.md
753753
- name: MMA removal tool
754754
href: agents/azure-monitor-agent-mma-removal-tool.md
755+
- name: AMA data field differences from MMA
756+
href: agents/azure-monitor-agent-data-field-differences.md
755757
- name: Migration custom text log tables
756758
href: agents/azure-monitor-agent-custom-text-log-migration.md
757759
- name: Performance

0 commit comments

Comments
 (0)