azure eventhubs sink Azure Eventhubs Sink

Provided by: "Apache Software Foundation"

Support Level for this Kamelet is: "Stable"

Send events to Azure Event Hubs.

The Kamelet checks for the partition-id / ce-partition-id header which is an identifier of the Event Hub partition that the event will be sent to. If the identifier is not specified, the Event Hubs service will be responsible for routing events that are sent to an available partition. A header is optional. If the header is not set, the partition is assigned by Event Hubs.

There are two different mechanism of authentication CONNECTION_STRING and AZURE_IDENTITY, you could specify with credentialType property. If you’re using CONNECTION_STRING sharedAccessName and sharedAccessKey properties will be needed.

In case of AZURE_IDENTITY selection, the DefaultAzureCredential will attempt to authenticate via the following mechanisms in the following order enviroment, Workload Identity, Managed Identity, Azure Developer CLI, IntelliJ, Azure CLI and Azure Powershell.

Configuration Options

The following table summarizes the configuration options available for the azure-eventhubs-sink Kamelet:

Property Name Description Type Default Example

eventhubName

Eventhubs Name

Required The Event Hub name.

string

namespaceName

Eventhubs Namespace

Required The Event Hubs namespace.

string

credentialType

Credential Type

Determines the credential strategy to adopt.

Enum values:

* CONNECTION_STRING * AZURE_IDENTITY

string

CONNECTION_STRING

sharedAccessKey

Share Access Key

The key for the Event Hubs SAS key name.

string

sharedAccessName

Share Access Name

The Event Hubs SAS key name.

string

Dependencies

At runtime, the azure-eventhubs-sink Kamelet relies upon the presence of the following dependencies:

  • camel:core

  • camel:azure-eventhubs

  • camel:kamelet

Camel JBang usage

Prerequisites

  • You’ve installed JBang.

  • You have executed the following command:

jbang app install camel@apache/camel

Supposing you have a file named route.yaml with this content:

- route:
    from:
      uri: "kamelet:timer-source"
      parameters:
        period: 10000
        message: 'test'
      steps:
        - to:
            uri: "kamelet:log-sink"

You can now run it directly through the following command

camel run route.yaml

Camel K Environment Usage

This section describes how you can use the azure-eventhubs-sink.

Knative sink

You can use the azure-eventhubs-sink Kamelet as a Knative sink by binding it to a Knative object.

azure-eventhubs-sink-pipe.yaml
apiVersion: camel.apache.org/v1
kind: Pipe
metadata:
  name: azure-eventhubs-sink-pipe
spec:
  source:
    ref:
      kind: Channel
      apiVersion: messaging.knative.dev/v1
      name: mychannel
  sink:
    ref:
      kind: Kamelet
      apiVersion: camel.apache.org/v1
      name: azure-eventhubs-sink
    properties:
      eventhubName: The Eventhubs Name
      namespaceName: The Eventhubs Namespace

Prerequisite

You have Camel K installed on the cluster.

Procedure for using the cluster CLI

  1. Save the azure-eventhubs-sink-pipe.yaml file to your local drive, and then edit it as needed for your configuration.

  2. Run the sink by using the following command:

    kubectl apply -f azure-eventhubs-sink-pipe.yaml

Procedure for using the Kamel CLI

Configure and run the sink by using the following command:

kamel bind channel:mychannel -p "sink.eventhubName=The Eventhubs Name" -p "sink.namespaceName=The Eventhubs Namespace" azure-eventhubs-sink

This command creates the Kamelet Pipe in the current namespace on the cluster.

Kafka sink

You can use the azure-eventhubs-sink Kamelet as a Kafka sink by binding it to a Kafka topic.

azure-eventhubs-sink-pipe.yaml
apiVersion: camel.apache.org/v1
kind: Pipe
metadata:
  name: azure-eventhubs-sink-pipe
spec:
  source:
    ref:
      kind: KafkaTopic
      apiVersion: kafka.strimzi.io/v1beta1
      name: my-topic
  sink:
    ref:
      kind: Kamelet
      apiVersion: camel.apache.org/v1
      name: azure-eventhubs-sink
    properties:
      eventhubName: The Eventhubs Name
      namespaceName: The Eventhubs Namespace

Prerequisites

  • You’ve installed Strimzi.

  • You’ve created a topic named my-topic in the current namespace.

  • You have Camel K installed on the cluster.

Procedure for using the cluster CLI

  1. Save the azure-eventhubs-sink-pipe.yaml file to your local drive, and then edit it as needed for your configuration.

  2. Run the sink by using the following command:

    kubectl apply -f azure-eventhubs-sink-pipe.yaml

Procedure for using the Kamel CLI

Configure and run the sink by using the following command:

kamel bind kafka.strimzi.io/v1beta1:KafkaTopic:my-topic -p "sink.eventhubName=The Eventhubs Name" -p "sink.namespaceName=The Eventhubs Namespace" azure-eventhubs-sink

This command creates the Kamelet Pipe in the current namespace on the cluster.

Kamelet source file

https://github.com/apache/camel-kamelets/blob/main/kamelets/azure-eventhubs-sink.kamelet.yaml

Back to top