Alooma can read and replicate all of the data in files from Azure Blob Storage or from Microsoft Application Insights.
If you are importing data from Microsoft Application Insights, start by setting up Continuous Export from Application Insights to an Azure Blob Storage.
Files in your Azure Blob Storage can be packaged and compressed using Tar or GZip, and can contain a variety of different file formats.
Add your Azure input from Alooma's plumbing screen.
Give your input a name. The name will appear in the plumbing screen, and will name the events that the input emits.
Provide the following access info:
Azure Account Name (the DNS prefix you created - e.g. for mystorage.blob.core.windows.net the name would be mystorage)
Azure Account Key (In the Azure portal, navigate to your storage account, click All settings and then click Access keys. The key is 88 base64 characters)
Container Name (between 3 and 63 lowercase characters)
File prefix (optional - the prefix of the files you'd like to upload, for instance
mydir/sys_log). If a prefix is entered, the other files are ignored.
Define which files to import:
All files will pull all the data from your container (for a given prefix, if defined above), and will continue to do so forever.
A date span pulls files written between the given dates, inclusive. If you select the date span option and don't specify dates, the input will only pull files written after the input was created.
Define the format of the files in your Azure Blob Storage from the list of our available file formats.
Keep the mapping mode to the default of OneClick if you'd like Alooma to automatically map the Azure events directly to your target data warehouse. Otherwise, they'll have to be mapped manually from the Mapper screen.
That's it! You're ready to pull data from your Azure Blob Storage with Alooma!