Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Allow overriding log defaults, i.e. force logs to console, great for docker

Description

at the moment we have a lot of log files, which makes tracking down problems time consuming

add the option to define one (or possibly more) global override log destination(s) i

i.e. send all logs to a single log file directory, or log single file, perhaps also to a datasource (yes that adds overhead, but flexibility)

still use all the individual log file level configurations, esp LOG_LEVEL obvs

{ "sysprop": "lucee.logging.force.appender", "envvar": "LUCEE_LOGGING_FORCE_APPENDER", "desc": "If set, override the default log4j appender, which is usually resource (log files), use console to log all logs to console" }, { "sysprop": "lucee.logging.force.level", "envvar": "LUCEE_LOGGING_FORCE_LEVEL", "desc": "If set, override the default log4j log level for all logs, which is usually ERROR" }

i.e. the following configuration will log all lucee logs out to the console, which is great for docker

set lucee_logging_force_level=trace set lucee_logging_force_appender=console

Activity

Show:

Zac Spitzer 4 days ago

Zac Spitzer 1 February 2025 at 11:37

Pete Freitag 10 June 2021 at 19:15

Would be useful if there were an environment variable to override the log level globally for this. So if I’m debugging an issue I could just set an environment variable to set the log level to DEBUG, or on production I only want to log errors.

Fixed

Details

Assignee

Reporter

Labels

New Issue warning screen

Before you create a new Issue, please post to the mailing list first https://dev.lucee.org

Once the issue has been verified, one of the Lucee team will ask you to file an issue

Sprint

Fix versions

Priority

Created 5 April 2021 at 14:48
Updated 4 days ago
Resolved 3 February 2025 at 16:04