two articles missing

Author: bwren

.openpublishing.redirection.json

@@ -30666,6 +30666,11 @@
             "redirect_url":  "/azure/azure-monitor/insights/container-overview",
             "redirect_document_id":  "false"
         },
+        {
+            "source_path":  "articles/monitoring/monitoring-container-agent-upgrade.md",
+            "redirect_url":  "/azure/azure-monitor/insights/container-agent-upgrade",
+            "redirect_document_id":  "false"
+        },
         {
             "source_path":  "articles/monitoring/monitoring-vminsights-faq.md",
             "redirect_url":  "/azure/azure-monitor/insights/vminsights-faq",
@@ -30705,6 +30710,11 @@
             "source_path":  "articles/monitoring/monitoring-vminsights-performance.md",
             "redirect_url":  "/azure/azure-monitor/insights/vminsights-performance",
             "redirect_document_id":  "false"
+        },
+        {
+            "source_path":  "articles/monitoring/monitoring-vminsights-optout.md",
+            "redirect_url":  "/azure/azure-monitor/insights/vminsights-optout",
+            "redirect_document_id":  "false"
         }
     ]
 }

articles/monitoring/monitoring-container-insights-agent-upgrade.md renamed to articles/azure-monitor/insights/container-insights-agent-upgrade.md

@@ -23,15 +23,15 @@ Azure Monitor for containers uses a containerized version of the Log Analytics a
 This article describes the process for upgrading the agent.
 
 ## Upgrading agent on monitored Kubernetes cluster
-The process to upgrade the agent consists of two straight forward steps. The first step is to disable monitoring with Azure Monitor for containers using Azure CLI.  Follow the steps described in the [Disable monitoring](../azure-monitor/insights/container-insights-optout.md?toc=%2fazure%2fmonitoring%2ftoc.json#azure-cli) article. Using Azure CLI allows us to remove the agent from the nodes in the cluster without impacting the solution and the corresponding data that is stored in the workspace. 
+The process to upgrade the agent consists of two straight forward steps. The first step is to disable monitoring with Azure Monitor for containers using Azure CLI.  Follow the steps described in the [Disable monitoring](container-insights-optout.md?toc=%2fazure%2fmonitoring%2ftoc.json#azure-cli) article. Using Azure CLI allows us to remove the agent from the nodes in the cluster without impacting the solution and the corresponding data that is stored in the workspace. 
 
 >[!NOTE]
 >While you are performing this maintenance activity, the nodes in the cluster are not forwarding collected data, and performance views will not show data between the time you remove the agent and install the new version. 
 >
 
-To install the new version of the agent, follow the steps described in the [Onboard monitoring](../azure-monitor/insights/container-insights-onboard.md?toc=%2fazure%2fmonitoring%2ftoc.json#enable-monitoring-using-azure-cli) article using Azure CLI, to complete this process.  
+To install the new version of the agent, follow the steps described in the [Onboard monitoring](container-insights-onboard.md?toc=%2fazure%2fmonitoring%2ftoc.json#enable-monitoring-using-azure-cli) article using Azure CLI, to complete this process.  
 
 After you've re-enabled monitoring, it might take about 15 minutes before you can view  updated health metrics for the cluster. 
 
 ## Next steps
-If you experience issues while upgrading the agent, review the [troubleshooting guide](../azure-monitor/insights/container-insights-troubleshoot.md) for support.
+If you experience issues while upgrading the agent, review the [troubleshooting guide](container-insights-troubleshoot.md) for support.

articles/azure-monitor/insights/container-insights-onboard.md

@@ -28,7 +28,7 @@ Before you start, make sure that you have the following:
 - A Log Analytics workspace. You can create it when you enable monitoring of your new AKS cluster or let the onboarding experience create a default workspace in the default resource group of the AKS cluster subscription. If you chose to create it yourself, you can create it through [Azure Resource Manager](../../log-analytics/log-analytics-template-workspace-configuration.md), through [PowerShell](https://docs.microsoft.com/azure/log-analytics/scripts/log-analytics-powershell-sample-create-workspace?toc=%2fpowershell%2fmodule%2ftoc.json), or in the [Azure portal](../../log-analytics/log-analytics-quick-create-workspace.md).
 - The Log Analytics contributor role, to enable container monitoring. For more information about how to control access to a Log Analytics workspace, see [Manage workspaces](../../log-analytics/log-analytics-manage-access.md).
 
-[!INCLUDE [log-analytics-agent-note](../../../../includes/log-analytics-agent-note.md)]
+[!INCLUDE [log-analytics-agent-note](../../../includes/log-analytics-agent-note.md)]
 
 ## Components 
 

articles/azure-monitor/insights/vminsights-onboard.md

@@ -195,7 +195,8 @@ In this section instructions on how to perform the at scale deployment of Azure
 
 Summarized are the steps you need to perform to pre-configure your Log Analytics workspace before you can proceed with onboarding your virtual machines.
 
-1. Create a new workspace if one does not already exist that can be used to support Azure Monitor for VMs. Review [Manage workspaces](../../log-analytics/log-analytics-manage-access.md?toc=/azure/azure-monitor/toc.json) before creating a new workspace to understand the cost, management, and compliance considerations before proceeding.       2. Enable performance counters in the workspace for collection on Linux and Windows VMs.
+1. Create a new workspace if one does not already exist that can be used to support Azure Monitor for VMs. Review [Manage workspaces](../../log-analytics/log-analytics-manage-access.md?toc=/azure/azure-monitor/toc.json) before creating a new workspace to understand the cost, management, and compliance considerations before proceeding.       
+2. Enable performance counters in the workspace for collection on Linux and Windows VMs.
 3. Install and enable the **ServiceMap** and **InfrastructureInsights** solution in your workspace.  
 
 ### Setup Log Analytics workspace
@@ -533,7 +534,7 @@ The Azure Monitor for VMs Map Dependency agent does not transmit any data itself
 
 Review the requirements and deployment methods for the [Log Analytics Linux and Windows agent](../../log-analytics/log-analytics-agent-overview.md).  
 
-[!INCLUDE [log-analytics-agent-note](../../../../includes/log-analytics-agent-note.md)]
+[!INCLUDE [log-analytics-agent-note](../../../includes/log-analytics-agent-note.md)]
 
 Summarized steps:
 
@@ -726,7 +727,7 @@ Microsoft automatically collects usage and performance data through your use of
 
 For more information about data collection and usage, see the [Microsoft Online Services Privacy Statement](https://go.microsoft.com/fwlink/?LinkId=512132).
 
-[!INCLUDE [GDPR-related guidance](../../../../includes/gdpr-dsr-and-stp-note.md)]
+[!INCLUDE [GDPR-related guidance](../../../includes/gdpr-dsr-and-stp-note.md)]
 ## Next steps
 
 With monitoring enabled for your virtual machine, this information is available for analysis with Azure Monitor for VMs.  To learn how to use the Health feature, see [View Azure Monitor for VMs Health](vminsights-health.md), or to view discovered application dependencies, see [View Azure Monitor for VMs Map](vminsights-maps.md).  

articles/monitoring/monitoring-vminsights-optout.md renamed to articles/azure-monitor/insights/vminsights-optout.md

@@ -53,7 +53,7 @@ The following steps describe how to completely remove Azure Monitor for VMs if y
 5. In the list of solutions, select **InfrastructureInsights(workspace name)**, and then on the **Overview** page for the solution, click **Delete**.  When prompted to confirm, click **Yes**.  
 6. From the list of solutions, select **ServiceMap(workspace name)**, and then on the **Overview** page for the solution, click **Delete**.  When prompted to confirm, click **Yes**.  
 
-If before onboarding Azure Monitor for VMs, you were not [collecting the performance counters enabled](../azure-monitor/insights/vminsights-onboard.md?toc=/azure/azure-monitor/toc.json#performance-counters-enabled) for the Windows or Linux-based VMs in your workspace, you need to disable those rules by following the steps described [here](../log-analytics/log-analytics-data-sources-performance-counters.md?toc=/azure/azure-monitor/toc.json#configuring-performance-counters) for Windows and for Linux.
+If before onboarding Azure Monitor for VMs, you were not [collecting the performance counters enabled](vminsights-onboard.md?toc=/azure/azure-monitor/toc.json#performance-counters-enabled) for the Windows or Linux-based VMs in your workspace, you need to disable those rules by following the steps described [here](../../log-analytics/log-analytics-data-sources-performance-counters.md?toc=/azure/azure-monitor/toc.json#configuring-performance-counters) for Windows and for Linux.
 
 ## Disable monitoring for an Azure VM and retain workspace