Azure Event Hub Integration Guide

review the following guide for setting up an integration between litmus edge and azure event hub https //docs microsoft com/en us/azure/event hubs/event hubs about the azure event hub connector is based on the azure official sdk https //github com/azure/azure event hubs go before you begin you must have an azure account step 1 add a device follow the steps to connect a device docid 3eyafppweuvmblcey17sq 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 checkbox step 2 add tags after connecting the device in litmus edge, you can add tags docid 8se7z3pmrfwl1nmzcwalx 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 add a connector docid\ ogw7fkqbwidbabn4wl5rr and select the azure event hubs provider configure the following parameters name a recognizable name to identify 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 checkbox 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 litmus edge when cloud providers are online queue mode select the queue mode as lifo (last in first out) or fifo (first in first out) selecting lifo means that the last data entry is processed first, and selecting fifo means the first data entry is processed first 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, you can review the manage connectors docid 3u7jzldinehy8shvifd d and relevant error messages step 5 add 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 add tags icon the add subscription dropdown appears click the +add a new subscription in dropdown menu the create subsubscription dialog appears for publishing litmus edge data to aws sitewise asset measurement, define the following data direction = local to remote outbound local topic = any topic in litmus edge remote topic = asset measurement alias defined on the aws sitewise portal the measurement alias is a user defined string for each measurement can be found under the alias column description = description for the subscription optional field click ok to add the subscription 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 litmus edge outbound topic navigate to process data > explore to see the messages in a tabular form