Transfer object
The following properties can be configured:
| Property | Description |
|---|---|
| InfluxDB 2.0/3.0 & Cloud | InfluxDB 2.0/3.0 & Cloud Plug-In Instance to be used |
| Measurement series | Dynamic: A static measurement series must be configured in the transfer object. This setting should be used if data is to be written to only one measurement series. |
| Timestamp source | InfluxDB: When receiving the data, the InfluxDB server uses its own server time (UTC) as the timestamp. If batched writing is active, this timestamp source should not be used. See: #selection-of-the-timestamp-source-for-batched-writing OPC Router (UTC): During transfer, the time is set by the OPC Router server in UTC as the timestamp. Dynamic: At runtime, you can pass your own timestamp. If possible, this will be converted to UTC. |
| Null handling | Error: The transfer is aborted with an error if a null value is encountered. Omit value: Zero values are not written to the database. If all fields are zero and no tags are defined, nothing is written to the database. Insert Discard: The value is discarded and nothing is written to the database. No error is triggered. Replace value: A zero value is replaced by a specified value. |
| Tag keys | Tags that are assigned to the written value. Tags help to filter and classify the data. In addition, different tags prevent identical values from being combined. |
| Field keys | Names for the fields in which the values are written at runtime, |
| Type | Data type of a field. |
| Default | Default value of a field. Note: This column is only available if "Discard" is selected for zero handling. |
Measurement series, tags, and fields that have not yet been used are automatically created by the InfluxDB server and do not need to be created beforehand.
Choosing the timestamp source for batched writing
InfluxDB should not be used as a timestamp source when transferring large amounts of data with batched writing, as this can lead to data loss. If InfluxDB is used as the timestamp source, the timestamps are only set when the data is received. Since batch inserts send a lot of data to the Influx database almost simultaneously, this can lead to an aggregation of values that are processed by InfluxDB in the same nanosecond. It is recommended to use OPC Router as the timestamp source or to set the timestamp yourself using the "dynamic" option.