Logging

When you encounter an issue in Collibra Data Intelligence Cloud, the log file can provide a lot of interesting information about what is happening/has happened.

Whenever there seems to be something wrong with the product, it is good practice to check the log file first.

When you report a problem to Collibra support, it is recommended to immediately attach the log file(s) to your support ticket.

Depending on the configuration, the log file shows you:

  • Errors that have occurred on the server side
  • Basic information about tasks that are performed
  • Detailed information about every action that has been performed
  • The date and time an event occurred
  • The thread that is executing an action
  • The log level of the message

You can see consult the log files in Collibra Console, or you can download the log files in Collibra Console.

If you download the log files, they are compressed (zipped). You have to decompress them before you can read them. You can use any text editor, like Notepad to read the log files.

Tip If the log file is displayed as a single, long line in Notepad, download and use the (free) text editor Notepad++ from http://notepad-plus-plus.org

The log files can also be found on the file system of the server /opt/collibra_data/<component>/logs. For more information on the Collibra directory structure, see Product architecture.

Log retention

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

  • The log files are rotated daily or when they reach a file size of 100 MB.
  • There are 30 log files in history, so a maximum of 30 days.
  • There is a maximum of 1 GB of all log files.

So, the log files are rotated daily, with a maximum size of 100 MB each. This means that an active log file is archived when a new day starts (midnight, server time) or when its size reaches 100 MB. The rotated log file is renamed, containing the current date, for example dgc.2016-09-15.log. The active log file, for example dgc.log, then starts out empty.

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