Skip to content

Commit d6426a9

Browse files
committed
Minor changes to language and formatting
1 parent 1b437d4 commit d6426a9

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/azure-monitor/agents/azure-monitor-agent-data-field-differences.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -32,16 +32,16 @@ This table collects Events from the Windows Event log. There are two other table
3232

3333
|LAW Field | Difference | Reason| Additional Information |
3434
|---|---|---|---|
35-
| UserName | MMA enriches the event with the username before sending the event for ingestion. AMA doesn't do the same enrichment. | The AMA enrichment isn't implemented yet. | AMA principles dictate that the event data should remain unchanged by default. Adding and enriched field adds possible processing errors and additional costs for storage. In this case, the customer demand for the field is very high and work is underway to add the username. |
35+
| UserName | MMA enriches the event with the username before sending the event for ingestion. AMA doesn't do the same enrichment. | The AMA enrichment isn't implemented yet. | AMA principles dictate that the event data should remain unchanged by default. Adding and enriched field adds possible processing errors and extra costs for storage. In this case, the customer demand for the field is very high and work is underway to add the username. |
3636

3737
### Perf Table for Performance Counters
3838

3939
The Perf table collects performance counters from Windows and Linux agents. It offers valuable insights into the performance of hardware components, operating systems, and applications. The following table shows key differences in how data is reported between OMS and Azure Monitor Agent (AMA).
4040

4141
| LAW Field | Difference | Reason | Additional Information |
4242
|--------------|------------|--------|------------------------|
43-
| InstanceName | Reported as **_Total** by OMS<br>Reported as **total** by AMA | | Where `ObjectName == "Logical Disk"` and `CounterName == "% Used Space"`, the InstanceName value is reported as **_Total** for records ingested by the OMS agent, whereas it's reported as **total** for records ingested by the Azure Monitor Agent (AMA).\* |
44-
| CounterValue | Is rounded to the nearest whole number by OMS but not rounded by AMA | | Where `ObjectName == "Logical Disk"` and `CounterName == "% Used Space"`, the CounterValue is value is rounded to the nearest whole number for records ingested by the OMS agent but not rounded for records ingested by the Azure Monitor Agent (AMA).\* |
43+
| InstanceName | Reported as **_Total** by OMS<br>Reported as **total** by AMA | | Where `ObjectName == "Logical Disk"` and `CounterName == "% Used Space"`, the `InstanceName` value is reported as **_Total** for records ingested by the OMS agent, and as **total** for records ingested by the Azure Monitor Agent (AMA).\* |
44+
| CounterValue | Is rounded to the nearest whole number by OMS but not rounded by AMA | | Where `ObjectName == "Logical Disk"` and `CounterName == "% Used Space"`, the `CounterValue` value is rounded to the nearest whole number for records ingested by the OMS agent but not rounded for records ingested by the Azure Monitor Agent (AMA).\* |
4545

4646
\* Doesn't apply to records ingested by the Microsoft Monitoring Agent (MMA) on Windows.
4747

0 commit comments

Comments
 (0)