AzureBlobStorageProvider Section
The "AzureBlobStorageProvider" section provides configuration for the Azure Blob Storage provider, used for storing over‑threshold size blob and slob data in Azure Blob Storage.
"AzureBlobStorageProvider" : {
"Endpoint" : "https://<storage‑account‑name>.blob.core.windows.net",
"ContainerName" : "<container‑name>",
"StagingDirectory" : "<staging-root-directory>",
"BlobPrefix" : "<optional-prefix>",
"Authentication" : {
"Type : "ConnectionString",
"ConnectionString" : "DefaultEndpointsProtocol=https;
AccountName=<storage-account-name>;
AccountKey=<account-key>;
EndpointSuffix=core.windows.net"}
}
The parameters are listed in the following table.
| Parameter | Required? | Description |
|---|---|---|
| Endpoint | Yes |
URL endpoint of the Azure Blob Storage service for your account, which is typically in the format https://<storage‑account‑name>.blob.core.windows.net. (Not required if the Authentication type is "ConnectionString".) |
| ContainerName | Yes | Name of the blob container within your storage account. |
| StagingDirectory | Yes |
Staging directory where blob and slob files are stored before they are uploaded to Azure Blob Storage. A directory hierarchy similar to that used by the FileStorageProvider is created under the specified StagingDirectory. Staged capture files are removed after they have been uploaded to Azure Blob Storage. This unique directory name cannot be shared if multiple JadeEventProducer.exe applications are run. As the temporary directories created to house the blob files are not cleaned up by the application, you need to maintain them yourself at this stage. |
| BlobPrefix | No | Optional prefix added to all blob directory names; for example, "events". |
| Authentication | Yes |
The BlobStorageProvider section Authentication parameter Type can be one of the following.
For details, see "Type‑Specific Parameters", later in this chapter. |
For Azure-related configurations, use the Azure Portal or Azure Command Line Interface (CLI).
