Azure Event Hub Integration Guide

review the following guide for setting up an integration between belden horizon data operations and https //docs microsoft com/en us/azure/event hubs/event hubs about the azure even hub connector is based on the https //github com/azure/azure event hubs go before you begin make sure you have an azure account step 1 add a device follow the steps to docid\ t cwpe0 jsfw5 aoj8wpp the device will be used to store tags that will be eventually used to create outbound topics in the connector make sure to select the enable data store check box step 2 add tags after connecting the device in belden horizon data operations, you can docid\ wpe2hmxelarlbnhwbuchy to the device create tags that you want to use to create outbound topics for the connector step 3 add the azure event hubs connector follow the steps to docid\ orxib vla2ngvdx94z1ow and select the azure event hubs provider configure the following parameters name enter a name for the connector connection string copy the string from your azure sas policy and paste it here maximum message size the maximum message size in kb the default value is 256 parallel connections count the maximum number of parallel connections from your edge device to azure event hub the default value is 50 combine messages select the check box to combine messages (thus reducing the number of parallel connections) throttling limit the maximum number of messages per second to be processed the default value is zero, which means that there is no limit persistent storage when enabled, this will cause messages to undergo a store and forward procedure messages will be stored within belden horizon data operations when cloud providers are online note ensure that you enter the connection string for the event hub entity and not the namespace using the wrong connection string will result in connection failures additionally, verify that the send and listen claims are enabled for the sas policy the connection string format should look like this endpoint=sb //\<your event hub name> servicebus windows net/;sharedaccesskeyname=\<your policy name>;sharedaccesskey=\<your access key>;entitypath=\<your entity name> step 4 enable the connector after adding the connector, click the toggle in the connector tile to enable it if you see a failed status, review the docid\ ocbqwycy xmmkwv9aunq and any relevant error messages step 5 create outbound topics for connector you will now need to create outbound topics for the connector from the tags created in step 2 to create outbound topics click the connector tile the connector dashboard appears click the topics tab click the import from devicehub tags icon the devicehub import dialog box appears select all the tags to import and click import after importing the tag(s), do the following edit the tag and configure the remote data topic copy and paste the name of your azure event hub click the enable toggle to enable the topic make sure the connector has a connected status step 6 verify connection in azure to verify the connection in azure open the azure portal open the event hub you have connected to and see statistics on the messages it receives from the belden horizon data operations outbound topic navigate to process data > explore to see the messages in a tabular form