The documentation you are viewing is for Dapr v0.11 which is an older version of Dapr. For up-to-date documentation, see the latest version.
Azure Event Hubs binding spec
Detailed documentation on the Azure Event Hubs binding component
See this for instructions on how to set up an Event Hub.
Setup Dapr component
apiVersion: dapr.io/v1alpha1 kind: Component metadata: name: <NAME> namespace: <NAMESPACE> spec: type: bindings.azure.eventhubs version: v1 metadata: - name: connectionString # Azure EventHubs connection string value: "Endpoint=sb://****" - name: consumerGroup # EventHubs consumer group value: "group1" - name: storageAccountName # Azure Storage Account Name value: "accountName" - name: storageAccountKey # Azure Storage Account Key value: "accountKey" - name: storageContainerName # Azure Storage Container Name value: "containerName" - name: partitionID # (Optional) PartitionID to send and receive events value: 0
connectionStringis the EventHubs connection string. Note that this is the EventHub itself and not the EventHubs namespace. Make sure to use the child EventHub shared access policy connection string.
consumerGroupis the name of an EventHubs Consumer Group to listen on.
storageAccountNameIs the name of the account of the Azure Storage account to persist checkpoints data on.
storageAccountKeyIs the account key for the Azure Storage account to persist checkpoints data on.
storageContainerNameIs the name of the container in the Azure Storage account to persist checkpoints data on.
partitionID(Optional) ID of the partition to send and receive events.
WarningThe above example uses secrets as plain strings. It is recommended to use a secret store for the secrets as described here.
Output Binding Supported Operations
- Bindings building block
- How-To: Trigger application with input binding
- How-To: Use bindings to interface with external resources
- Bindings API reference
Last modified April 2, 2021: Merge pull request #1368 from dapr/version-banner-v0.11 (affdf47)