fixes

Author: bwren

.openpublishing.redirection.azure-monitor.json

@@ -6760,7 +6760,7 @@
             "redirect_document_id": false
         },
         {
-            "source_path_from_root": "/articles/azure-monitor-agents/data-collection-rule-azure-monitor-agent.md",
+            "source_path_from_root": "/articles/azure-monitor/agents/data-collection-rule-azure-monitor-agent.md",
             "redirect_url": "/azure/azure-monitor/agents/azure-monitor-agent-data-collection",
             "redirect_document_id": false
         }

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

@@ -739,4 +739,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 wusing Azure Monitor Agent](./azure-monitor-agent-data-collection.md.md).
+- For more information on creating a data collection rule, see [Collect data from virtual machines wusing Azure Monitor Agent](./azure-monitor-agent-data-collection.md).

articles/azure-monitor/agents/azure-monitor-agent-troubleshoot-linux-vm-rsyslog.md

@@ -22,7 +22,7 @@ Overview of Azure Monitor Agent for Linux Syslog collection and supported RFC st
   > Before Azure Monitor Agent version 1.28, it used a Unix domain socket instead of TCP port to receive events from rsyslog. `omfwd` output module in `rsyslog` offers spooling and retry mechanisms for improved reliability.
 - The Syslog daemon uses queues when Azure Monitor Agent ingestion is delayed or when Azure Monitor Agent isn't reachable.
 - Azure Monitor Agent ingests Syslog events via the previously mentioned socket and filters them based on facility or severity combination from data collection rule (DCR) configuration in `/etc/opt/microsoft/azuremonitoragent/config-cache/configchunks/`. Any `facility` or `severity` not present in the DCR is dropped.
-- Azure Monitor Agent attempts to parse events in accordance with **RFC3164** and **RFC5424**. It also knows how to parse the message formats listed in [this website](./azure-monitor-agent-overview.md#data-sources-and-destinations).
+- Azure Monitor Agent attempts to parse events in accordance with **RFC3164** and **RFC5424**. It also knows how to parse the message formats listed in [this website](./azure-monitor-agent-overview.md#supported-services-and-features).
 - Azure Monitor Agent identifies the destination endpoint for Syslog events from the DCR configuration and attempts to upload the events.
   > [!NOTE]
   > Azure Monitor Agent uses local persistency by default. All events received from `rsyslog` or `syslog-ng` are queued in `/var/opt/microsoft/azuremonitoragent/events` if they fail to be uploaded.

articles/azure-monitor/agents/data-collection-windows-event.md renamed to articles/azure-monitor/agents/data-collection-windows-events.md

@@ -201,7 +201,7 @@ After the load balancer is created, a backend pool needs to be created, which di
 ## Configure the Azure Monitor agent to communicate using Log Analytics gateway  
 
 To configure the Azure Monitor agent (installed on the gateway server) to use the gateway to upload data for Windows or Linux:
-1. Follow the instructions to [configure proxy settings on the agent](./azure-monitor-agent-overview.md#proxy-configuration) and provide the IP address and port number corresponding to the gateway server. If you have deployed multiple gateway servers behind a load balancer, the agent proxy configuration is the virtual IP address of the load balancer instead.  
+1. Follow the instructions to [configure proxy settings on the agent](./azure-monitor-agent-network-configuration.md#proxy-configuration) and provide the IP address and port number corresponding to the gateway server. If you have deployed multiple gateway servers behind a load balancer, the agent proxy configuration is the virtual IP address of the load balancer instead.  
 2. Add the **configuration endpoint URL** to fetch data collection rules to the allowlist for the gateway  
    `Add-OMSGatewayAllowedHost -Host global.handler.control.monitor.azure.com`  
    `Add-OMSGatewayAllowedHost -Host <gateway-server-region-name>.handler.control.monitor.azure.com`  

articles/azure-monitor/agents/gateway.md

@@ -730,7 +730,7 @@ items:
           items:
           - name: Windows events
             displayName: data collection rule,Azure Monitor agent
-            href: agents/data-collection-windows-event.md
+            href: agents/data-collection-windows-eventsss.md
           - name: Syslog events
             href: agents/data-collection-syslog.md        
           - name: IIS logs

articles/azure-monitor/toc.yml

@@ -93,7 +93,7 @@ The operating system and applications in virtual machines often write to the Win
 
 For guidance on how to create a DCR to collect Windows and Syslog events, see [Collect data with Azure Monitor Agent](../agents/azure-monitor-agent-data-collection.md). You can quickly create a DCR by using the most common Windows event logs and Syslog facilities filtering by event level.
 
-For more granular filtering by criteria such as event ID, you can create a custom filter by using [XPath queries](../agents/data-collection-windows-event.md#filter-events-using-xpath-queries). You can further filter the collected data by [editing the DCR](../essentials/data-collection-rule-edit.md) to add a [transformation](../essentials/data-collection-transformations.md).
+For more granular filtering by criteria such as event ID, you can create a custom filter by using [XPath queries](../agents/data-collection-windows-events.md#filter-events-using-xpath-queries). You can further filter the collected data by [editing the DCR](../essentials/data-collection-rule-edit.md) to add a [transformation](../essentials/data-collection-transformations.md).
 
 Use the following guidance as a recommended starting point for event collection. Modify the DCR settings to filter unneeded events and add other events depending on your requirements.