Merge pull request #281796 from cdpark/horz-monitor-notification

Q&M: Curate 27 SOX Azure Monitor horizontals articles to reduce duplication -- Notification Hubs

Author: v-dirichards

articles/notification-hubs/TOC.yml

@@ -160,7 +160,7 @@
     href: notification-hubs-baidu-china-android-notifications-get-started.md
   - name: Use APNS VOIP through Notification Hubs
     href: voip-apns.md  
-  - name: Monitor
+  - name: Monitor Notification Hubs
     href: monitor-notification-hubs.md
   - name: Enable diagnostic logs
     href: notification-hubs-diagnostic-logs.md

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

@@ -20,7 +20,7 @@ See [Monitor Notification Hubs](monitor-notification-hubs.md) for details on the
 ### Supported metrics for Microsoft.NotificationHubs/namespaces/notificationHubs
 The following table lists the metrics available for the Microsoft.NotificationHubs/namespaces/notificationHubs resource type.
 [!INCLUDE [horz-monitor-ref-metrics-tableheader](~/reusable-content/ce-skilling/azure/includes/azure-monitor/horizontals/horz-monitor-ref-metrics-tableheader.md)]
-[!INCLUDE [Microsoft.NotificationHubs/namespaces/notificationHubs](~/azure-reference-other-repo/azure-monitor-ref/supported-metrics/includes/microsoft-notificationhubs-namespaces-notificationhubs-metrics-include.md)]
+[!INCLUDE [Microsoft.NotificationHubs/namespaces/notificationHubs](~/reusable-content/ce-skilling/azure/includes/azure-monitor/reference/metrics/microsoft-notificationhubs-namespaces-notificationhubs-metrics-include.md)]
 
 [!INCLUDE [horz-monitor-ref-metrics-dimensions-intro](~/reusable-content/ce-skilling/azure/includes/azure-monitor/horizontals/horz-monitor-ref-metrics-dimensions-intro.md)]
 
@@ -29,10 +29,10 @@ The following table lists the metrics available for the Microsoft.NotificationHu
 [!INCLUDE [horz-monitor-ref-resource-logs](~/reusable-content/ce-skilling/azure/includes/azure-monitor/horizontals/horz-monitor-ref-resource-logs.md)]
 
 ### Supported resource logs for Microsoft.NotificationHubs/namespaces
-[!INCLUDE [Microsoft.NotificationHubs/namespaces](~/azure-reference-other-repo/azure-monitor-ref/supported-logs/includes/microsoft-notificationhubs-namespaces-logs-include.md)]
+[!INCLUDE [Microsoft.NotificationHubs/namespaces](~/reusable-content/ce-skilling/azure/includes/azure-monitor/reference/logs/microsoft-notificationhubs-namespaces-logs-include.md)]
 
 ### Supported resource logs for Microsoft.NotificationHubs/namespaces/notificationHubs
-[!INCLUDE [Microsoft.NotificationHubs/namespaces/notificationHubs](~/azure-reference-other-repo/azure-monitor-ref/supported-logs/includes/microsoft-notificationhubs-namespaces-notificationhubs-logs-include.md)]
+[!INCLUDE [Microsoft.NotificationHubs/namespaces/notificationHubs](~/reusable-content/ce-skilling/azure/includes/azure-monitor/reference/logs/microsoft-notificationhubs-namespaces-notificationhubs-logs-include.md)]
 
 [!INCLUDE [horz-monitor-ref-logs-tables](~/reusable-content/ce-skilling/azure/includes/azure-monitor/horizontals/horz-monitor-ref-logs-tables.md)]
 <!-- No table(s) at https://learn.microsoft.com/azure/azure-monitor/reference/tables/tables-resourcetype. -->

articles/notification-hubs/notification-hubs-diagnostic-logs.md

@@ -21,19 +21,7 @@ All logs are stored in JavaScript Object Notation (JSON) format in the following
 - **AzureActivity**: Displays logs from operations and actions that are conducted against your namespace in the Azure portal or through Azure Resource Manager template deployments.
 - **AzureDiagnostics**: Displays logs from operations and actions that are conducted against your namespace by using the API, or through management clients on the language SDK.
 
-Diagnostic log JSON strings include the elements listed in the following table:
-
-| Name | Description |
-| ------- | ------- |
-| time | UTC timestamp of the log |
-| resourceId | Relative path to the Azure resource |
-| operationName | Name of the management operation |
-| category | Log category. Valid values: `OperationalLogs` |
-| callerIdentity | Identity of the caller who initiated the management operation |
-| resultType | Status of the management operation. Valid values: `Succeeded` or `Failed` |
-| resultDescription | Description of the management operation |
-| correlationId | Correlation ID of the management operation (if specified) |
-| callerIpAddress | The caller IP address. Empty for calls that originated from the Azure portal |
+For a list of elements that are included in diagnostic log strings, see [Azure Monitor Logs tables](monitor-notification-hubs-reference.md#azure-monitor-logs-tables).
 
 Here's an example of an operational log JSON string: