CSV collector

The collector settings are used by the collector to successfully parse CSV files.

Description: The delimiter of the csv file. Required: yes

Description: Indicates if the csv files contain a header or not. If a header is present, the header record will be skipped when parsing the csv file. Required: yes

Description: Index of column holding the timestamp (starts from 0) Required: yes

Description: The layout of the timestamp of the measurements, default RFC3339 will be used. More info: https://pkg.go.dev/time#Layout Required: no

Description: Index of column holding the status (starts from 0) Required: no

Description: The string to trim (leading and trailing) from the csv cells used (values, mappings, status, …) Required: no

Description: Base directory, upon which the default incoming, processed and error directory are constructed. Required: yes Example: c:\plantdata\

Description: Override for the directory that needs to be monitored by the CSV collector. Required: no Example: c:\plantdata\incoming

Description: Override for the directory in which processed files will be put. Processed files are files which had at least one measurement sent to Influx. Required: no Example: c:\plantdata\processed

Processed files are files which had at least one measurement sent to Influx.

Description: Override for the directory in which files that contained an error will be put. Invalid CSV files will be stored here. Required: no Example: c:\plantdata\failed

Description: File mask of the files to use. Required: yes

The file mask for which the collector will monitor files.

Description: Delay in milliseconds for processing new files after the were detected Required: no Default: 10000

Description: Delay in milliseconds for processing new files after the were detected Required: no Default: 3000

Description: Initial delay for checking the incoming directory in milliseconds Required: no Default: 9000

Description: The maximum time in minutes to keep processed files. 0 will keep the files indefinitely Required: no Default: 43200

Description: The maximum time in minutes to keep failed files. 0 will keep the files indefinitely Required: no Default: 129600

Description: The timezone for the data points coming from the source device can be overwritten using this setting. Available timezones can be found here: https://en.wikipedia.org/wiki/List_of_tz_database_time_zones Required: no

The Measurement Settings section configures how CSV data is interpreted and mapped into measurements. This includes defining how each column in the CSV file is used, setting up filters for data inclusion, and specifying data quality indicators.

Description: Column of the value in the csv file for this measurement. Required: yes Example: 6

Description: Filter to parse only the rows that match the filter. The filter is a JSON object where the key is the column index (as a string) and the value is the value to match. If multiple values in the same column should be matched, separate them with a semicolon. Required: yes Details:

Example: In the following example, the filter will only parse rows where the value of the first column is Example value or the value of the second column is match with this or also match with this.

Description: All values that are mapped to status ‘Good’. Multiple statuses can be configured using semicolon separated values. Required: no Example: “Valid;correct”

Checkout the data collection methods section for more information.

Description: The layout of the timestamp, defaults to the TimestampLayout setting on the collector. More info: https://pkg.go.dev/time#Layout Required: no

Description:This allows to add tags to the measurement with the tag value coming from csv data. The structure of this setting is similar as the Filter setting. The json key is the column index (as string) where the tag value is present, and the json value is the tag key (or tag name) under which the data should be stored upon the measurement: Required: no Example: {"4": "Description"}

This example demonstrates setting up a collector and measurement for a CSV with multiple sensor data.

Given the following CSV format, with files being provided by a data source located in Europe/Brussels.

The CSV collector can create points for multiple measurements at the same record (optionally originating from different value columns). Measurements on the csv collector, are required to have a value column index using ValueColumn and can optionally have a mapping for a name or multiple names in the csv record using Filter.

When no name in the csv is available for the measurement, the measurement can be saved with Filter: {}

When there is a name or there are multiple names available in the csv (in different columns) which should match for this measurement, then the measurement can be saved with Filter: {"column index": "name in csv in that column"} or {"column index": "name in csv in that column", "column index": "name in csv in that column"}

For multiple mappings in Filter, all mappings should be valid for the record to create a point for the measurement!

For one mapping, multiple possible names can be given by separating the names with a semicolon: {"column index": "name1;name2", "column index": "name in csv in that column"}

Make sure to set the according collector settingscollector settings , prior to adding measurements with the proper measurement settingsmeasurement settings.