Import log triggers: CSV-file structure

Activate Cloud Logging and set up a data source

This article assumes you've already activated Cloud Logging (or started the 30 day free trial) and have set up a data source (including variables). View our corresponding guides if you haven't yet.

The import function in the Cloud Logging configurator is, together with the export function, built to easily and effortlessly copy log triggers from one device to another. Additionally, you can use the import function to prepare log triggers in a CSV file and load them all at once into your cloud logger.

This article explains the structure of the CSV file and the syntax of the corresponding settings. Despite the fact that every protocol is structured in it’s own way (i.e. Siemens S7 works with Data Blocks and OPC-UA doesn’t) a uniform file structure is applied for all protocols.

How to: export and import log triggers

View the "Configure log triggers"-guide on the left about the actual steps of exporting and importing a CSV file.

CSV file structure

The structure of the CSV file needs to be correct for the import function to work properly. The headers (first row) of column 1-5 should look like this:

Each column represents a different setting and these are all explained below. You can easily navigate to the desired section by pressing the corresponding header above.

Tip: an easy template

You can quickly and easily create a template by first creating a single log trigger using X4 Remote interface and then exporting this data trigger to a CSV file, or download an empty template here: CSV Template.

Identifier

This variable ensures that every data source and variable in the your company remains unique, even when you give multiple variables the same name. An identifier only has to be unique for a certain data-source. Two different data-sources in the same company can have the same identifiers and can therefore import the same CSV-file.

Name

You can name the log triggers freely. It is advised to enter a very brief description of the variable (i.e. error state, temperature too high, emergency stop zone B).

Address

Here you enter the address corresponding with the variable you’d like to use as log trigger. For example, when using Modbus and the variable is a holding register with address 7, you enter a 7 here. If you’re unsure you can best export an existing log trigger first.

Condition

A log trigger happens if the outcome of <variable><condition><threshold> is true. For example, if variable “Temperature” is “greater than or equal to” “60” degrees celsius.

The available options for the condition are:

Threshold

The threshold is the last part of the equation that determines if a log trigger happens or not. The available options depend on the variable’s data type. For example, if the variable’s data type is boolean, then you can choose either TRUE or FALSE.

Description

In addition to the log trigger name, you can add a full description of the log trigger here.