The documentation you are viewing is for Dapr v1.9 which is an older version of Dapr. For up-to-date documentation, see the latest version.
Azure Event Hubs binding spec
Component format
To setup Azure Event Hubs binding create a component of type bindings.azure.eventhubs
. See this guide on how to create and apply a binding configuration.
See this for instructions on how to set up an Event Hub.
apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
name: <NAME>
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
Warning
The above example uses secrets as plain strings. It is recommended to use a secret store for the secrets as described here.Spec metadata fields
Field | Required | Binding support | Details | Example |
---|---|---|---|---|
connectionString | Y | Output | 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 | "Endpoint=sb://****" |
consumerGroup | Y | Output | The name of an EventHubs Consumer Group to listen on | "group1" |
storageAccountName | Y | Output | The name of the account of the Azure Storage account to persist checkpoints data on | "accountName" |
storageAccountKey | Y* | Output | The account key for the Azure Storage account to persist checkpoints data on. *Not required if using AAD authentication. | "accountKey" |
storageContainerName | Y | Output | The name of the container in the Azure Storage account to persist checkpoints data on | "containerName" |
partitionID | N | Output | ID of the partition to send and receive events | 0 |
eventHub | N | Output | The name of the EventHubs hub. Required if using AAD authentication. | eventHubsNamespace-hubName |
eventHubNamespace | N | Output | The name of the EventHubs namespace. Required if using AAD authentication. | eventHubsNamespace |
Azure Active Directory (AAD) authentication
The Azure Event Hubs pubsub component supports authentication using all Azure Active Directory mechanisms. For further information and the relevant component metadata fields to provide depending on the choice of AAD authentication mechanism, see the docs for authenticating to Azure.
Binding support
This component supports output binding with the following operations:
create
Input Binding to Azure IoT Hub Events
Azure IoT Hub provides an endpoint that is compatible with Event Hubs, so Dapr apps can create input bindings to read Azure IoT Hub events using the Event Hubs bindings component.
The device-to-cloud events created by Azure IoT Hub devices will contain additional IoT Hub System Properties, and the Azure Event Hubs binding for Dapr will return the following as part of the response metadata:
System Property Name | Description & Routing Query Keyword |
---|---|
iothub-connection-auth-generation-id |
The connectionDeviceGenerationId of the device that sent the message. See IoT Hub device identity properties. |
iothub-connection-auth-method |
The connectionAuthMethod used to authenticate the device that sent the message. |
iothub-connection-device-id |
The deviceId of the device that sent the message. See IoT Hub device identity properties. |
iothub-connection-module-id |
The moduleId of the device that sent the message. See IoT Hub device identity properties. |
iothub-enqueuedtime |
The enqueuedTime in RFC3339 format that the device-to-cloud message was received by IoT Hub. |
message-id |
The user-settable AMQP messageId. |
For example, the headers of a HTTP Read()
response would contain:
{
'user-agent': 'fasthttp',
'host': '127.0.0.1:3000',
'content-type': 'application/json',
'content-length': '120',
'iothub-connection-device-id': 'my-test-device',
'iothub-connection-auth-generation-id': '637618061680407492',
'iothub-connection-auth-method': '{"scope":"module","type":"sas","issuer":"iothub","acceptingIpFilterRule":null}',
'iothub-connection-module-id': 'my-test-module-a',
'iothub-enqueuedtime': '2021-07-13T22:08:09Z',
'message-id': 'my-custom-message-id',
'x-opt-sequence-number': '35',
'x-opt-enqueued-time': '2021-07-13T22:08:09Z',
'x-opt-offset': '21560',
'traceparent': '00-4655608164bc48b985b42d39865f3834-ed6cf3697c86e7bd-01'
}
Related links
- Basic schema for a Dapr component
- Bindings building block
- How-To: Trigger application with input binding
- How-To: Use bindings to interface with external resources
- Bindings API reference
Feedback
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.