Skip to content

Commit 445e5c6

Browse files
Merge pull request #232527 from bwren/patch-58
Update best-practices-cost.md
2 parents cc35b14 + 5b70f67 commit 445e5c6

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/azure-monitor/best-practices-cost.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -41,7 +41,7 @@ Azure Monitor includes the following design considerations related to cost:
4141
> [!div class="checklist"]
4242
> - Use diagnostic settings and transformations to collect only critical resource log data from Azure resources.
4343
> - Configure VM agents to collect only critical events.
44-
> - Use transformations to filter resource logs.
44+
> - Use transformations to filter resource logs for [supported tables](logs/tables-feature-support.md).
4545
> - Ensure that VMs aren't sending data to multiple workspaces.
4646
4747
**Monitor usage**
@@ -74,7 +74,7 @@ Since Azure Monitor charges for the collection of data, your goal should be to c
7474

7575
| Recommendation | Description |
7676
|:---|:---|
77-
| Collect only critical resource log data from Azure resources. | When you create [diagnostic settings](essentials/diagnostic-settings.md) to send [resource logs](essentials/resource-logs.md) for your Azure resources to a Log Analytics database, only specify those categories that you require. Since diagnostic settings don't allow granular filtering of resource logs, use a [workspace transformation](essentials/data-collection-transformations.md?#workspace-transformation-dcr) to further filter unneeded data. See [Diagnostic settings in Azure Monitor](essentials/diagnostic-settings.md#controlling-costs) for details on how to configure diagnostic settings and using transformations to filter their data. |
77+
| Collect only critical resource log data from Azure resources. | When you create [diagnostic settings](essentials/diagnostic-settings.md) to send [resource logs](essentials/resource-logs.md) for your Azure resources to a Log Analytics database, only specify those categories that you require. Since diagnostic settings don't allow granular filtering of resource logs, you can use a [workspace transformation](essentials/data-collection-transformations.md?#workspace-transformation-dcr) to further filter unneeded data for those resources that use a [supported table](logs/tables-feature-support.md). See [Diagnostic settings in Azure Monitor](essentials/diagnostic-settings.md#controlling-costs) for details on how to configure diagnostic settings and using transformations to filter their data. |
7878

7979
#### Virtual machines
8080

0 commit comments

Comments
 (0)