Automating archiving Azure Monitor Data with KustoSolution ·
In our last article, we laid down a method on how to archive Azure Monitor Data using Kusto (Azure Data Explorer). This allows us to later analyse that data on a much longer period than the Azure Monitor retention period.
In this article, we will automate that archiving method using Azure Logic Apps.
As usual, the code is in GitHub.
Deploying the solution
The solution is available in the form of an ARM Template:
There are two parameters:
|Cluster Id||This should be the Azure Resource Id of the ADX cluster we are going to use:
|Db||The name of the database in the cluster where we are going to archive Azure Monitor data|
The ARM Template deploys two Logic App:
In order for the solution to work, the designated database must have been setup with tables & functions. See last article’s.
The kusto cluster must also be running (i.e. not be stopped).
Azure Logic App has a connector for Kusto. It works well.
It follows the connector convention of requiring a user authentication. This is typically done in the portal by opening the connection and clicking the authenticating button.
That means the current user is authenticated for the connection and basically the user does the cluster’s action.
We prefer having service principal to perform action on behalf of a system (e.g. a Logic App).
Also we had issue with the
.alter table statement…
For all those reasons, we authored a separate Logic App doing Kusto actions (either query or command) and leveraging the Kusto REST API and Logic App Managed Service Identity (MSI). Kusto REST API is really straight forward to use.
Since we were wrapping Kusto call in a different Logic App, we took the opportunity to tidy up the output. The REST API is quite verbose and requires at least one Logic App action to find the actual query result. So we do that work in the kusto-app. We also return the original REST API response.
The kusto-app has an identity. We can see that by choosing the Identity pane:
That identity must be given access on the Kusto database so it can perform queries and command on it.
In order to give access to Logic App, we’ll follow this procedure for the database we selected. We will select kusto-app as the principal and give it Database admin role. This the highest permission we can give, but it is required since we will do
.alter database to modify the merge policy.
We can open the archive app. We’ll notice it mimics pretty closely the process we laid out.
We listed Application Insights tables in the for-each-table action. Changing that list for Log Analytics would be the only change necessary to adapt the app for Log Analytics.
We automated the process of archiving Azure Monitor data with Kusto.
This could be run recurrently. In theory it could be run every 90 days to pickup data before the retention on Azure Monitor delete data.
In practice, large data fails on
.append. We noticed on Azure Application Insights for instance that the
PerformanceCounters table was failing with 90 days worth of data. We had to split the ingestion manually.
The ingestion could be split in the automated process, but an easier option is to perform the ingestion more often.