Skip to content

Commit 436604e

Browse files
committed
acrolinx fixes
1 parent 899a744 commit 436604e

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

articles/lighthouse/how-to/monitor-at-scale.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
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.
44
ms.date: 02/03/2020
55
ms.topic: conceptual
66
---
@@ -9,19 +9,19 @@ ms.topic: conceptual
99

1010
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.
1111

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.
1313

1414
## Create Log Analytics workspaces
1515

1616
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.
1717

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.
1919

2020
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).
2121

2222
## Deploy policies that log data
2323

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.
2525

2626
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.
2727

0 commit comments

Comments
 (0)