You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/lighthouse/how-to/monitor-at-scale.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
---
2
2
title: Monitor delegated resources at scale
3
-
description: Learn how to effectively use Azure Monitor to gather data across the customer tenants you’re managing.
3
+
description: Learn how to effectively use Azure Monitor in a scalable way across the customer tenants you’re managing.
4
4
ms.date: 02/03/2020
5
5
ms.topic: conceptual
6
6
---
@@ -9,19 +9,19 @@ ms.topic: conceptual
9
9
10
10
As a service provider, you may have onboarded multiple customer tenants for Azure delegated resource management. [Azure Lighthouse](../overview.md) allows service providers to perform operations at scale across several tenants at once, making management tasks more efficient.
11
11
12
-
This topic shows you how to effectively use [Azure Monitor](../../azure-monitor/index.yml)to gain visibility into telemetry data across the customer tenants you’re managing.
12
+
This topic shows you how to use [Azure Monitor](../../azure-monitor/index.yml)in a scalable way across the customer tenants you’re managing.
13
13
14
14
## Create Log Analytics workspaces
15
15
16
16
In order to collect data, you’ll need to create Log Analytics workspaces. These Log Analytics workspaces are unique environments for Azure Monitor log data. Each workspace has its own data repository and configuration, and data sources and solutions are configured to store their data in a particular workspace.
17
17
18
-
We recommend creating these workspaces directly in the customer tenants. This way their data remains in their tenants rather than being exported into yours. This also allows for centralized monitoring of any resources or services supported by Log Analytics, giving you more flexibility on what types of data you monitor.
18
+
We recommend creating these workspaces directly in the customer tenants. This way their data remains in their tenants rather than being exported into yours. This also allows centralized monitoring of any resources or services supported by Log Analytics, giving you more flexibility on what types of data you monitor.
19
19
20
20
You can create a Log Analytics workspace by using the [Azure portal](../../azure-monitor/learn/quick-create-workspace.md), by using [Azure CLI](../../azure-monitor/learn/quick-create-workspace-cli.md), or by using [Azure PowerShell](../../azure-monitor/learn/quick-create-workspace-posh.md).
21
21
22
22
## Deploy policies that log data
23
23
24
-
Once you’ve created your Log Analytics workspaces, you can deploy [Azure Policy](../../governance/policy/index.yml) across your customer hierarchies so that diagnostic data is sent to the appropriate workspace in each tenant. The exact policies you deploy may vary depending on the resource types which you want to monitor.
24
+
Once you’ve created your Log Analytics workspaces, you can deploy [Azure Policy](../../governance/policy/index.yml) across your customer hierarchies so that diagnostic data is sent to the appropriate workspace in each tenant. The exact policies you deploy may vary depending on the resource types that you want to monitor.
25
25
26
26
To learn more about creating policies, see [Tutorial: Create and manage policies to enforce compliance](../../governance/policy/tutorials/create-and-manage.md). This [community tool](https://github.com/Azure/Azure-Lighthouse-samples/tree/master/Azure-Delegated-Resource-Management/tools/azure-diagnostics-policy-generator) provides a script to help you create policies to monitor the specific resource types that you choose.
0 commit comments