Basic Settings
You can configure the following basic settings in OPC Router Management. You can open the settings dialog by clicking the “Options” button.
Runtime
| Property | Description |
|---|---|
| Connection Timeout | Time (in s) that the connection establishment may take before a connection error is returned. |
| System Metrics Update Interval (s) | Interval at which system data (CPU/RAM) is sent to the license portal. |
Flow Status Configuration
| Property | Description |
|---|---|
| Retention period for events | Time range during which the data is retained. You can select a retention period ranging from a minimum of one day to a maximum of one month. |
| Retention Period for Transferred Values | Time range during which the data is retained in the event of malfunctions. |
| Log Transferred Values | Enable this option if you want transferred values to be logged. |
| Maximum log size for events (GB) | Specify the maximum log size for events in GB. |
| Maximum number of characters in the status display | Limit the number of characters displayed for transferred values in the status view. This applies only to arrays and strings. |
Project Backups
For information on what constitutes a complete backup in addition to automatic project backups, and how to restore a backed-up state to production, see Backup and Recovery .
| Property | Description |
|---|---|
| Project Backup | Select when an automatic project backup should be performed. |
| Maximum number of retained project backups | Number of project backups to be retained. If this number is exceeded in the destination directory, the oldest project backup is automatically deleted. |
| Backup path | Destination directory where the project backup is saved. |
| Include authentication data in project backup | Use this option to include or exclude all passwords from connections (plug-ins) in a project. |
Log Output
| Property | Description |
|---|---|
| Log directory | Directory for storing log files (default: <OPC Router program directory>\LogDir). |
| Log all transfers | Writes all data transfers to the log file. Enabling this option takes precedence over log deactivation for individual flows. |
| Errors | Records errors. Recommended during normal operation. |
| Warnings | Records warnings. Recommended during normal operation. |
| Trace | Comprehensive logging of program operations. For troubleshooting. Should be disabled during normal operation. |
You can log program operations to varying degrees of detail. During normal operation, we recommend logging warnings and errors. The log file remains clear and organized, yet information is readily available in the event of an error. With <Ui>Trace</Ui>, you can log very detailed information. Enable <Ui>Trace</Ui> to identify the causes of errors. The log files are located in the directory specified above under “Log Directory”; in the Docker container, this is the mount path /var/log/opcrouter.
Every time an OPC Router process is started, it displays a message indicating its current version.
For information on where the files are located, how to download them without access to the server, and how the event log differs from the status display, see ": Log Files and Event Log" at .
Web Interface Language
You can switch the menu and dialog language of the management interface using the flag icon in the upper-left corner of the web interface. You can choose between German and English.
Reset Database to Factory Settings
This reset option is available only in Expert Mode. If Expert Mode is enabled, the “Expert Mode” section appears in the Options dialog box, along with the “Database Settings” button. Clicking this button opens another dialog box where you can select which databases should be cleared.
Emptying a database permanently deletes the affected data. There is no confirmation prompt for the deletion process, and there is no way to undo it. Export your project and back it up before proceeding.
The dialog is divided into four sections, each of which can be emptied separately:
| Section | Content |
|---|---|
| YAML files | Project configuration as files in the configuration store: flows, plug-ins, router settings, secrets, certificates, notification groups, and other storage locations. |
| Runtime Database | The same configuration data in the runtime database, plus manually triggered transfers. |
| Status Database | The recorded status data, i.e., events and transferred values. |
| Delete All | Resets all of the above areas together—restoring the system to its factory default state. |
Resetting the status database affects only the records and leaves the engineering unchanged. All other sections remove parts of the engineering itself.