You can export the following data as a CSV file:

  • Messages from the Message List view
  • Messages from the System State List view
  • Events from the Event list view
  • Log data from Operator Log view
  • Data points from the Field Elements view

Only the currently visible content is exported, which depends on the current filter used and the user privileges. The sorting of messages in the Message List view may be affected by the sort sequence configured for disciplines. Submessages must be visible in the message list so that they can be exported. By disabling the Siveillance Control mode button, you can export all messages. Keep in mind that you cannot reimport the CSV file into Siveillance Control.

The CSV export serves the following purposes:

  • The file proves that your configured system is functioning. Your test data must include all message types that occur. Proof relates, for example, to the full complement of messages received.
  • The file serves as backup file for completed messages and events for documentation purposes before deleting them.
  • Keep in mind, that you cannot reimport the file.

Exporting Data in a CSV File

  1. For exporting messages or events, open the Events/Messages perspective.
  1. For exporting log data, open the Operator Log perspective.
  1. For exporting field elements, open the Engineering perspective.
  1. In the respective view, set a filter to display all data that you want to export.
  1. Click .
  1. Select Export into CSV file from the drop-down list.
  1. In the Target file name, specify the target directory and file name and click Finish.

Export of the Operator Log

The CSV export of the Operator Log is repeated continuously by the log mechanism of the system. The log entries are logged in the CsvOperatorLogger category and can be diverted to a separate file in accordance with the configuration. Moreover, the system can be configured such that a new file is created every day to which only the entries of the day are written. Thus the export can be transferred on a daily basis.

Sample configuration

The log entries are written to a separate file called operatorlog.csv in the configuration below. A new file is created for each day. The old files are retained for 30 days.

<appender name="operatorlog-csv" class="ch.qos.logback.core.rolling.RollingFileAppender"> <file>/var/log/viewpoint/operatorlog.csv</file> <rollingPolicy class="ch.qos.logback.core.rolling.FixedWindowRollingPolicy"> <fileNamePattern>/var/log/viewpoint/</fileNamePattern> <minIndex>1</minIndex> <maxIndex>10</maxIndex> </rollingPolicy> <triggeringPolicy class="ch.qos.logback.core.rolling.SizeBasedTriggeringPolicy"> <maxFileSize>10MB</maxFileSize> </triggeringPolicy> <encoder> <pattern>%msg%n</pattern> </encoder> </appender>

<appender name="OPERATORLOGCSV"

The configuration file logback.xml is available in the /etc/viewpoint directory and can be adapted. The logbook allows the user to get a quick overview of past events and system states using comprehensive filter options.