Is the Splunk Addon for Microsoft Azure compatible with China Azure?

[rcao_splunk]

A China Azure customer wants to pull data out with Splunk Addon for Microsoft Azure from China Azure, but always failed. There is a log in the _internal log:

…ERROR ExecProcessor - message from ""C:\Program Files\Splunk\etc\apps\SplunkAzure\bin\SplunkAzure.exe"" An error occurred while processing this request.

I am sure the Azure account and key are right because I can query tables successfully via Azure Storage Explorer for China (http://shaunstorage.blob.core.chinacloudapi.cn/share/AzureStorageExplorerCN.zip ), yes, there is another edition for Global Azure (http://azurestorageexplorer.codeplex.com/ ). I guess the Azure addon might use the Global Azure’s codes, so I would like to confirm this app is only compatible with Global Azure or both?

Thanks a lot.

[rarsan_splunk]

The old Windows-only add-on referenced in original question has been pulled down. Take a look at the new cross-platform Splunk Add-on for Microsoft Azure which pulls data from Azure Storage API using Azure Storage Python SDK.

Among others, the Add-on leverages TableService and BlockBlobService which use core.windows.net endpoint for Azure cloud. You'll need to set endpoint_suffix to core.chinacloudapi.cn endpoint to access Azure China cloud instead.

[mholme59]

From my experience, this plugin does not currently support Azure China. I've coded an application of my own that targets Azure storage - the same API can be used for both Global Azure and China Azure. However, there is one value you need to change.

Example working with Blobs from the Azure Python SDK, should be quite similar for Table Storage:

Global Azure: blob_service = BlobService(account_name="my storage account", account_key="my account key", host_base=".blob.core.windows.net")
Azure China: blob_service = BlobService(account_name="my storage account", account_key="my account key", host_base=".blob.core.chinacloudapi.cn")

This plugin no longer seems to be under active development. However, this would be a very easy item to make configurable if the developer were to pick it back up.