Skip to main content
Ent+
This feature is available as an add-on for the Honeycomb Enterprise plan. Please contact your Honeycomb account team for details.

​
Prerequisites

Setup an Event Hub to listen for Blob Create events. More information on how to set this up can be found in the Azure documentation here.

​
Blob Format

Stored logs and traces must be in OTLP JSON format in order to be correctly parsed by the receiver.

​
Supported Platforms

PlatformMetricsLogsTraces
Linux✓✓
Windows✓✓
macOS✓✓

​
Configuration Table

ParameterTypeDefaultDescription
telemetry_typestelemetrySelector["Logs", "Traces"]Choose Telemetry Type.
connection_string*string""The connection string for the Azure Storage account. Information can be found here.
event_hub_endpoint*string""The Azure Event Hub endpoint triggering on the Blob Create events. Information can be found here.
logs_container*string”logs”Name of the Azure Storage container where logs are stored.
traces_container*string”traces”Name of the Azure Storage container where traces are stored
* required field

​
Example Configuration

​
Basic Configuration

For basic configuration only, the connection_string for Azure Storage and the event_hub_endpoint need to be supplied. In the example below, we are using a fake connection_string and event_hub_endpoint in the form Azure expects.

​
Web Interface

Honeycomb Docs - Azure Blob Storage - image 1

​
Standalone Source

YAML
apiVersion: bindplane.observiq.com/v1
kind: Source
metadata:
  id: azure_blob
  name: azure_blob
spec:
  type: azure_blob
  parameters:
    - name: connection_string
      value: 'DefaultEndpointsProtocol=https;AccountName=accountName;AccountKey=+idLkHYcL0MUWIKYHm2j4Q==;EndpointSuffix=core.windows.net'
    - name: event_hub_endpoint
      value: 'Endpoint=sb://oteldata.servicebus.windows.net/;SharedAccessKeyName=otelhubbpollicy;SharedAccessKey=mPJVubIK5dJ6mLfZo1ucsdkLysLSQ6N7kddvsIcmoEs=;EntityPath=otellhub'