Create a remote Influx database

TIP: Remote Influx database does not support InfluxDB cloud.
  1. In
    Project view
    , right-click
    DataStores
     and select
    Remote InfluxDB database
    .
  2. In
    Properties
    , complete:
    • Properties
      :
      • Server
        . IP address or hostname of the database server.
      • TCP Port
        . TCP port of the database server.
        TIP: The default value for InfluxDB servers is typically 8086.
      • Organization
        . Organization must match the one specified on the database server.
      • Bucket
        . Bucket must match the one specified on the database server.
      • Token
        . Token must match the one specified for fetching data from the database server.
      • Use SSL
        . For secure data connection, set to
        True
        .
      • Server Certificate
        . Server certificate must match the one specified on the database server for secure SSL connection.
    • Store and Forward
      :
      TIP: Store and Forward stores data in case of temporary connection loss to storage.
      Store and Forward is only available for external Influx databases. See Store and Forward.
      • SF Enabled
        .  Enables or disables Store and Forward.
      • SF Buffer Max Size
        . Maximum number of elements in the buffer, which can be set from 1 to 100000. An element is one entry (row) in a database table.
        TIP: The following diagnostic, read-only properties are available:

          SF Buffer usage
          . A diagnostics value set by runtime, indicating the current number of elements in the buffer.

          SF Buffer overflow
          . A diagnostics value set by runtime. False - indicates currently upcoming data is handled

    TIP:
    InfluxDB datastore has additional property for each table created to assign InfluxDB tags to dataset. InfluxDB tags are used by Influx database to identify and label datapoints for further analysis. It is also the way to log datapoints with the same timestamp to the same bucket and measurement, and avoid loss of data.
    For example: Without tags defined, when many events are triggered at the same time (with the same timestamp), InfluxDB overwrites them and only one record is logged in the database. To avoid this, you can bind the property to a unique property of a logged event (such as ). This forces the InfluxDB server to record all datapoints with the same timestamp. You may use the property to add any variable as a label for datapoints, for maintaining and analyzing data stored on server.
(optional) Configure the database structure. See Configure a database table.
Provide Feedback
Have questions or feedback about this documentation? Please submit your feedback here.