Merge pull request #222486 from pritamso/Broken-link-fix-yanivlavi

Broken link removed

Author: prmerger-automator[bot]

articles/azure-monitor/alerts/alerts-troubleshoot-log.md

@@ -75,7 +75,7 @@ When a log alert rule is created, the query is validated for correct syntax. But
 
 - Rules were created via the API, and validation was skipped by the user.
 - The query [runs on multiple resources](../logs/cross-workspace-query.md), and one or more of the resources was deleted or moved.
-- The [query fails](https://dev.loganalytics.io/documentation/Using-the-API/Errors) because:
+- The [query fails](/azure/azure-monitor/logs/api/errors) because:
     - The logging solution wasn't [deployed to the workspace](../insights/solutions.md#install-a-monitoring-solution), so tables aren't created.
     - Data stopped flowing to a table in the query for more than 30 days.
     - [Custom logs tables](../agents/data-sources-custom-logs.md) aren't yet created, because the data flow hasn't started.
@@ -200,4 +200,4 @@ Try the following steps to resolve the problem:
 
 - Learn about [log alerts in Azure](./alerts-unified-log.md).
 - Learn more about [configuring log alerts](../logs/log-query-overview.md).
-- Learn more about [log queries](../logs/log-query-overview.md).
+- Learn more about [log queries](../logs/log-query-overview.md).