Event Hubs Clients

The connector for Azure Event Hubs functions as one or more Event Hubs client(s). Each client may have different configuration settings.

Add Event Hubs Client

To add a client, select the “Clients” navigation node and press the “Add” toolbar button. This will add a new Event Hubs client with default configuration settings. Rename the client to suit.

Client Settings

After selecting the client’s “Configuration” node, edit the client settings as required.

Client settings for Azure Identity

Client settings for Shared Access Signature

• Name

  Choose any name.

• Authentication

  Select either “Azure Identity” if the system running Dataristix is configured with a default Azure Identity (for example, in an Azure Kubernetes cluster), or select “Shared Access Signature”.

  Azure Identity Authentication

  The first image above shows example settings for Azure Identity authentication. Configure settings as follows:

  • Event Hubs Host Name

    Enter the host name as shown in your Azure portal’s overview for your Event Hubs namespace .

  • Storage Blob Endpoint

    If messages are to be consumed (not only produced) then a storage location is required and a storage Blob endpoint needs to be configured. Enter the endpoint address as shown in your Azure portal’s storage account settings.

  Shared Access Signature Authentication

  The second image above shows example settings for Shared Access Signature authentication. Configure settings as follows:

  • Event Hubs Connection String

    Enter the connection string as shown for your Event Hub’s “Shared access policies” access key in your Azure portal. Create an access key if none exists.

  • Storage Blob Connection String

    If messages are to be consumed (not only produced) then a storage location is required and a storage Blob connection string needs to be configured. You can generate the “SAS and connection string” for your checkpoint storage account under “Security + networking”, “Shared access signature”. Remember to check the “Allowed resource types” options.

• Storage Container

  If messages are to be consumed then enter the storage blob container where Event Hub checkpoints may be stored.

• Tag browsing consumer group Identity

  If you plan browsing for tags using the Dataristix tag browser, then enter an existing consumer group ID that may be used for tag browsing. This should be a dedicated consumer group not being used elsewhere to avoid interference with message processing elsewhere.

• Test Event Hub Name

  Enter an existing event hub name for connection testing.

After configuring the above you can try to establish a connection to the cluster by pressing the “Test Connection” button.

Remove Event Hubs Client

Select the “Clients” navigation node and a Event Hubs client from the list on the right, then press the “Remove” toolbar button to remove the selected client. You can also right-click on a Event Hubs client and select “Remove” from the context menu.

Warning

Note that all topics configured for the Event Hubs client will be also be removed. This affects all tasks using these topics.