Merge pull request #224101 from AbbyMSFT/toc-update

BCS2022 · web-flow · commit a8494c4447f1 · 2023-01-17T12:38:19.000-08:00
Update TOC move tutorials to specific sections
diff --git a/.openpublishing.redirection.azure-monitor.json b/.openpublishing.redirection.azure-monitor.json
@@ -1,10 +1,20 @@
 {
     "redirections": [
         {
+            "source_path_from_root": "/articles/azure-monitor/best-practices.md",
+            "redirect_url": "/azure/azure-monitor/getting-started",
+            "redirect_document_id": false
+         },
+         {
             "source_path_from_root": "/articles/azure-monitor/change/change-analysis-query.md",
             "redirect_url": "/azure/azure-monitor/change/change-analysis-visualizations",
             "redirect_document_id": false
-        },
+         },
+         {
+            "source_path_from_root": "/articles/azure-monitor/change/tutorial-outages.md",
+            "redirect_url": "/azure/azure-monitor/change/change-analysis-track-outages",
+            "redirect_document_id": false
+         }, 
         {
             "source_path_from_root": "/articles/azure-monitor/change/change-analysis-custom-filters.md",
             "redirect_url": "/azure/azure-monitor/change/change-analysis-visualizations",
diff --git a/articles/azure-monitor/best-practices.md b/articles/azure-monitor/best-practices.md
diff --git a/articles/azure-monitor/change/change-analysis-track-outages.md b/articles/azure-monitor/change/change-analysis-track-outages.md
@@ -1,7 +1,7 @@
 ---
-title: Tutorial - Track a web app outage using Change Analysis
-description: Tutorial on how to identify the root cause of a web app outage using Azure Monitor Change Analysis.
-ms.topic: tutorial
+title: Track a web app outage using Change Analysis
+description: Describes how to identify the root cause of a web app outage using Azure Monitor Change Analysis.
+ms.topic: how-to
 ms.author: hannahhunter
 author: hhunter-ms
 ms.contributor: cawa
@@ -11,11 +11,11 @@ ms.subservice: change-analysis
 ms.custom: devx-track-azurepowershell
 ---
 
-# Tutorial: Track a web app outage using Change Analysis
+# Track a web app outage using Change Analysis
 
 When issues happen, one of the first things to check is what changed in application, configuration and resources to triage and root cause issues. Change Analysis provides a centralized view of the changes in your subscriptions for up to the past 14 days to provide the history of changes for troubleshooting issues.  
 
-In this tutorial, you will: 
+To track an outage, we will: 
 
 > [!div class="checklist"]
 > - Clone, create, and deploy a [sample web application](https://github.com/Azure-Samples/changeanalysis-webapp-storage-sample) with a storage account.
diff --git a/articles/azure-monitor/getting-started.md b/articles/azure-monitor/getting-started.md
@@ -0,0 +1,40 @@
+---
+title: Getting started with Azure Monitor
+description: Guidance and recommendations for deploying Azure Monitor.
+ms.topic: conceptual
+author: bwren
+ms.author: bwren
+ms.date: 10/18/2021
+ms.reviewer: bwren
+---
+
+# Getting started with Azure Monitor
+This article helps guide you through getting started with Azure Monitor including recommendations for preparing your environment and configuring Azure Monitor. It presents an overview of the basic steps you need for a complete Azure Monitor implementation. It will help you understand how you can take advantage of Azure Monitor's features to maximize the observability of your cloud and hybrid applications and resources.
+
+This article focuses on configuration requirements and deployment options, as opposed to actual configuration details. Links are provided for detailed information for the required configurations.
+
+Azure Monitor is available the moment you create an Azure subscription. The Activity log immediately starts collecting events about activity in the subscription, and platform metrics are collected for any Azure resources you created. Features such as metrics explorer are available to analyze data. Other features require configuration. This scenario identifies the configuration steps required to take advantage of all Azure Monitor features. It also makes recommendations for which features you should use and how to determine configuration options based on your particular requirements.
+
+The goal of a complete implementation is to collect all useful data from all of your cloud resources and applications and enable the entire set of Azure Monitor features based on that data.
+To enable Azure Monitor to monitor all of your Azure resources, you need to both:
+- Configure Azure Monitor components
+- Configure Azure resources to generate monitoring data for Azure Monitor to collect.
+
+> [!IMPORTANT]
+> If you're new to Azure Monitor or are want to monitor a single Azure resource, start with the [Monitor Azure resources with Azure Monitor tutorial](essentials/monitor-azure-resource.md). The tutorial provides general concepts for Azure Monitor and guidance for monitoring a single Azure resource. This article provides recommendations for preparing your environment to leverage all features of Azure Monitor to monitoring your entire set of applications and resources together at scale.
+
+## Getting started workflow
+These articles provide detailed information about each of the main steps you'll need to do when getting started with Azure Monitor.
+
+| Article | Description |
+|:---|:---|
+| [Planning](best-practices-plan.md)  | Things that you should consider before starting your implementation. Includes design decisions and information about your organization and requirements that you should gather. |
+| [Configure data collection](best-practices-data-collection.md) | Tasks required to collect monitoring data from your Azure and hybrid applications and resources. |
+| [Analysis and visualizations](best-practices-analysis.md) | Standard features and additional visualizations that you can create to analyze collected monitoring data. |
+| [Alerts and automated responses](best-practices-alerts.md) | Configure notifications and processes that are automatically triggered when an alert is created. |
+| [Best practices and cost management](best-practices-cost.md) | Reducing your cloud monitoring costs by implementing and managing Azure Monitor in the most cost-effective manner. |
+
+
+## Next steps
+
+- [Planning your monitoring strategy and configuration](best-practices-plan.md)
diff --git a/articles/azure-monitor/toc.yml b/articles/azure-monitor/toc.yml
@@ -9,6 +9,18 @@ items:
     href: observability-data.md
   - name: What can you monitor?
     href: monitor-reference.md
+  - name: Getting started
+    items:
+    - name: Overview
+      href: getting-started.md
+    - name: Planning
+      href: best-practices-plan.md
+    - name: Configure data collection
+      href: best-practices-data-collection.md
+    - name: Analysis and visualizations
+      href: best-practices-analysis.md
+    - name: Alerts and automated actions
+      href: best-practices-alerts.md
   - name: Optimize costs
     href: best-practices-cost.md
   - name: What's new?
@@ -28,31 +40,23 @@ items:
     href: faq.yml
 - name: Tutorials
   items:
-  - name: End to end deployment
-    items:
-    - name: Overview
-      href: best-practices.md
-    - name: Planning
-      href: best-practices-plan.md
-    - name: Configure data collection
-      href: best-practices-data-collection.md
-    - name: Analysis and visualizations
-      href: best-practices-analysis.md
-    - name: Alerts and automated actions
-      href: best-practices-alerts.md
-  - name: Monitor an Azure Resource - Overview
+  - name: Monitor an Azure Resource
     href: essentials/monitor-azure-resource.md
   - name: Analyze metric data
     href: essentials/tutorial-metrics.md
   - name: Collect and view resource logs
-    href: essentials/tutorial-resource-logs.md
-  - name: Create a metric alert
-    href: alerts/tutorial-metric-alert.md
-  - name: Create a log query alert
-    href: alerts/tutorial-log-alert.md
+    href: essentials/tutorial-resource-logs.md 
   - name: Virtual machines
     items:
-    - name: Monitor a virtual machine
+    - name: Enable recommended alerts
+      href: vm/tutorial-monitor-vm-alert-recommended.md
+    - name: Create availability alert
+      href: vm/tutorial-monitor-vm-alert-availability.md
+    - name: Enable VM insights
+      href: vm/tutorial-monitor-vm-enable-insights.md
+    - name: Collect guest logs and metrics
+      href: vm/tutorial-monitor-vm-guest.md
+    - name: Monitor virtual machines
       items:
       - name: Overview
         href: vm/monitor-virtual-machine.md
@@ -66,38 +70,6 @@ items:
         href: vm/monitor-virtual-machine-alerts.md
       - name: Migrate management pack logic
         href: vm/monitor-virtual-machine-management-packs.md
-    - name: Enable recommended alerts
-      href: vm/tutorial-monitor-vm-alert-recommended.md
-    - name: Create availability alert
-      href: vm/tutorial-monitor-vm-alert-availability.md
-    - name: Enable VM insights
-      href: vm/tutorial-monitor-vm-enable-insights.md
-    - name: Collect guest logs and metrics
-      href: vm/tutorial-monitor-vm-guest.md
-  - name: Application Insights
-    items:
-    - name: Application Insights SDK for ASP.NET Core applications
-      href: app/tutorial-asp-net-core.md
-    - name: Custom metrics with .NET and .NET Core
-      href: app/tutorial-asp-net-custom-metrics.md
-    - name: Find application run-time exceptions
-      href: app/tutorial-runtime-exceptions.md
-    - name: Find application performance issues
-      href: app/tutorial-performance.md
-    - name: Understand application users
-      href: app/tutorial-users.md
-    - name: Dashboard with application data
-      href: app/tutorial-app-dashboards.md
-    - name: Monitor mobile or UWP application
-      href: app/mobile-center-quickstart.md
-  - name: Change Analysis
-    items:
-      - name: Track web outages
-        href: change/tutorial-outages.md
-  - name: Monitor Kubernetes
-    href: ../aks/monitor-aks.md?toc=/azure/azure-monitor/toc.json
-  - name: Forward syslog data to workspace
-    href: ../sentinel/forward-syslog-monitor-agent.md?bc=%2fazure%2fazure-monitor%2fbreadcrumb%2ftoc.json&toc=%2fazure%2fazure-monitor%2ftoc.json
   - name: Self-monitoring
     href: monitor-azure-monitor.md 
 - name: Samples
@@ -233,7 +205,9 @@ items:
         href: agents/data-collection-text-log.md
       - name: Collect SNMP traps
         displayName: data collection rule,Azure Monitor agent
-        href: agents/data-collection-snmp-data.md        
+        href: agents/data-collection-snmp-data.md
+      - name: Forward syslog data to workspace
+        href: ../sentinel/forward-syslog-monitor-agent.md?bc=%2fazure%2fazure-monitor%2fbreadcrumb%2ftoc.json&toc=%2fazure%2fazure-monitor%2ftoc.json        
     - name: Define network settings
       href: agents/azure-monitor-agent-data-collection-endpoint.md
     - name: Migrate from Log Analytics Agent
@@ -582,6 +556,22 @@ items:
       href: app/app-insights-overview.md
     - name: FAQ
       href: /azure/azure-monitor/faq#application-insights
+    - name: Tutorials
+      items:
+        - name: Application Insights SDK for ASP.NET Core applications
+          href: app/tutorial-asp-net-core.md
+        - name: Custom metrics with .NET and .NET Core
+          href: app/tutorial-asp-net-custom-metrics.md
+        - name: Find application run-time exceptions
+          href: app/tutorial-runtime-exceptions.md
+        - name: Find application performance issues
+          href: app/tutorial-performance.md
+        - name: Understand application users
+          href: app/tutorial-users.md
+        - name: Dashboard with application data
+          href: app/tutorial-app-dashboards.md
+        - name: Monitor mobile or UWP application
+          href: app/mobile-center-quickstart.md
     - name: Auto-instrumentation
       items:
       - name: Overview
@@ -950,6 +940,7 @@ items:
         href: app/sharepoint.md
       - name: Windows desktop
         href: app/windows-desktop.md
+ 
   - name: Container insights
     items:
     - name: Overview
@@ -1305,6 +1296,12 @@ items:
       href: change/change-analysis-enable.md
     - name: Visualizations
       href: change/change-analysis-visualizations.md
+    - name: Custom filters
+      href: change/change-analysis-custom-filters.md
+    - name: Pin and share changes via Azure dashboard
+      href: change/change-analysis-query.md
+    - name: Track a web outage with Change Analysis
+      href: change/change-analysis-track-outages.md
     - name: Troubleshoot
       href: change/change-analysis-troubleshoot.md
 - name: Respond
@@ -1436,6 +1433,12 @@ items:
         href: alerts/alerts-enable-template.md
       - name: Classic metric alert calling a webhook
         href: alerts/alerts-webhooks.md
+    - name: Tutorials
+      items:
+      - name: Create a metric alert
+        href: alerts/tutorial-metric-alert.md
+      - name: Create a log query alert
+        href: alerts/tutorial-log-alert.md
   - name: AutoScale
     items:
       - name: Overview
diff --git a/articles/sentinel/forward-syslog-monitor-agent.md b/articles/sentinel/forward-syslog-monitor-agent.md
@@ -10,13 +10,13 @@ ms.custom: template-tutorial
 #Customer intent: As a security-engineer, I want to get syslog data into Microsoft Sentinel so that I can use the data with other data to do attack detection, threat visibility, proactive hunting, and threat response. As an IT administrator, I want to get syslog data into my Log Analytics workspace to monitor my linux-based devices.
 ---
 
-# Tutorial: Forward syslog data to a Log Analytics workspace by using the Azure Monitor agent
+# Forward syslog data to a Log Analytics workspace by using the Azure Monitor agent
 
-In this tutorial, you'll configure a Linux virtual machine (VM) to forward syslog data to your workspace by using the Azure Monitor agent. These steps allow you to collect and monitor data from Linux-based devices where you can't install an agent like a firewall network device.
+In this article, we'll describe how to configure a Linux virtual machine (VM) to forward syslog data to your workspace by using the Azure Monitor agent. These steps allow you to collect and monitor data from Linux-based devices where you can't install an agent like a firewall network device.
  
 Configure your linux-based device to send data to a Linux VM. The Azure Monitor agent on the VM forwards the syslog data to the Log Analytics workspace. Then use Microsoft Sentinel or Azure Monitor to monitor the device from the data stored in the Log Analytics workspace.
 
-In this tutorial, you learn how to:
+In this article, you learn how to:
 
 > [!div class="checklist"]
 > * Create a data collection rule
@@ -26,7 +26,7 @@ In this tutorial, you learn how to:
 
 ## Prerequisites
 
-To complete the steps in this tutorial, you must have the following resources and roles.
+To complete the steps in this article, you must have the following resources and roles.
 
 - Azure account with an active subscription. [Create an account for free](https://azure.microsoft.com/free/?WT.mc_id=A261C142F).
 - Azure account with the following roles to deploy the agent and create the data collection rules:
