Merge pull request #230914 from pritamso/Broken-link-fix-mukeshdua

Broken link fixed

Author: prmerger-automator[bot]

articles/operator-nexus/howto-monitor-aks-h-cluster.md

@@ -144,7 +144,7 @@ export LAW_RESOURCE_ID=$(az monitor log-analytics workspace show -g "${RESOURCE_
 ./dcr.sh
 ```
 
-View/manage the DCR from the Azure portal or [CLI](/azure/monitor/data-collection/rule).
+View/manage the DCR from the Azure portal or [CLI](/cli/azure/monitor/data-collection/rule).
 By default, the Linux Syslog log level is set to "INFO". You can change the log level as needed.
 
 > [!NOTE]
@@ -314,4 +314,4 @@ Container Insights provides end-users functionality to fine-tune the collection
 ## Extra resources
 
 - Review [workbooks documentation](../azure-monitor/visualize/workbooks-overview.md) and then you may use Operator Nexus telemetry [sample Operator Nexus workbooks](https://github.com/microsoft/AzureMonitorCommunity/tree/master/Azure%20Services/Azure%20Operator%20Distributed%20Services).
-- Review [Azure Monitor Alerts](../azure-monitor/alerts/alerts-overview.md), how to create [Azure Monitor Alert rules](../azure-monitor/alerts/alerts-create-new-alert-rule.md?tabs=metric), and use [sample Operator Nexus Alert templates](https://github.com/microsoft/AzureMonitorCommunity/tree/master/Azure%20Services/Azure%20Operator%20Distributed%20Services).
+- Review [Azure Monitor Alerts](../azure-monitor/alerts/alerts-overview.md), how to create [Azure Monitor Alert rules](../azure-monitor/alerts/alerts-create-new-alert-rule.md?tabs=metric), and use [sample Operator Nexus Alert templates](https://github.com/microsoft/AzureMonitorCommunity/tree/master/Azure%20Services/Azure%20Operator%20Distributed%20Services).