Azure Blob Storage Archive Outputs and Integrations

George Alpizar
George Alpizar
  • Updated

Azure Blob Storage

This output type sends logs to an Azure Blob Storage endpoint.

Note

In the Edge Delta App, when you create an integration or an individual output, similar parameters will display. As a result, this document applies to both outputs and integrations.

Before you begin

Before you can create an output, you must have an account key.


Review Parameters

Review the following parameters that you can configure in the Edge Delta App:

Visual Editor YAML Description
Name name

Enter a descriptive name for the output or integration.

For outputs, this name will be used to map this destination to a workflow.

This parameter is required. 

Review the following example: 

name: my-blob
Integration integration_name

This parameter only appears when you create an individual output.

This parameter refers to the organization-level integration created in the Integrations page. If you enter this name, then the rest of the fields will be automatically populated.

If you need to add multiple instances of the same integration into the config, then you can add a custom name to each instance via the name field. In this situation, the name should be used to refer to the specific instance of the destination in the workflows.

This parameter is optional. 

Review the following example: 

integration_name: blob_acct
Not applicable type

Enter blob.

This parameter is required. 

Review the following example: 

type: blob
Account Name account_name

Enter the account name for the Azure account.

This parameter is required. 

Review the following example: 

account_name: '{{ Env "BLOB_ACCOUNT_NAME" }}'
Account Key account_key

Enter the account key for Azure account.

This parameter is required. 

Review the following example: 

account_key: '{{ Env "BLOB_ACCOUNT_KEY" }}
Container container

Enter the container name to upload.

This parameter is required. 

Review the following example: 

container: testcontainer
Not applicable auto_create_container

Create the container on the service, with no metadata and no public access.

This parameter is optional. 

Review the following example: 

auto_create_container: false
Compression compress

Enter a compression type for archiving purposes. 

You can enter gzip, zstd, snappy, or uncompressed

This parameter is optional. 

Review the following example: 

compress: gzip
Encoding  encoding

Enter an encoding type for archiving purposes. 

You can enter json or parquet

This parameter is optional. 

Review the following example: 

encoding: parquet 
Use Native Compression use_native_compression

Enter true or false to compress parquet-encoded data.

This option will not compress metadata. 

This option can be useful with big data cloud applications, such as AWS Athena and Google BigQuery.

Note

To use this parameter, you must set the encoding parameter to parquet

This parameter is optional.

Review the following example: 

use_native_compression: true
Buffer TTL  buffer_ttl

Enter a length of time to retry failed streaming data.

After this length of time is reached, the failed streaming data will no longer be tried.

This parameter is optional. 

Review the following example: 

buffer_ttl: 2h

Buffer Path 

buffer_path

Enter a folder path to temporarily store failed streaming data.

The failed streaming data will be retried until the data reaches its destinations or until the Buffer TTL value is reached.

If you enter a path that does not exist, then the agent will create directories, as needed.

This parameter is optional.

Review the following example:

buffer_path: /var/log/edgedelta/pushbuffer/
Buffer Max Size 
buffer_max_bytesize

Enter the maximum size of failed streaming data that you want to retry.

If the failed streaming data is larger than this size, then the failed streaming data will not be retried.

This parameter is optional.

Review the following example:

buffer_max_bytesize: 100MB

Review Sample Configuration

The following sample configuration displays an output without the name of the organization-level integration:

    - name: my-blob
      type: blob
      account_name: {{ Env "BLOB_ACCOUNT_NAME" }}
      account_key: {{ Env "BLOB_ACCOUNT_KEY" }}
      container: testcontainer
      auto_create_container: false

 

Share this document