Merge pull request #216745 from baanders/10-31-monitor

ADT: Revamp monitoring articles

Author: Court72

articles/digital-twins/.openpublishing.redirection.digital-twins.json

@@ -1,5 +1,20 @@
 {
   "redirections": [
+    {
+      "source_path": "how-to-monitor-metrics.md",
+      "redirect_url": "/azure/digital-twins/how-to-monitor",
+      "redirect_document_id": true
+    },
+    {
+      "source_path": "how-to-monitor-diagnostics.md",
+      "redirect_url": "/azure/digital-twins/how-to-monitor",
+      "redirect_document_id": false
+    },    
+    {
+      "source_path": "how-to-monitor-alerts.md",
+      "redirect_url": "/azure/digital-twins/how-to-monitor",
+      "redirect_document_id": false
+    },
     {
       "source_path": "how-to-create-app-registration-portal.md",
       "redirect_url": "/azure/digital-twins/how-to-create-app-registration",
@@ -31,8 +46,8 @@
       "redirect_document_id": true
     },
     {
-      "source_path": "troubleshoot-resource-health.md",
-      "redirect_url": "/azure/digital-twins/how-to-monitor-resource-health",
+      "source_path": "how-to-monitor-resource-health.md",
+      "redirect_url": "/azure/digital-twins/troubleshoot-resource-health",
       "redirect_document_id": true
     },
     {

articles/digital-twins/TOC.yml

@@ -137,14 +137,10 @@
       href: how-to-integrate-maps.md
   - name: Monitor and troubleshoot
     items:
-    - name: Metrics
-      href: how-to-monitor-metrics.md
-    - name: Diagnostics logs
-      href: how-to-monitor-diagnostics.md
-    - name: Alerts
-      href: how-to-monitor-alerts.md
-    - name: Resource health
-      href: how-to-monitor-resource-health.md
+    - name: Monitor your instance
+      href: how-to-monitor.md
+    - name: Troubleshoot resource health
+      href: troubleshoot-resource-health.md
     - name: Troubleshoot performance
       href: troubleshoot-performance.md
     - name: Known issues

articles/digital-twins/concepts-apis-sdks.md

@@ -120,11 +120,7 @@ Service methods return strongly typed objects wherever possible. However, becaus
 
 API metrics such as requests, latency, and failure rate can be viewed in the [Azure portal](https://portal.azure.com/). 
 
-From the portal homepage, search for your Azure Digital Twins instance to pull up its details. Select the **Metrics** option from the Azure Digital Twins instance's menu to bring up the **Metrics** page.
-
-:::image type="content" source="media/how-to-monitor-metrics/azure-digital-twins-metrics.png" alt-text="Screenshot showing the metrics page for Azure Digital Twins.":::
-
-From here, you can view the metrics for your instance and create custom views.
+For information about viewing and managing metrics with Azure Monitor, see [Get started with metrics explorer](../azure-monitor/essentials/metrics-getting-started.md). For a full list of API metrics available for Azure Digital Twins, see [Azure Digital Twins API request metrics](how-to-monitor.md#api-request-metrics).
 
 ## Next steps
 

articles/digital-twins/how-to-manage-routes.md

@@ -156,7 +156,7 @@ az resource create --id <Azure-Digital-Twins-instance-Azure-resource-ID>/endpoin
 
 When an endpoint can't deliver an event within a certain time period or after trying to deliver the event a certain number of times, it can send the undelivered event to a storage account. This process is known as *dead-lettering*.
 
-You can set up the necessary storage resources using the [Azure portal](https://portal.azure.com/#home) or the [Azure Digital Twins CLI](/cli/azure/dt). However, to create an endpoint with dead-lettering enabled, you'll need use the [Azure Digital Twins CLI](/cli/azure/dt) or [control plane APIs](concepts-apis-sdks.md#overview-control-plane-apis).
+You can set up the necessary storage resources using the [Azure portal](https://portal.azure.com/#home) or the [Azure Digital Twins CLI](/cli/azure/dt). However, to create an endpoint with dead-lettering enabled, you'll need to use the [Azure Digital Twins CLI](/cli/azure/dt) or [control plane APIs](concepts-apis-sdks.md#overview-control-plane-apis).
 
 To learn more about dead-lettering, see [Endpoints and event routes](concepts-route-events.md#dead-letter-events). For instructions on how to set up an endpoint with dead-lettering, continue through the rest of this section.
 
@@ -473,15 +473,9 @@ When you implement or update a filter, the change may take a few minutes to be r
 
 Routing metrics such as count, latency, and failure rate can be viewed in the [Azure portal](https://portal.azure.com/). 
 
-From the portal homepage, search for your Azure Digital Twins instance to pull up its details. Select the **Metrics** option from the Azure Digital Twins instance's navigation menu on the left to bring up the **Metrics** page.
-
-:::image type="content" source="media/how-to-monitor-metrics/azure-digital-twins-metrics.png" alt-text="Screenshot showing the metrics page for Azure Digital Twins.":::
-
-From here, you can view the metrics for your instance and create custom views.
-
-For more on viewing Azure Digital Twins metrics, see [Monitor with metrics](how-to-monitor-metrics.md).
+For information about viewing and managing metrics with Azure Monitor, see [Get started with metrics explorer](../azure-monitor/essentials/metrics-getting-started.md). For a full list of routing metrics available for Azure Digital Twins, see [Azure Digital Twins routing metrics](how-to-monitor.md#routing-metrics).
 
 ## Next steps
 
 Read about the different types of event messages you can receive:
-* [Event notifications](concepts-event-notifications.md)
+* [Event notifications](concepts-event-notifications.md)