This tab displays global logging settings for the platform. Here you can adjust central logging parameters while the system is running. Changes are applied immediately. All values are now stored in the database and persist across restarts.
Go to: Control Center > Logs > Log settings > General log settings.
Note for upgrades to LDP 26.3.0
On the first start after upgrading to LDP 26.3.0, any existing custom values from
./etc/startup.xmlare automatically migrated to the database. This migration runs once. Once you save a value in this tab, the corresponding entries in./etc/startup.xmlare obsolet. The XML file is not modified, and the old values it contains are not deleted.
Log files
Write logs to files as well: If this checkbox is selected, log entries are written to files in addition to the database.
XML parameter:
fileLogEnabled
General log storage period
Parameter | Parameter (startup.xml) | Default value | Description |
|---|---|---|---|
Duration until logs without job number are deleted |
| 30 days | Specifies the number of days after which log entries without an associated job number are automatically deleted. |
Job log retention period
NOTE
If MongoDB is enabled, the following three fields are not editable. MongoDB then handles the management of retention periods.
Parameter | Parameter (startup.xml) | Default value | Description |
|---|---|---|---|
Duration until logs are deleted |
| 30 days | Specifies the number of days after which job log entries are automatically deleted. This value can be overridden in profiles. |
Time until log statistics are deleted (in "dw_log_sum") |
| 5 days | Specifies the number of days after which log statistics in the |
Minimum duration until logs are deleted |
| 7 days | Defines the period for which logs are stored, even if a profile's backup interval is set to 0. Logs are not deleted until this period has elapsed. |
When you hover the mouse cursor over each field, a tooltip appears with information that includes the corresponding parameter name from startup.xml.
MongoDB settings
This section controls the long-term archiving of logs in MongoDB. The fields are editable only when the MongoDB service is active. If MongoDB is not active, all fields in this section are disabled.
Parameter | Default value | Description |
|---|---|---|
Activate long-term archiving | Disabled | If the checkbox is selected, logs are moved to the archive 30 days after they are created. |
Duration until logs are deleted from the archive | 900 days | Specifies the number of days after which archived logs are permanently deleted. |
Field status depending on the MongoDB configuration
Which fields are editable depends on whether MongoDB is active.
Field | MongoDB is not active | MongoDB is active |
|---|---|---|
Write logs to a file as well. | Editable | Editable |
Duration until logs without a job number are deleted. | Editable | Editable |
Duration until logs are deleted. | Editable | Not editable |
Duration until log statistics are deleted. | Editable | Not editable |
Minimum duration until logs are deleted. | Editable | Not editable |
Enable long-term archiving. | Not editable | Editable |
Duration until logs are deleted from the archive. | Not editable | Editable |
Apply button
Click Apply to save the changed values. The platform saves the changes to the database.
In a cluster system, the values are applied to all nodes.