Debug Log

The system operation logs of Doris’s FE and BE nodes are at INFO level by default. It can usually satisfy the analysis of system behavior and the localization of basic problems. However, in some cases, it may be necessary to enable DEBUG level logs to further troubleshoot the problem. This document mainly introduces how to enable the DEBUG log level of FE and BE nodes.

It is not recommended to adjust the log level to WARN or higher, which is not conducive to the analysis of system behavior and the location of problems.

Enable DEBUG log may cause a large number of logs to be generated, Please be careful to open it in production environment.

Enable FE Debug log

The Debug level log of FE can be turned on by modifying the configuration file, or it can be turned on at runtime through the interface or API.

  1. Open via configuration file

    Add the configuration item sys_log_verbose_modules to fe.conf. An example is as follows:

    1. # Only enable Debug log for class org.apache.doris.catalog.Catalog
    2. sys_log_verbose_modules=org.apache.doris.catalog.Catalog
    4. # Open the Debug log of all classes under the package org.apache.doris.catalog
    5. sys_log_verbose_modules=org.apache.doris.catalog
    7. # Enable Debug logs for all classes under package org
    8. sys_log_verbose_modules=org

    Add configuration items and restart the FE node to take effect.

  2. Via FE UI interface

    The log level can be modified at runtime through the UI interface. There is no need to restart the FE node. Open the http port of the FE node (8030 by default) in the browser, and log in to the UI interface. Then click on the Log tab in the upper navigation bar.

    image.png

    We can enter the package name or specific class name in the Add input box to open the corresponding Debug log. For example, enter org.apache.doris.catalog.Catalog to open the Debug log of the Catalog class:

    image.png

    You can also enter the package name or specific class name in the Delete input box to close the corresponding Debug log.

    The modification here will only affect the log level of the corresponding FE node. Does not affect the log level of other FE nodes.

  3. Modification via API

    The log level can also be modified at runtime via the following API. There is no need to restart the FE node.

    1. curl -X POST -uuser:passwd fe_host:http_port/rest/v1/log?add_verbose=org.apache.doris.catalog.Catalog

    The username and password are the root or admin users who log in to Doris. The add_verbose parameter specifies the package or class name to enable Debug logging. Returns if successful:

    1. {
    2.     "msg": "success",
    3.     "code": 0,
    4.     "data": {
    5.         "LogConfiguration": {
    6.             "VerboseNames": "org,org.apache.doris.catalog.Catalog",
    7.             "AuditNames": "slow_query,query,load",
    8.             "Level": "INFO"
    9.         }
    10.     },
    11.     "count": 0
    12. }

    Debug logging can also be turned off via the following API:

    1. curl -X POST -uuser:passwd fe_host:http_port/rest/v1/log?del_verbose=org.apache.doris.catalog.Catalog

    The del_verbose parameter specifies the package or class name for which to turn off Debug logging.

Enable BE Debug log

BE’s Debug log currently only supports modifying and restarting the BE node through the configuration file to take effect.

  1. sys_log_verbose_modules=plan_fragment_executor,olap_scan_node
  2. sys_log_verbose_level=3

sys_log_verbose_modules specifies the file name to be opened, which can be specified by the wildcard *. for example:

  1. sys_log_verbose_modules=*

Indicates that all DEBUG logs are enabled.

sys_log_verbose_level indicates the level of DEBUG. The higher the number, the more detailed the DEBUG log. The value range is 1-10.