data collection article rename

Author: bwren

.openpublishing.redirection.azure-monitor.json

@@ -7740,6 +7740,11 @@
    "redirect_url": "/azure/azure-monitor/reference",
    "redirect_document_id": false
   },
+  {
+   "source_path": "articles/azure-monitor/vm/data-collection.md",
+   "redirect_url": "/azure/azure-monitor/vm/data-collection",
+   "redirect_document_id": false
+  },
   {
    "source_path": "articles/azure-monitor/agents/data-collection-windows-events.md",
    "redirect_url": "/azure/azure-monitor/vm/data-collection-windows-events",

articles/azure-monitor/agents/azure-monitor-agent-extension-versions.md

@@ -75,4 +75,4 @@ We strongly recommend that you always update to the latest version, or opt in to
 ## Next steps
 
 - [Install and manage the extension](./azure-monitor-agent-manage.md).
-- [Create a data collection rule](./azure-monitor-agent-data-collection.md) to collect data from the agent and send it to Azure Monitor.
+- [Create a data collection rule](../vm/data-collection.md) to collect data from the agent and send it to Azure Monitor.

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

@@ -32,7 +32,7 @@ For any machine that isn't in Azure, the [Azure Arc agent](/azure/azure-arc/serv
 | Installation method | Description |
 |:---|:---|
 | Virtual machine (VM) extension | Use any of the methods described in this article to install the agent via the Azure extension framework. This method doesn't create a DCR, so you must create at least one DCR and associate it with the agent before data collection begins. |
-| [Create a DCR](./azure-monitor-agent-data-collection.md) | When you create a DCR in the Azure portal, the Azure Monitor Agent is installed on any machine that's added as a resource for the DCR. The agent immediately begins to collect data as defined in the DCR.
+| [Create a DCR](../vm/data-collection.md) | When you create a DCR in the Azure portal, the Azure Monitor Agent is installed on any machine that's added as a resource for the DCR. The agent immediately begins to collect data as defined in the DCR.
 | [VM insights](../vm/vminsights-enable-overview.md) | When you enable VM insights on a machine, the Azure Monitor Agent is installed and a DCR is created to collect a predefined set of data. You shouldn't modify this DCR, but you can create more DCRs to collect more data. |
 | [Container insights](../containers/kubernetes-monitoring-enable.md#container-insights) | When you enable Container insights on a Kubernetes cluster, a containerized version of the Azure Monitor Agent is installed in the cluster and a DCR is created to immediately begin collecting data. You can modify the DCR by using the guidance in [Configure data collection and cost optimization in Container insights by using DCRs](../containers/container-insights-data-collection-dcr.md).
 | [Client installer](./azure-monitor-agent-windows-client.md) | Install the agent by using a Windows MSI installer for Windows 11 and Windows 10 clients. |
@@ -48,7 +48,7 @@ For any machine that isn't in Azure, the [Azure Arc agent](/azure/azure-arc/serv
 
 ### [Azure portal](#tab/azure-portal)
 
-To install the agent and create a DCR to collect data by using the Azure portal, use the guidance in [Collect data by using the Azure Monitor Agent](./azure-monitor-agent-data-collection.md).
+To install the agent and create a DCR to collect data by using the Azure portal, use the guidance in [Collect data by using the Azure Monitor Agent](../vm/data-collection.md).
 
 ### [Azure PowerShell](#tab/azure-powershell)
 
@@ -530,4 +530,4 @@ Currently not supported.
 
 ## Related content
 
-[Create a data collection rule](./azure-monitor-agent-data-collection.md) to collect data from the agent and send it to Azure Monitor.
+[Create a data collection rule](../vm/data-collection.md) to collect data from the agent and send it to Azure Monitor.

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

@@ -103,9 +103,9 @@ The following tables identify the different environments and features that are c
 
 ## Supported data sources
 
-For a list of data sources the Azure Monitor Agent can collect and to learn how to configure them, see [Collect data with the Azure Monitor Agent](./azure-monitor-agent-data-collection.md).
+For a list of data sources the Azure Monitor Agent can collect and to learn how to configure them, see [Collect data with the Azure Monitor Agent](../vm/data-collection.md).
 
 ## Related content
 
 - [Install the Azure Monitor Agent](azure-monitor-agent-manage.md) on Windows and Linux virtual machines.
-- [Create a data collection rule](./azure-monitor-agent-data-collection.md) to collect data from the agent and send it to Azure Monitor.
+- [Create a data collection rule](../vm/data-collection.md) to collect data from the agent and send it to Azure Monitor.

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

@@ -1,83 +1,84 @@
----
-title: Performance in Forwarding to Azure Monitor Agent
-description: Learn about performance benchmark data for the Azure Monitor Agent running in a gateway event forwarding scenario.
-ms.topic: conceptual
-author: guywi-ms
-ms.author: guywild
-ms.date: 11/14/2024
-ms.reviewer: jeffwo
- 
-# Customer intent: As a deployment engineer, I can scope the resources required to scale my gateway data colletors the use the Azure Monitor Agent. 
-
----
-# Azure Monitor Agent performance benchmark
-
-The Azure Monitor Agent can handle many thousands of events per second (EPS) in the gateway event forwarding scenario. The exact throughput rate depends on various factors like the size of each event, the specific data type, and physical hardware resources.
-
-This article describes the Microsoft internal benchmark that's used for testing the agent throughput of 10,000 (10K) syslog events in the gateway forwarder scenario. The benchmark results should provide a guide to size the resources that you need in your environment.
-
-> [!NOTE]
-> The results in this article are only informational related to the performance of Azure Monitor Agent in a gateway forwarding scenario. The results and the information in the article don't constitute any service agreement on the part of Microsoft.
-
-## Best practices for agent as a forwarder
-
-- The Linux Azure Monitor Agent should target 10K EPS. A 20K EPS warning might occur, but it doesn't mean that data is lost. The Azure Monitor Agent doesn't guarantee a lossless connection. Loss is more likely when EPS is over 10K.
-- The forwarder should be on a dedicated system to eliminate potential interference from other workloads.
-- The forwarder system should be monitored for CPU, memory, and disk utilization to prevent overloads from causing data loss.
-- The load balancer and redundant forwarder systems should be used to improve reliability and scalability. For other considerations for forwarders, see the Log Analytics gateway documentation.
-
-## Agent performance
-
-The benchmark is run in a controlled environment to get repeatable, accurate, and statistically significant results. The resources consumed by the agent are measured under a load of 10,000 simulated syslog events per second. The simulated load is run on the same physical hardware that the agent being tested is on. Test trials run for seven days. For each trial, performance metrics are sampled every second to collect CPU, memory, and network maximum and average usage. This approach provides the right information to help you estimate the resources needed for your environment.
-
-> [!NOTE]
-> Performance testing results don't measure the end-to-end throughput ingested by a Log Analytics workspace (or other telemetry sinks). End-to-end variability might occur due to network and back-end pipeline performance.
-
-The benchmarks are run on an Azure virtual machine Standard_F8s_v2 system using Azure Monitor Agent Linux version 1.25.2 and 10 GB of disk space for the event cache.
-
-- vCPUs: Eight with Hyper-Threading (800% CPU is possible)
-- Memory: 16 GiB
-- Temp storage: 64 GiB
-- Max disk IOPS: 6,400
-- Network: 12,500 Mbps max on all four physical NICs
-
-## Results
-
-| Perf Metric | Ave (Max) Med |
-|:---|:---:|
-| **CPU %**           | 51 (262)     |
-| **Memory RSS MB**      | 276 (1,017)  |
-| **Network KBps**    | 338 (18,033) |
-
-## FAQs
-
-Get answers to common questions.
-
-### How much data is sent per agent?
-
-The amount of data sent per agent depends on:
-
-- The solutions you enabled
-- The number of logs and performance counters that are collected
-- The volume of data in the logs
-
-For more information, see [Analyze usage in a Log Analytics workspace](../logs/analyze-usage.md).
-
-For computers that are able to run the WireData Agent, use the following query to see how much data is sent:
-
-```kusto
-WireData
-| where ProcessName == "C:\\Program Files\\Microsoft Monitoring Agent\\Agent\\MonitoringHost.exe"
-| where Direction == "Outbound"
-| summarize sum(TotalBytes) by Computer 
-```
-
-### How much network bandwidth is used by the Microsoft Monitoring Agent when it sends data to Azure Monitor?
-
-Bandwidth is a function of the amount of data that's sent. Data is compressed as it's sent over the network.
-
-## Related content
-
-- [Use the Log Analytics gateway in Azure Monitor](gateway.md) to connect computers without internet access.
-- [Install the Azure Monitor Agent](azure-monitor-agent-manage.md) on Windows and Linux virtual machines.
-- [Create a data collection rule](azure-monitor-agent-data-collection.md) to collect data from the agent and send it to Azure Monitor.
+---
+title: Performance in Forwarding to Azure Monitor Agent
+description: Learn about performance benchmark data for the Azure Monitor Agent running in a gateway event forwarding scenario.
+ms.topic: conceptual
+author: guywi-ms
+ms.author: guywild
+ms.date: 11/14/2024
+ms.reviewer: jeffwo
+ 
+# Customer intent: As a deployment engineer, I can scope the resources required to scale my gateway data colletors the use the Azure Monitor Agent. 
+
+---
+# Azure Monitor Agent performance benchmark
+
+The Azure Monitor Agent can handle many thousands of events per second (EPS) in the gateway event forwarding scenario. The exact throughput rate depends on various factors like the size of each event, the specific data type, and physical hardware resources.
+
+This article describes the Microsoft internal benchmark that's used for testing the agent throughput of 10,000 (10K) syslog events in the gateway forwarder scenario. The benchmark results should provide a guide to size the resources that you need in your environment.
+
+
+> [!NOTE]
+> The results in this article are only informational related to the performance of Azure Monitor Agent in a gateway forwarding scenario. The results and the information in the article don't constitute any service agreement on the part of Microsoft.
+
+## Best practices for agent as a forwarder
+
+- The Linux Azure Monitor Agent should target 10K EPS. A 20K EPS warning might occur, but it doesn't mean that data is lost. The Azure Monitor Agent doesn't guarantee a lossless connection. Loss is more likely when EPS is over 10K.
+- The forwarder should be on a dedicated system to eliminate potential interference from other workloads.
+- The forwarder system should be monitored for CPU, memory, and disk utilization to prevent overloads from causing data loss.
+- The load balancer and redundant forwarder systems should be used to improve reliability and scalability. For other considerations for forwarders, see the Log Analytics gateway documentation.
+
+## Agent performance
+
+The benchmark is run in a controlled environment to get repeatable, accurate, and statistically significant results. The resources consumed by the agent are measured under a load of 10,000 simulated syslog events per second. The simulated load is run on the same physical hardware that the agent being tested is on. Test trials run for seven days. For each trial, performance metrics are sampled every second to collect CPU, memory, and network maximum and average usage. This approach provides the right information to help you estimate the resources needed for your environment.
+
+> [!NOTE]
+> Performance testing results don't measure the end-to-end throughput ingested by a Log Analytics workspace (or other telemetry sinks). End-to-end variability might occur due to network and back-end pipeline performance.
+
+The benchmarks are run on an Azure virtual machine Standard_F8s_v2 system using Azure Monitor Agent Linux version 1.25.2 and 10 GB of disk space for the event cache.
+
+- vCPUs: Eight with Hyper-Threading (800% CPU is possible)
+- Memory: 16 GiB
+- Temp storage: 64 GiB
+- Max disk IOPS: 6,400
+- Network: 12,500 Mbps max on all four physical NICs
+
+## Results
+
+| Perf Metric | Ave (Max) Med |
+|:---|:---:|
+| **CPU %**           | 51 (262)     |
+| **Memory RSS MB**      | 276 (1,017)  |
+| **Network KBps**    | 338 (18,033) |
+
+## FAQs
+
+Get answers to common questions.
+
+### How much data is sent per agent?
+
+The amount of data sent per agent depends on:
+
+- The solutions you enabled
+- The number of logs and performance counters that are collected
+- The volume of data in the logs
+
+For more information, see [Analyze usage in a Log Analytics workspace](../logs/analyze-usage.md).
+
+For computers that are able to run the WireData Agent, use the following query to see how much data is sent:
+
+```kusto
+WireData
+| where ProcessName == "C:\\Program Files\\Microsoft Monitoring Agent\\Agent\\MonitoringHost.exe"
+| where Direction == "Outbound"
+| summarize sum(TotalBytes) by Computer 
+```
+
+### How much network bandwidth is used by the Microsoft Monitoring Agent when it sends data to Azure Monitor?
+
+Bandwidth is a function of the amount of data that's sent. Data is compressed as it's sent over the network.
+
+## Related content
+
+- [Use the Log Analytics gateway in Azure Monitor](gateway.md) to connect computers without internet access.
+- [Install the Azure Monitor Agent../vm/data-collection.mdndows and Linux virtual machines.
+- [Create a data collection rule](azure-monitor-agent-data-collection.md) to collect data from the agent and send it to Azure Monitor.

articles/azure-monitor/agents/azure-monitor-agent-private-link.md

@@ -35,7 +35,7 @@ By default, Azure Monitor Agent connects to a public endpoint to connect to your
 
 ## Associate DCEs to target resources
 
-Associate the DCEs to the target resources by editing the DCR in the Azure portal. On the **Resources** tab, select **Enable Data Collection Endpoints**. Select a DCE for each virtual machine. For more information, see [Configure data collection for the Azure Monitor Agent](../agents/azure-monitor-agent-data-collection.md).
+Associate the DCEs to the target resources by editing the DCR in the Azure portal. On the **Resources** tab, select **Enable Data Collection Endpoints**. Select a DCE for each virtual machine. For more information, see [Configure data collection for the Azure Monitor Agent](../vm/data-collection.md).
 
 :::image type="content" source="media/azure-monitor-agent-dce/data-collection-rule-virtual-machines-with-endpoint.png" lightbox="media/azure-monitor-agent-dce/data-collection-rule-virtual-machines-with-endpoint.png" alt-text="Screenshot that shows configuring data collection endpoints for an agent.":::
 

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

@@ -79,4 +79,4 @@ The Azure Monitor Agent does not work on Linux virtual machines when the systemw
 
 ## Related content
 
-- [Create a data collection rule](azure-monitor-agent-data-collection.md) to collect data from the agent and send it to Azure Monitor.
+- [Create a data collection rule](../vm/data-collection.md) to collect data from the agent and send it to Azure Monitor.

articles/azure-monitor/agents/azure-monitor-agent-send-data-to-event-hubs-and-storage.md

@@ -750,4 +750,4 @@ WAD and LAD will only be getting security/patches going forward. Most engineerin
 
 ## See also
 
-- For more information on creating a data collection rule, see [Collect data from virtual machines using Azure Monitor Agent](./azure-monitor-agent-data-collection.md).
+- For more information on creating a data collection rule, see [Collect data from virtual machines using Azure Monitor Agent](../vm/data-collection.md).

articles/azure-monitor/agents/azure-monitor-agent-troubleshoot-windows-arc.md

@@ -53,7 +53,7 @@ Follow the steps below to troubleshoot the latest version of the Azure Monitor a
     1. Check if you see the latest DCR downloaded at this location `C:\Resources\Directory\AMADataStore\mcs\configchunks` 
 
 ## Issues collecting Performance counters
-1. Check that your DCR JSON contains a section for 'performanceCounters'. If not, fix your DCR. See [how to create DCR](./azure-monitor-agent-data-collection.md) or [sample DCR](./data-collection-rule-sample-agent.md).
+1. Check that your DCR JSON contains a section for 'performanceCounters'. If not, fix your DCR. See [how to create DCR](../vm/data-collection.md) or [sample DCR](./data-collection-rule-sample-agent.md).
 2. Check that the file `C:\Resources\Directory\AMADataStore\mcs\mcsconfig.lkg.xml` exists.
 3. Open the file and check if it contains `CounterSet` nodes as shown in the example below:
     ```xml
@@ -92,7 +92,7 @@ Follow the steps below to troubleshoot the latest version of the Azure Monitor a
     2. Open it and look for any Level 2 errors and try to fix them.
 
 ## Issues collecting Windows event logs
-1. Check that your DCR JSON contains a section for 'windowsEventLogs'. If not, fix your DCR. See [how to create DCR](./azure-monitor-agent-data-collection.md) or [sample DCR](./data-collection-rule-sample-agent.md).
+1. Check that your DCR JSON contains a section for 'windowsEventLogs'. If not, fix your DCR. See [how to create DCR](../vm/data-collection.md) or [sample DCR](./data-collection-rule-sample-agent.md).
 2. Check that the file `C:\Resources\Directory\AMADataStore\mcs\mcsconfig.lkg.xml` exists.
 3. Open the file and check if it contains `Subscription` nodes as shown in the example below:
     ```xml

articles/azure-monitor/agents/azure-monitor-agent-troubleshoot-windows-vm.md

@@ -47,7 +47,7 @@ Follow the steps below to troubleshoot the latest version of the Azure Monitor a
     1. Check if you see the latest DCR downloaded at this location `C:\WindowsAzure\Resources\AMADataStore.<virtual-machine-name>\mcs\configchunks`  
     
 ## Issues collecting Performance counters
-1. Check that your DCR JSON contains a section for 'performanceCounters'. If not, fix your DCR. See [how to create DCR](./azure-monitor-agent-data-collection.md) or [sample DCR](./data-collection-rule-sample-agent.md).
+1. Check that your DCR JSON contains a section for 'performanceCounters'. If not, fix your DCR. See [how to create DCR](../vm/data-collection.md) or [sample DCR](./data-collection-rule-sample-agent.md).
 2. Check that the file `C:\WindowsAzure\Resources\AMADataStore.<virtual-machine-name>\mcs\mcsconfig.lkg.xml` exists.
 3. Open the file and check if it contains `CounterSet` nodes as shown in the example below:
     ```xml
@@ -84,7 +84,7 @@ Follow the steps below to troubleshoot the latest version of the Azure Monitor a
     2. Open it and look for any Level 2 errors and try to fix them.
 
 ## Issues collecting Windows event logs
-1. Check that your DCR JSON contains a section for 'windowsEventLogs'. If not, fix your DCR. See [how to create DCR](./azure-monitor-agent-data-collection.md) or [sample DCR](./data-collection-rule-sample-agent.md).
+1. Check that your DCR JSON contains a section for 'windowsEventLogs'. If not, fix your DCR. See [how to create DCR](../vm/data-collection.md) or [sample DCR](./data-collection-rule-sample-agent.md).
 2. Check that the file `C:\WindowsAzure\Resources\AMADataStore.<virtual-machine-name>\mcs\mcsconfig.lkg.xml` exists.
 3. Open the file and check if it contains `Subscription` nodes as shown in the example below:
     ```xml

articles/azure-monitor/agents/azure-monitor-agent-windows-client.md

@@ -63,7 +63,7 @@ Here's a comparison between using the client installer and using the virtual mac
     (Example: `12345a01-b1cd-1234-e1f2-1234567g8h99.ods.opinsights.azure.com`)
 
     If you use private links on the agent, you must also add the [data collection endpoints](../essentials/data-collection-endpoint-overview.md#components-of-a-dce).
-- A DCR that you want to associate with the devices. If it doesn't exist already, [create a data collection rule](./azure-monitor-agent-data-collection.md). *Don't associate the rule to any resources yet*.
+- A DCR that you want to associate with the devices. If it doesn't exist already, [create a data collection rule](../vm/data-collection.md). *Don't associate the rule to any resources yet*.
 - Before you use any PowerShell cmdlet, ensure that the cmdlet-related PowerShell module is installed and imported.
 
 ## Limitations