Have you ever been surprised by a larger-than-expected monthly Azure Data Lake Analytics bill? Creating alerts using Log Analytics will help you know when the bill is growing more than it should. In this post, I will show you how to create an alert that emails a message whenever the total AUs assigned to jobs exceeds a daily threshold. – it’s easy to get started!
This is another post in a series on how to save money and reduce costs with Azure Data Lake Analytics.
Connect your Azure Data Lake Analytics account to Log Analytics
Follow the steps in our previous blog post on Log Analytics to connect your accounts and start collecting usage and diagnostics logs – in this specific case, make sure you select the Audit logs to create this alert:
Create the query: Azure Data Lake Analytics AUs assigned
A simple Azure Log Analytics query showing the recently completed jobs is:
search * | where Type == "AzureDiagnostics" | where ResourceProvider == "MICROSOFT.DATALAKEANALYTICS" | where OperationName == "JobEnded
The attribute Parallelism_d in the previous query, contains the total number of AUs assigned by the user on a job that has ended (regardless of status). The following query aggregates the results on a 1-day interval and sums all the values of the Parallelism_d column, returning the total AUs assigned by users to jobs that ended. Note that this is not the total number of AU-hours (we will cover that on a later blog post).
We will use this query to power our Log Analytics alert:
search * | where Type == "AzureDiagnostics" | where ResourceProvider == "MICROSOFT.DATALAKEANALYTICS" | where OperationName == "JobEnded" | summarize AggregatedValue = sum(Parallelism_d) by bin(TimeGenerated, 1d)
Creating the Log Analytics alert
If you want to see the step-by-step guide to create a new Log Analytics alert, check out our recent blog post on creating Log Analytics Alerts.
For the alert signal logic, use the following values:
- Use the query from the previous step
- Set the sum of AUs to 50 as the threshold (you can use any number that reflects your own threshold)
- Set the trigger to 0: whenever the threshold is breached
- Set the period and frequency for 24 hours.
After one or more jobs exceed the AU threshold set in the alert within a 24 hour period, the users/teams in the alert action group will get an email alert:
In this blog post I showed you how to set up and alert whenever a specific threshold of AUs is exceeded. This usage alert can directly help to manage costs and understand the Data Lake Analytics usage in your organization - create your notifications and share your experiences with us!
In future posts, we'll cover other useful alerts and notifications that can be set up for your Azure Data Lake Analytics and Data Lake Store accounts. Go ahead and set your own usage alerts -- it's easy to get started!