fixes

Author: bwren

.openpublishing.redirection.azure-monitor.json

@@ -6287,7 +6287,7 @@
         },
         {
             "source_path_from_root": "/articles/azure-monitor/terminology.md",
-            "redirect_url": "/azure/azure-monitor/alerts/overview",
+            "redirect_url": "/azure/azure-monitor/overview",
             "redirect_document_id": false
         },
         {

articles/azure-monitor/agents/solution-agenthealth.md

@@ -43,7 +43,7 @@ The following table describes the connected sources that this solution supports.
 ## Use the solution
 When you add the solution to your Log Analytics workspace, the **Agent Health** tile is added to your dashboard. This tile shows the total number of agents and the number of unresponsive agents in the last 24 hours.
 
-![Screenshot that shows the Agent Health tile on the dashboard.](./media/solution-agenthealth/agenthealth-solution-tile-homepage.png)
+:::image type="content" source="media/solution-agenthealth/agenthealth-solution-tile-homepage.png" alt-text="Screenshot that shows the Agent Health tile on the dashboard." lightbox="media/solution-agenthealth/agenthealth-solution-tile-homepage.png:::
 
 Select the **Agent Health** tile to open the **Agent Health** dashboard. The dashboard includes the columns in the following table. Each column lists the top 10 events by count that match that column's criteria for the specified time range. You can run a log search that provides the entire list. Select **See all** beneath each column or select the column heading.
 

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

@@ -27,7 +27,7 @@ The following resources describe different scenarios for creating DCRs. In some
 |:---|:---|:---|
 | Azure Monitor Agent | [Configure data collection for Azure Monitor Agent](../agents/data-collection-rule-azure-monitor-agent.md) | Use the Azure portal to create a DCR that specifies events and performance counters to collect from a machine with Azure Monitor Agent. Then apply that rule to one or more virtual machines. Azure Monitor Agent will be installed on any machines that don't currently have it.  |
 | | [Use Azure Policy to install Azure Monitor Agent and associate with a DCR](../agents/azure-monitor-agent-manage.md#use-azure-policy) | Use Azure Policy to install Azure Monitor Agent and associate one or more DCRs with any virtual machines or virtual machine scale sets as they're created in your subscription.
-| Custom logs | [Configure custom logs by using the Azure portal](../logs/tutorial-logs-ingestion-portal.md)<br>[Configure custom logs by using Azure Resource Manager templates and the REST API](../logs/tutorial-logs-ingestion-api.md)<br>[Configure custom logs by using Azure Monitorint Agent](../agents/data-collection-text-log.md) | Send custom data by using a REST API or Agent. The API call connects to a data collection endpoint and specifies a DCR to use. The agent uses the DCR to configure the collection of data on a machine. The DCR specifies the target table and potentially includes a transformation that filters and modifies the data before it's stored in a Log Analytics workspace.  |
+| Text logs | [Configure custom logs by using the Azure portal](../logs/tutorial-logs-ingestion-portal.md)<br>[Configure custom logs by using Azure Resource Manager templates and the REST API](../logs/tutorial-logs-ingestion-api.md)<br>[Configure text logs by using Azure Monitoring Agent](../agents/data-collection-text-log.md) | Send custom data by using a REST API or Agent. The API call connects to a data collection endpoint and specifies a DCR to use. The agent uses the DCR to configure the collection of data on a machine. The DCR specifies the target table and potentially includes a transformation that filters and modifies the data before it's stored in a Log Analytics workspace.  |
 | Azure Event Hubs | [Ingest events from Azure Event Hubs to Azure Monitor Logs](../logs/ingest-logs-event-hub.md)| Collect data from multiple sources to an event hub and ingest the data you need directly into tables in one or more Log Analytics workspaces. This is a highly scalable method of collecting data from a wide range of sources with minimum configuration.|
 | Workspace transformation | [Configure ingestion-time transformations by using the Azure portal](../logs/tutorial-workspace-transformations-portal.md)<br>[Configure ingestion-time transformations by using Azure Resource Manager templates and the REST API](../logs/tutorial-workspace-transformations-api.md) | Create a transformation for any supported table in a Log Analytics workspace. The transformation is defined in a DCR that's then associated with the workspace. It's applied to any data sent to that table from a legacy workload that doesn't use a DCR. |
 

articles/azure-monitor/essentials/resource-logs.md

@@ -90,7 +90,8 @@ Most Azure resources write data to the workspace in either **Azure diagnostics**
 
 All Azure services will eventually use the resource-specific mode. As part of this transition, some resources allow you to select a mode in the diagnostic setting. Specify resource-specific mode for any new diagnostic settings because this mode makes the data easier to manage. It also might help you avoid complex migrations later.
 
-   ![Screenshot that shows the Diagnostics settings mode selector.](media/resource-logs/diagnostic-settings-mode-selector.png)
+:::image type="content" source="media/resource-logs/diagnostic-settings-mode-selector.png" alt-text="Screenshot that shows the Diagnostics settings mode selector." lightbox="media/resource-logs/diagnostic-settings-mode-selector.png":::
+
 
 > [!NOTE]
 > For an example that sets the collection mode by using an Azure Resource Manager template, see [Resource Manager template samples for diagnostic settings in Azure Monitor](./resource-manager-diagnostic-settings.md#diagnostic-setting-for-recovery-services-vault).

articles/azure-monitor/insights/resource-manager-sql-insights.md

@@ -48,7 +48,7 @@ The following sample creates an alert rule that will cover the SQL resources wit
 The parameter file has values from one of the alert templates we provide in SQL Insights, you can modify it to alert on other data we collect for SQL.  The template does not specify an action group for the alert rule.
 
 
-#### Template file
+### Template file
 
 View the [template file on git hub](https://github.com/microsoft/Application-Insights-Workbooks/blob/master/Workbooks/Workloads/Alerts/log-metric-noag.armtemplate).
 

articles/azure-monitor/logs/resource-manager-workspace.md

@@ -747,11 +747,11 @@ resource windowsPerfProcessorPercentageDataSource 'Microsoft.OperationalInsights
 
 The following sample adds collection of [Linux performance counters](../agents/data-sources-performance-counters.md) to an existing workspace.
 
-### Notes
+#### Notes
 
 - Add a **datasources** element for each object and instance to collect. You can specify different set of counters for each object and instance combination, but you can only specify a single rate for all counters.
 
-### Template file
+#### Template file
 
 # [Bicep](#tab/bicep)
 
@@ -931,7 +931,7 @@ resource linuxPerformanceProcessorDataSource 'Microsoft.OperationalInsights/work
 
 The following sample adds collection of [text logs](../agents/data-sources-custom-logs.md) to an existing workspace.
 
-### Notes
+#### Notes
 
 - The configuration of delimiters and extractions can be complex. For help, you can define a text log using the Azure portal and the retrieve its configuration using [Get-AzOperationalInsightsDataSource](/powershell/module/az.operationalinsights/get-azoperationalinsightsdatasource) with **-Kind** set to **CustomLog**.
 

articles/azure-monitor/toc.yml

@@ -861,7 +861,7 @@ items:
         items:  
           - name: Log Analytics VM Extension
             displayName: troubleshoot, troubleshooting
-            href: visualize/vmext-troubleshoot.md
+            href: agents/vmext-troubleshoot.md
           - name: Log Analytics Windows agent
             displayName: troubleshoot, troubleshooting
             href: agents/agent-windows-troubleshoot.md
@@ -1237,8 +1237,6 @@ items:
           href: logs/workspace-expression.md
         - name: resource expression
           href: logs/resource-expression.md
-        - name: Unify application data resources
-          href: logs/unify-app-resource-data.md
         - name: Query Azure Data Explorer from Azure Monitor
           href: logs/azure-monitor-data-explorer-proxy.md
       - name: API
@@ -1513,7 +1511,7 @@ items:
   - name: Azure Resource Graph queries
     href: ./resource-graph-samples.md
   - name: Azure CLI metric alerts
-    href: azure-cli-metrics-alert-sample.md
+    href: alerts/azure-cli-metrics-alert-sample.md
 - name: Reference
   items:
   - name: Service limits