Skip to content

Commit c31aa25

Browse files
author
Amson Liu
authored
Merge pull request #9353 from amsliu/v-liuamson-CI6621
New article for CI 6621.
2 parents 73cb421 + 9b66ca3 commit c31aa25

File tree

2 files changed

+47
-0
lines changed

2 files changed

+47
-0
lines changed
Lines changed: 45 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,45 @@
1+
---
2+
title: Understand and Mitigate High Data Consumption in Log Analytics
3+
description: Provides instructions to resolve high data usage in Log Analytics.
4+
ms.date: 07/24/2025
5+
ms.reviewer: v-liuamson; v-gsitser
6+
ms.service: azure-monitor
7+
ms.custom: Configure and Manage Log analytics tables
8+
---
9+
10+
# Understand and mitigate high data consumption in Log Analytics
11+
12+
This article discusses high data consumption that occurs in Log Analytics workspaces, and focuses on tables such as `AzureDiagnostics`. This article also provides insights into the costs that are associated with data usage, and offers steps to optimize and reduce these costs.
13+
14+
## Common issues and solutions
15+
16+
- **Data retention**: Make sure that data retention settings are configured appropriately to avoid unnecessary storage costs.
17+
- **Data filtering**: Implement data filtering to collect only necessary data and reduce the volume of data ingested.
18+
19+
### Instructions to resolve high data usage
20+
21+
1. Identify high data tables:
22+
23+
1. Use the `AzureDiagnostics` table to determine which listed references are sending large amounts of data.
24+
1. To identify the reference that's contributing to high data usage, run the following query in your Log Analytics workspace:
25+
26+
```plaintext
27+
AzureDiagnostics | distinct _ResourceId
28+
```
29+
30+
2. Review the diagnostic settings:
31+
32+
1. Navigate to the diagnostic settings of the identified reference.
33+
1. Remove unnecessary diagnostic settings if the data isn't required. This step stops the data from being sent to the AzureDiagnostics table.
34+
35+
3. Review the articles in the ["References" section](#references) to understand the costs that are associated with your Log Analytics workspace.
36+
37+
4. To optimize data usage and reduce costs, follow the best practices that are outlined in the "References" section.
38+
39+
## References
40+
41+
- [Understand Azure Monitor pricing](https://azure.microsoft.com/pricing/details/monitor/)
42+
- [Best Practices for Cost Management](/azure/azure-monitor/fundamentals/best-practices-cost)
43+
- [Cost Management for Logs](/azure/azure-monitor/logs/cost-logs)
44+
45+
If the issue persists after you follow the solution steps, open a support case for further assistance.

support/azure/azure-monitor/toc.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -115,6 +115,8 @@ items:
115115
items:
116116
- name: Configure and Manage Log analytics tables
117117
items:
118+
- name: Understand and mitigate high data consumption in Log Analytics
119+
href: log-analytics/configure-and-manage-log-analytics-tables/understand-and-mitigate-high-data-consumption-log-analytics.md
118120
- name: Troubleshoot custom table creation errors in Azure
119121
href: log-analytics/configure-and-manage-log-analytics-tables/troubleshoot-custom-table-creation-errors.md
120122
- name: Troubleshoot custom log table creation in Azure

0 commit comments

Comments
 (0)