InfluxDB v1.7.x SSL Integration Guide

review the following guide for setting up an integration between litmus edge and an influxdb database (version 1 7 or 1 8) using ssl authentication note the following data types and formats are not viewable in influxdb string char json payloads user scenario in this guide influxdb is installed through a docker image you have several other options for the installation see the following to learn more download influxdb oss install influxdb oss step 1 set up influxdb you will first need to pull an influxdb image file and then run it on your computer for this guide influxdb version 1 8 0 is pulled to set up influxdb on your computer, open the command prompt window run the following command docker run name influxdb p 8086 8086 influxdb 1 8 0 the command will create the influxdb container with the name "influxdb", on port 8086, and install influxdb version 1 8 0 once the influxdb container is running, refer to the following to learn more about setting up and configuring influxdb, and also enabling ssl authentication influxdb v1 documentation configure influxdb oss creating a database https //docs influxdata com/influxdb/v1/introduction/get started/#creating a database enable https with influxdb once you set up and configure influxdb to your specific requirements, you can complete the setup in litmus edge step 2 add 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 3 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 4 add the influxdb v1 7 x ssl connector follow the steps to add a connector docid\ ogw7fkqbwidbabn4wl5rr and select the db influxdb v1 7 x ssl provider configure the following parameters name enter a name for the connector influxdb address enter the influxdb database address and port in the following format http //\<influxdb address> \<port> influxdb database name enter the database name configured in the influxdb setup in step 1 username (optional) enter a username to access the database password (optional) enter the password associated with the username ca certificate paste or upload the ca certificate required to access influxdb certificate paste or upload the ssl certificate private key enter or paste the ssl private key insert batch size enter the number of messages to be collected as a batch before inserting into the database insert batch commit time the batch commit time in seconds 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 step 5 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 6 create topics for connector you will now need to import the tags you added in step 3 to the connector as topics 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 after adding all required topics, navigate to the integration overview page and ensure the connector is not disabled and still shows a connected status step 7 enable topics ensure the topics you imported are enabled by returning to the topics tab and clicking the enable all topics icon step 8 verify connection access the influxdb database to ensure that data is being sent successfully from litmus edge to the database