Logging in Equo Chromium

The output produced by Equo Chromium is managed by the Java Util Logging (JUL) API and is enabled via the chromium.debug system property.

The use of JUL to handle logging is only implemented as of version 128.0.12.

If chromium.debug is set to true, logging for Equo Chromium will be enabled. Otherwise it will always be disabled.

-Dchromium.debug=true

Configuring JUL

Java Util Logging can be configured either programmatically or with a logging configuration file or class, passed to JUL via the java.util.logging.config.file or java.util.logging.config.class system properties.

Setting a custom configuration file or class:

-Djava.util.logging.config.file
-Djava.util.logging.config.class

If you want to configure the Equo Chromium logger programmatically, you should get the logger first, with:

    static final Logger logger = Logger.getLogger("com.equo.chromium");

Redirecting Equo Chromium output to a file

To redirect the logs produced by Equo Chromium to a desired file in a desired location, you must set a FileHandler and define its pattern attribute in your JUL configuration:

In a configuration file:

handlers=java.util.logging.handlers.FileHandler
java.util.logging.handlers.FileHandler.pattern=<path_to_your_file>/<your_log_file_name>.log
The path to the log file can be absolute or relative to your application’s root.
There are several configuration options for the formatting of your log file’s name, as well as for the size limit; maximum amount of log files; whether logs will be appended to one single log file or have their own file each; among a few others. All listed in the Java Util Logging documentation.

For full knowledge on how to use JUL, please refer to the JUL Documentation.

By default, the Equo Chromium logs will be of level FINE, which is similar to a "debugging" level.