Logs settings page

When you encounter an issue in Collibra, the log file provides technical information that can help identify what happened:

Depending on the configuration, the log file shows:

Accessing log files

To access log files, you must have a global role with the Logs > View global permission, such as Sysadmin. You can consult log files on the Settings page or download them for offline use.

Note To optimize system performance, syntax highlighting is enabled only when 100 lines are shown.

If you download the log files, they are compressed. Decompress the files before reading them. You can use any text editor to view the contents.

The information in the log files is determined by the logger and logger level configured in the environment log settings in Collibra Console.

Log retention

In Collibra cloud environments:

By default, there is a cumulative size limit of 5 GB for log files stored in Collibra. This limit ensures efficient storage management. However, under heavy usage or with increased logging detail, such as during troubleshooting, you might reach the threshold before the 30-day retention period ends. This could result in older logs being removed earlier than expected.

By default, we are using a size and time rolling policy which is configured as follows:

Log files are rotated at the start of a new day (midnight, server time) or when the file size reaches 100 MB. Rotated files are renamed with the current date, for example dgc.2016-09-15.log. The active log file, such as dgc.log, is then reset and starts empty.

You can edit the log retention configuration in logging.properties in collibra_data/dgc/config.

Tip To retain logs for extended periods, generate diagnostic files. Diagnostic files bundle selected logs and environment information into a compressed ZIP archive. These archives, once created and stored in Collibra Console, do not count toward the log file storage limit. Generating diagnostic files periodically is a reliable method for preserving log data beyond the standard rotation cycle, especially for historical analysis or troubleshooting complex workflows.