![]() This information helps you determine trends such as whether any increase is from overall data usage or usage by a particular solution. ![]() The Data ingestion per solution chart on the Usage and estimated costs page for each workspace shows the total volume of data sent and how much is being sent by each solution over the previous 31 days. Select Additional Queries for prebuilt queries that help you further understand your data patterns. You can determine if data collection steadily increased over time or suddenly increased in response to a configuration change. The tab also shows trending of data collection over time. This information can help you quickly identify the tables that contribute to the bulk of your data volume. See the Usage tab for a breakdown of ingestion by solution and table. Data tables that are ingesting the most data volume in the main table.Log Analytics Workspace Insights provides you with a quick understanding of the data in your workspace. If you need deeper analysis into your collected data than existing Azure Monitor features, use any of the following log queries in Log Analytics. These tools require no configuration and can often provide the information you need with minimal effort. Start your analysis with existing tools in Azure Monitor. Select or add an action group to notify you when the threshold is exceeded.īillable data volume greater than 50 GB in 24 hours. Usage | where IsBillable | summarize DataGB = sum(Quantity / 1000) You can also increase the frequency to check usage multiple times every day, but this option will result in a higher charge for the alert rule. Modify the Alert Logic setting to use a different threshold based on expected usage in your environment. The following example is a log alert rule that sends an alert if the billable data volume ingested in the last 24 hours was greater than 50 GB. Notification allows you to address any potential anomalies before the end of your billing period. To avoid unexpected bills, you should be proactively notified anytime you experience excessive usage. The rest of this article provides methods for detecting such a situation and then analyzing collected data to identify and mitigate the source of the increased usage. Volume of data collected from each monitored resource.Īn unexpected increase in any of these factors can result in increased charges for data retention.Number and type of monitored resources.Set of insights and services enabled and their configuration. ![]() The amount of data ingestion can be considerable, depending on the: Causes for higher-than-expected usageĮach Log Analytics workspace is charged as a separate service and contributes to the bill for your Azure subscription. For strategies to reduce your Azure Monitor costs, see Cost optimization and Azure Monitor.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |