Azure Blob Rehydration

Prerequisites

Ensure you have access to an Azure Blob Storage account. Set up your Azure Blob Storage to store OTLP data in the required format for rehydration. More information on how to set this up can be found in the Azure documentation here.

Blob Format

Rehydrated data must be in OTLP format for correct processing. Ensure your data adheres to this format.

Supported Platforms

Platform	Supported
Linux	✓
Windows	✓
macOS	✓
Kubernetes Cluster*	✓

Available in the Bindplane Distro for OpenTelemetry Collector v1.69.0+.

Note: When deploying with a Kubernetes Cluster agent, select StatefulSet as the deployment method.

Configuration Fields

Field	Description
Connection String	The connection string for the Azure Blob Storage account.
Container	Name of the Azure Storage container from which to rehydrate data.
Batch Size	The number of blobs to download at once. This parameter directly impacts performance by controlling the number of concurrent blob downloads. If your host has a large number of cores, you can probably increase this value to increase rate of rehydration.
Page Size	The maximum number of blob information to return in a single API call.
Starting Time	UTC start time for rehydration.
Ending Time	UTC end time for rehydration.
Delete on Read	If true, blobs are deleted after rehydration.
Enable Storage	Enable to specify a storage extension for tracking rehydration progress.
Storage Directory	Directory for storing rehydration state, useful for maintaining state and resuming operations. (Only relevant if Enable Storage is true)

Example Configuration

Basic Configuration

This configuration sets up Azure Blob Rehydration with necessary details such as connection string, container, and time range for rehydration.

Adjust the Connection String, Container, Starting Time, and Ending Time to match your configuration.