Skip to content

Commit d41292b

Browse files
Merge pull request #276684 from guywi-ms/patch-115
Update workspace-design.md
2 parents cda3d59 + f232ca2 commit d41292b

File tree

1 file changed

+2
-3
lines changed

1 file changed

+2
-3
lines changed

articles/azure-monitor/logs/workspace-design.md

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -2,8 +2,7 @@
22
title: Design a Log Analytics workspace architecture
33
description: The article describes the considerations and recommendations for customers preparing to deploy a workspace in Azure Monitor.
44
ms.topic: conceptual
5-
ms.date: 04/05/2023
6-
5+
ms.date: 05/30/2024
76
---
87

98
# Design a Log Analytics workspace architecture
@@ -15,7 +14,7 @@ A single [Log Analytics workspace](log-analytics-workspace-overview.md) might be
1514
1615
Here's a video about the fundamentals of Azure Monitor Logs and best practices and design considerations for designing your Azure Monitor Logs deployment:
1716

18-
> [!VIDEO https://www.youtube.com/embed/pqUvZqoQV4o]
17+
> [!VIDEO https://www.youtube.com/embed/7RBp9j0P_Ao?cc_load_policy=1&cc_lang_pref=auto]
1918
2019
## Design strategy
2120
Your design should always start with a single workspace to reduce the complexity of managing multiple workspaces and in querying data from them. There are no performance limitations from the amount of data in your workspace. Multiple services and data sources can send data to the same workspace. As you identify criteria to create more workspaces, your design should use the fewest number that will match your requirements.

0 commit comments

Comments
 (0)