Skip to content

Commit cab7bf2

Browse files
committed
Update azure-monitor-agent-migration.md
1 parent 7ab0e5c commit cab7bf2

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/azure-monitor/agents/azure-monitor-agent-migration.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -56,7 +56,7 @@ Before you begin migrating from the Log Analytics agent to Azure Monitor Agent,
5656

5757
1. Compare the data ingested by Azure Monitor Agent with legacy agent data to ensure there are no gaps. You can do this on any table by using the [join operator](/azure/data-explorer/kusto/query/joinoperator?pivots=azuremonitor) to add the `Category` column from the [Heartbeat](/azure/azure-monitor/reference/tables/heartbeat) table, which indicates `Azure Monitor Agent` for data collected by the Azure Monitor Agent.
5858

59-
For example:
59+
For example, this query adds the `Category` column from the `Heartbeat` table to data retrieved from the `Event` table:
6060

6161
```kusto
6262
Heartbeat

0 commit comments

Comments
 (0)