Consume a message in real-time from a Azure Event Hubs and create one execution per message.
If you would like to consume multiple messages processed within a given time frame and process them in batch, you can use the io.kestra.plugin.azure.eventhubs.Trigger instead.
type: "io.kestra.plugin.azure.eventhubs.RealtimeTrigger"Trigger flow based on events received from Azure Event Hubs in real-time.
id: azure_eventhubs_realtime_trigger
namespace: company.team
tasks:
- id: log
type: io.kestra.plugin.core.log.Log
message: Hello there! I received {{ trigger.body }} from Azure EventHubs!
triggers:
- id: read_from_eventhub
type: io.kestra.plugin.azure.eventhubs.RealtimeTrigger
eventHubName: my_eventhub
namespace: my_eventhub_namespace
connectionString: "{{ secret('EVENTHUBS_CONNECTION') }}"
bodyDeserializer: JSON
consumerGroup: "$Default"
checkpointStoreProperties:
containerName: kestra
connectionString: "{{ secret('BLOB_CONNECTION') }}"
The event hub to read from.
Namespace name of the event hub to connect to.
The Deserializer to be used for serializing the event value.
The config properties to be passed to the Deserializer.
Configs in key/value pairs.
The config properties to be used for configuring the BlobCheckpointStore.
Azure Event Hubs Checkpoint Store can be used for storing checkpoints while processing events from Azure Event Hubs.
Connection string of the Storage Account.
The consumer group.
Custom endpoint address when connecting to the Event Hubs service.
The ISO Datetime to be used when PartitionStartingPosition is configured to INSTANT.
Configs in key/value pairs.
The starting position.
The SAS token to use for authenticating requests.
This string should only be the query parameters (with or without a leading '?') and not a full URL.
List of execution states after which a trigger should be stopped (a.k.a. disabled).