Skip to content

Commit 7d087f1

Browse files
Merge pull request #257890 from guywi-ms/patch-86
Update cross-workspace-query.md
2 parents efceb00 + b92d7db commit 7d087f1

File tree

1 file changed

+3
-2
lines changed

1 file changed

+3
-2
lines changed

articles/azure-monitor/logs/cross-workspace-query.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,8 +2,8 @@
22
title: Query across resources with Azure Monitor | Microsoft Docs
33
description: This article describes how you can query against resources from multiple workspaces and an Application Insights app in your subscription.
44
ms.topic: conceptual
5-
author: bwren
6-
ms.author: bwren
5+
author: guywi-ms
6+
ms.author: guywild
77
ms.date: 05/30/2023
88

99
---
@@ -30,6 +30,7 @@ There are two methods to query data that's stored in multiple workspaces and app
3030
## Cross-resource query limits
3131

3232
* The number of Application Insights components and Log Analytics workspaces that you can include in a single query is limited to 100.
33+
* Querying across a large number of resources can substantially slow down the query.
3334
* Cross-resource queries in log alerts are only supported in the current [scheduledQueryRules API](/rest/api/monitor/scheduledqueryrule-2018-04-16/scheduled-query-rules). If you're using the legacy Log Analytics Alerts API, you'll need to [switch to the current API](../alerts/alerts-log-api-switch.md).
3435
* References to a cross resource, such as another workspace, should be explicit and can't be parameterized. See [Gather identifiers for Log Analytics workspaces](?tabs=workspace-identifier#gather-identifiers-for-log-analytics-workspaces-and-application-insights-resources) for examples.
3536

0 commit comments

Comments
 (0)