Eventhub Publisher

The EventHub Publisher component sends event data to Azure Event Hubs, leveraging its scalability and throughput capabilities to ensure efficient and reliable transmission.

This component is typically used to:

• Publish streaming data from pipelines into Event Hubs.

• Enable downstream consumers (analytics engines, dashboards, microservices) to subscribe to the published events.

• Integrate real-time applications with Azure’s event-driven architecture.

Configuration Sections

All component configurations are classified into the following sections:

• Basic Information

• Meta Information

• Resource Configuration

Basic Information Tab

The Basic Information tab defines execution and deployment settings.

Field	Description	Required
Invocation Type	Select execution mode: Batch or Real-Time.	Yes
Deployment Type	Displays the deployment type of the component (pre-selected).	Yes
Container Image Version	Displays the Docker image version used (pre-selected).	Yes
Failover Event	Select a failover event to handle retries or errors.	Optional
Batch Size	Maximum number of records processed in one execution cycle (minimum: 10).	Yes

Meta Information Tab

The Meta Information tab configures EventHub connection and authentication details. The component supports two authentication methods:

Method 1: Publish Using Connection String

Field	Description	Required
Connection String	Full connection string for establishing a connection to the Event Hub.	Yes
Consumer Group	Logical grouping of event consumers that will read events from the same partition.	Yes
EventHub Name	The name of the Event Hub within the namespace where events will be published.	Yes
Checkpoint Location	The location in the stream that represents the last successfully processed event.	Optional
Enqueued Time	Timestamp when the event was added to the partition. Typically represents the event’s occurrence or generation time.	Optional
Publisher Namespace	Logical namespace grouping publishers and managing access control for Event Hubs.	Yes

Method 2: Publish Using Principal Secret

Field	Description	Required
Client ID	Azure AD application ID registered in the Azure portal (App Registrations).	Yes
Tenant ID	ID of the Azure AD tenant containing the application/service principal.	Yes
Client Secret	Secret associated with the Azure AD application for authentication.	Yes
Consumer Group	Logical grouping of event publishers that write to the same partition.	Yes
EventHub Name	The name of the Event Hub within the namespace where events will be published.	Yes
Checkpoint Location	The location in the stream representing the last successfully processed event.	Optional
Enqueued Time	Timestamp when the event was added to the partition.	Optional
Publisher Namespace	Logical namespace grouping publishers and managing access control.	Yes

Saving the Configuration

1. Choose Connection String or Principal Secret authentication.

2. Enter the required fields in the Meta Information tab.

3. Save the component configuration (Storage icon).

4. Activate the pipeline.

5. Events flowing into the publisher are sent to the configured Event Hub.

Example Workflow

1. Configure EventHub Publisher with:

   • Method: Principal Secret

   • Client ID / Tenant ID / Client Secret: Values from Azure AD App Registration

   • EventHub Name: sales-events

   • Publisher Namespace: company-namespace

2. Connect an input event (e.g., processed transactions from Kafka Consumer).

3. Activate the pipeline.

4. Events are published to Event Hub, where downstream analytics tools consume them for real-time reporting.