Merge pull request #188251 from spelluru/sbehmetrics0210

Dimensions are not exported

Author: PMEds28

.openpublishing.redirection.azure-monitor.json

@@ -9,6 +9,11 @@
             "source_path_from_root": "/articles/application-insights/app-insights-performance-counters.md",
             "redirect_url": "/azure/azure-monitor/app/performance-counters",
             "redirect_document_id": true
+        },
+        {
+            "source_path_from_root": "/articles/azure-monitor/insights/service-bus-insights.md",
+            "redirect_url": "/azure/service-bus-messaging/service-bus-insights",
+            "redirect_document_id": false
         }
     ]
 }

articles/azure-monitor/toc.yml

@@ -1224,8 +1224,6 @@ items:
       href: insights/cosmosdb-insights-overview.md
     - name: Azure Data Explorer
       href: insights/data-explorer.md
-    - name: Azure Service Bus
-      href: insights/service-bus-insights.md
     - name: Log Analytics workspace
       href: logs/log-analytics-workspace-insights-overview.md
     - name: Networks

articles/azure-monitor/whats-new.md

@@ -175,7 +175,7 @@ This article lists significant changes to Azure Monitor documentation.
 
 **New articles**
 
-- [Azure Monitor - Service Bus insights](insights/service-bus-insights.md)
+- [Azure Monitor - Service Bus insights](../service-bus-messaging/service-bus-insights.md)
 
 **Updated articles**
 

articles/event-hubs/monitor-event-hubs-reference.md

@@ -3,13 +3,16 @@ title: Monitoring Azure Event Hubs data reference
 description: Important reference material needed when you monitor Azure Event Hubs. 
 ms.topic: reference
 ms.custom: subject-monitoring
-ms.date: 01/20/2022
+ms.date: 02/10/2022
 ---
 
 
 # Monitoring Azure Event Hubs data reference
 See [Monitoring Azure Event Hubs](monitor-event-hubs.md) for details on collecting and analyzing monitoring data for Azure Event Hubs.
 
+> [!NOTE]
+> Azure Monitor doesn't include dimensions in the exported metrics data that's sent to a destination (Azure Storage, Azure Event Hubs, or Log Analytics).
+
 ## Metrics
 This section lists all the automatically collected platform metrics collected for Azure Event Hubs. The resource provider for these metrics is **Microsoft.EventHub/clusters** or **Microsoft.EventHub/clusters**.
 
@@ -138,6 +141,9 @@ Name | Description
 ## Azure Monitor Logs tables
 Azure Event Hubs uses Kusto tables from Azure Monitor Logs. You can query these tables with Log Analytics. For a list of Kusto tables the service uses, see [Azure Monitor Logs table reference](/azure/azure-monitor/reference/tables/tables-resourcetype#event-hubs).
 
+> [!IMPORTANT]
+> Dimensions aren't exported to a Log Analytics workspace. 
+
 
 ## Next steps
 - For details on monitoring Azure Event Hubs, see [Monitoring Azure Event Hubs](monitor-event-hubs.md).

articles/event-hubs/monitor-event-hubs.md

@@ -3,7 +3,7 @@ title: Monitoring Azure Event Hubs
 description: Learn how to use Azure Monitor to view, analyze, and create alerts on metrics from Azure Event Hubs. 
 ms.topic: conceptual
 ms.custom: subject-monitoring
-ms.date: 01/20/2022
+ms.date: 02/10/2022
 ---
 
 # Monitor Azure Event Hubs
@@ -37,10 +37,16 @@ Resource Logs aren't collected and stored until you create a diagnostic setting
 
 See [Create diagnostic setting to collect platform logs and metrics in Azure](../azure-monitor/essentials/diagnostic-settings.md) for the detailed process for creating a diagnostic setting using the Azure portal, CLI, or PowerShell. When you create a diagnostic setting, you specify which categories of logs to collect. The categories for Azure Event Hubs are listed in [Azure Event Hubs monitoring data reference](monitor-event-hubs-reference.md#resource-logs).
 
+> [!NOTE]
+> Azure Monitor doesn't include dimensions in the exported metrics data that's sent to a destination (Azure Storage, Azure Event Hubs, or Log Analytics).
+
+### Azure Storage
 If you use **Azure Storage** to store the diagnostic logging information, the information is stored in containers named **insights-logs-operationlogs** and **insights-metrics-pt1m**. Sample URL for an operation log: `https://<Azure Storage account>.blob.core.windows.net/insights-logs-operationallogs/resourceId=/SUBSCRIPTIONS/<Azure subscription ID>/RESOURCEGROUPS/<Resource group name>/PROVIDERS/MICROSOFT.SERVICEBUS/NAMESPACES/<Namespace name>/y=<YEAR>/m=<MONTH-NUMBER>/d=<DAY-NUMBER>/h=<HOUR>/m=<MINUTE>/PT1H.json`. The URL for a metric log is similar. 
 
+### Azure Event Hubs
 If you use **Azure Event Hubs** to store the diagnostic logging information, the information is stored in Event Hubs instances named **insights-logs-operationlogs** and **insights-metrics-pt1m**. You can also select your own event hub. 
 
+### Log Analytics
 If you use **Log Analytics** to store the diagnostic logging information, the information is stored in tables named **AzureDiagnostics** and **AzureMetrics**. 
 
 > [!IMPORTANT]

articles/service-bus-messaging/TOC.yml

@@ -220,6 +220,8 @@
       href: service-bus-end-to-end-tracing.md
     - name: Monitoring Azure Service Bus
       href: monitor-service-bus.md
+    - name: Azure Monitor - Service Bus insights
+      href: service-bus-insights.md
   - name: Integrate
     items:
     - name: Integrate with RabbitMQ