Logging configuration

Logging can be enabled by making changes to the config/logs.xml file found within your Continuum CMS application. Below is an example entry from this file.

<item key="application" enable="false" level="warning" description="Jadu Application logs">/path/to/logs/</item>

To turn on logging modify the enable attribute to be true and update the path to be where you wish the log file to be created. We recommend using the logs directory that is located at the root of your Continuum CMS application.


The level option allows you to choose which severity level you would like the application to log. Eight levels are available and these are detailed below along with the type of information each one will log.

  • debug: Detailed debug information.

  • info: Interesting events. Examples: User logs in, SQL logs.

  • notice: Normal but significant events.

  • warning: Exceptional occurrences that are not errors.

  • error: Runtime errors that do not require immediate action but should typically be logged and monitored.

  • critical: Critical conditions.

  • alert: Action must be taken immediately.

  • emergency: Emergency: system is unusable.

    The application will log the level you have selected and anything that is higher in serverity. For example choosing a level of critical will log critical, alert, and emergency but no others.

results matching ""

    No results matching ""