Skip to content

Commit 6e1ac17

Browse files
committed
Update waf-logs-cost.md
1 parent fe857a2 commit 6e1ac17

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/azure-monitor/includes/waf-logs-cost.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -31,5 +31,5 @@ ms.date: 08/24/2023
3131
| Regularly analyze collected data to identify trends and anomalies. | Use [Log Analytics workspace insights](../logs/log-analytics-workspace-insights-overview.md) to periodically review the amount of data collected in your workspace. In addition to helping you understand the amount of data collected by different sources, it will identify anomalies and upward trends in data collection that could result in excess cost. Further analyze data collection using methods in [Analyze usage in Log Analytics workspace](../logs/analyze-usage.md) to determine if there's additional configuration that can decrease your usage further. This is particularly important when you add a new set of data sources, such as a new set of virtual machines or onboard a new service. |
3232
| Create an alert when data collection is high. | To avoid unexpected bills, you should be [proactively notified anytime you experience excessive usage](../logs/analyze-usage.md#send-alert-when-data-collection-is-high). Notification allows you to address any potential anomalies before the end of your billing period. |
3333
| Consider a daily cap as a preventative measure to ensure that you don't exceed a particular budget. | A [daily cap](../logs/daily-cap.md) disables data collection in a Log Analytics workspace for the rest of the day after your configured limit is reached. This shouldn't be used as a method to reduce costs as described in [When to use a daily cap](../logs/daily-cap.md#when-to-use-a-daily-cap).<br><br>If you do set a daily cap, in addition to [creating an alert when the cap is reached](../logs/log-analytics-workspace-health.md#view-log-analytics-workspace-health-and-set-up-health-status-alerts), ensure that you also [create an alert rule to be notified when some percentage has been reached (90% for example)](../logs/analyze-usage.md#send-alert-when-data-collection-is-high). This gives you an opportunity to investigate and address the cause of the increased data before the cap shuts off data collection. |
34-
| Set up alerts on Azure Advisor cost recommendations for Log Analytics workspaces. | Azure Advisor recommendations for Log Analytics workspaces proactively alert you when there's an opportunity to optimize your costs. [Create Azure Advisor alerts](../../advisor/advisor-alerts-portal.md) for these cost recommendations: <ul><li>Consider configuring the cost effective Basic logs plan on selected tables - We've identified ingestion of more than 1 GB per month to tables that are eligible for the low cost Basic log data plan. The Basic log plan gives you search capabilities for debugging and troubleshooting at a lower cost.</li><li>Consider Changing Pricing Tier- Based on your current usage volume, investigate changing your pricing (Commitment) tier to receive a discount and reduce costs.</li><li>Consider removing unused restored tables - You have one or more tables with restored data active in your workspace. If you're no longer using a restored data, delete the table to avoid unnecessary charges.</li><li>Data ingestion anomaly was detected - We've identified a much higher ingestion rate over the past week, based on your ingestion in the three previous weeks. Take note of this change and the expected change in your costs.</ul></li>You can also view automatically generated recommendation by selecting **Overview** > **Recommendations** or **Advisor recommendations** from your Log Analytics workspace resource menu.|
34+
| Set up alerts on Azure Advisor cost recommendations for Log Analytics workspaces. | Azure Advisor recommendations for Log Analytics workspaces proactively alert you when there's an opportunity to optimize your costs. [Create Azure Advisor alerts](../../advisor/advisor-alerts-portal.md) for these cost recommendations: <ul><li>Consider configuring the cost effective Basic logs plan on selected tables - We've identified ingestion of more than 1 GB per month to tables that are eligible for the low cost Basic log data plan. The Basic log plan gives you search capabilities for debugging and troubleshooting at a lower cost.</li><li>Consider changing pricing tier- Based on your current usage volume, investigate changing your pricing (Commitment) tier to receive a discount and reduce costs.</li><li>Consider removing unused restored tables - You have one or more tables with restored data active in your workspace. If you're no longer using a restored data, delete the table to avoid unnecessary charges.</li><li>Data ingestion anomaly was detected - We've identified a much higher ingestion rate over the past week, based on your ingestion in the three previous weeks. Take note of this change and the expected change in your costs.</ul></li>You can also view automatically generated recommendation by selecting **Overview** > **Recommendations** or **Advisor recommendations** from your Log Analytics workspace resource menu.|
3535

0 commit comments

Comments
 (0)