A unique text string used to identify this connection. This label is used to identify the connection when configuring store and forward, and to create the database name or retention policy in some historians. The label can contain only letters, numbers and the underscore ( _ ) character.

The namespace of the Azure Event Hub. This namespace can contain multiple different Event Hubs. Confirm that it is the Namespace being typed into this text box, not the name of the Event Hub itself. If you are using your own Event Hub, go to https://portal.azure.com/#home. Then click Event Hubs, under Azure Services and create an Event Hub.

The name of the Event Hub that will be written to. After clicking into the Namespace, there is the option to create a new Event Hub. The name of that Event Hub can be provided into this text entry field.

the connection string used to connect to and authenticate the Event Hub connection. This can be found in the Event Hubs Namespace page, under Shared Access Policies.

Create a new policy key, giving it all of Manage, Send and Listen options.

After this policy key is created, clicking that policy key will open a dialog on the side with many different keys. Copy the key called Connection String – Primary Key. This will be what you enter into the Namespace text entry field to gain access to the specified Event Hub within this Namespace.

Enter a specific Partition ID if you would like to write to a specific partition only. If you would like to write to all partitions, leave the Partition ID blank. If you would like to write to multiple specific partitions, create an Azure Event Hubs connection for each partition.

The amount of producers wanted to send items to Azure Event Hubs. The default is 1. This ensures that the messages that are sent maintain time order. If using more than one producer, the throughput increases, but time order of messages is lost.

The amount of times to split a message batch. For example, if there are 10,000 points, a message split of 5 would split the message into 5 messages of 2000 points each. This is useful to match with the producer count to increase throughput.

The number of milliseconds that the DataHub instance will buffer data in memory before sending it to Event Hubs. Setting this value to zero means that no accumulation time will be enforced.

If both this value and Maximum # of buffered values (below) are specified, then the DataHub instance will write all buffered values to Kinesis whenever the first of these two limits is reached.

The maximum number of values that the DataHub instance will buffer in memory before transmitting them to Event Hubs. Setting this value to zero means that all values will be sent as soon as possible.

Checking this option causes messages regarding successful writes to the database to be logged at the Information level in the DataHub Event Log. If this is not checked then these messages are logged at the Debug level and are therefore normally hidden from the user.