Skip to content

Commit 3eef921

Browse files
Update data-collection.md
1 parent 5401010 commit 3eef921

File tree

1 file changed

+4
-0
lines changed

1 file changed

+4
-0
lines changed

articles/azure-monitor/essentials/data-collection.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -31,6 +31,10 @@ See [Data collection transformations in Azure Monitor](data-collection-transform
3131
The following sections describe the data collection scenarios that are currently supported using DCR and the new data ingestion pipeline.
3232

3333
### Azure Monitor agent
34+
35+
>[!IMPORTANT]
36+
>The Log Analytics agent is on a **deprecation path** and won't be supported after **August 31, 2024**. Any new data centers brought online after January 1 2024 will not support the Log Analytics agent. If you use the Log Analytics agent to ingest data to Azure Monitor, [migrate to the new Azure Monitor agent](./azure-monitor-agent-migration.md) prior to that date.
37+
>
3438
The diagram below shows data collection for the [Azure Monitor agent](../agents/azure-monitor-agent-overview.md) running on a virtual machine. In this scenario, the DCR specifies events and performance data to collect from the agent machine, a transformation to filter and modify the data after its collected, and a Log Analytics workspace to send the transformed data. To implement this scenario, you create an association between the DCR and the agent. One agent can be associated with multiple DCRs, and one DCR can be associated with multiple agents.
3539

3640
:::image type="content" source="media/data-collection-transformations/transformation-azure-monitor-agent.png" lightbox="media/data-collection-transformations/transformation-azure-monitor-agent.png" alt-text="Diagram showing data collection for Azure Monitor agent." border="false":::

0 commit comments

Comments
 (0)