Skip to content

Commit 37ef285

Browse files
Update cross-workspace-queries.md
Adding a note to callout that we should use workspace identifiers vs the workspace name as per the same guidance as: https://learn.microsoft.com/en-us/azure/azure-monitor/logs/workspace-expression
1 parent 16e7553 commit 37ef285

File tree

1 file changed

+3
-0
lines changed

1 file changed

+3
-0
lines changed

articles/azure-monitor/logs/api/cross-workspace-queries.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -21,6 +21,9 @@ For either implicit or explicit cross-workspace queries, you need to specify the
2121
- Workspace ID - GUID string
2222
- Azure Resource ID - string with format /subscriptions/\<subscriptionId\>/resourceGroups/\<resourceGroup\>/providers/ microsoft.operationalinsights/workspaces/\<workspaceName\>
2323

24+
> [!NOTE]
25+
> We strongly recommend identifying a workspace by its unique Workspace ID or Azure Resource ID because they remove ambiguity and are more performant.
26+
2427
## Implicit cross workspace queries
2528

2629
For implicit syntax, specify the workspaces that you want to include in your query scope. The API performs a single query over each application provided in your list. The syntax for a cross-workspace POST is:

0 commit comments

Comments
 (0)