cambium.logback.core.strategy
Log level override utility fns based on strategy turbo-filter. Example config (logback.xml):
<turboFilter class="cambium.logback.core.StrategyTurboFilter"> <name>mdcStrategy</name> </turboFilter>
<turboFilter class="cambium.logback.core.StrategyTurboFilter"> <name>multiStrategy</name> </turboFilter>
Here we define two strategy based turbo-filters that would probably be configured during app init phase.
Log level override utility fns based on strategy turbo-filter.
Example config (logback.xml):
<turboFilter class="cambium.logback.core.StrategyTurboFilter">
<name>mdcStrategy</name>
</turboFilter>
<turboFilter class="cambium.logback.core.StrategyTurboFilter">
<name>multiStrategy</name>
</turboFilter>
Here we define two strategy based turbo-filters that would probably be configured during app init phase.multi-count-validatorclj
(multi-count-validator n)Return a validator based on specified count of times when log level override should be applied. See: set-multi-strategy!
Return a validator based on specified count of times when log level override should be applied. See: set-multi-strategy!
multi-forever-validatorclj
A validator that always causes log level to be overridden. See: set-multi-strategy!
A validator that always causes log level to be overridden. See: set-multi-strategy!
multi-log-levelsclj
(multi-log-levels multi-strategy-name)Return a map of logger names to levels in the current multi-log-override configuration.
Return a map of logger names to levels in the current multi-log-override configuration.
multi-millis-validatorclj
(multi-millis-validator millis)Return a validator based on the duration (in milliseconds) for which the log level override should be applied. See: set-multi-strategy!
Return a validator based on the duration (in milliseconds) for which the log level override should be applied. See: set-multi-strategy!
remove-log-level!clj
(remove-log-level! multi-strategy-name logger-names)Remove specified logger names from the current multi-log-override configuration.
Remove specified logger names from the current multi-log-override configuration.
remove-strategy!clj
(remove-strategy! strategy-name)Remove a configured strategy by its name.
Remove a configured strategy by its name.
set-log-level!clj
(set-log-level! multi-strategy-name logger-names log-level)Set the specified log level for the given logger names in the current multi-log-override configuration.
Set the specified log level for the given logger names in the current multi-log-override configuration.
set-mdc-strategy!clj
(set-mdc-strategy! mdc-strategy-name mdc-key)Set turbo-filter strategy for the given strategy name based on specified MDC attribute, whose value can be set to a log level string to control which log levels are allowed to be logged.
Set turbo-filter strategy for the given strategy name based on specified MDC attribute, whose value can be set to a log level string to control which log levels are allowed to be logged.
set-multi-strategy!clj
(set-multi-strategy! multi-strategy-name root-log-level validator)Set turbo-filter strategy for the given strategy name based on multiple logger names, each of which can be assigned with a log level string to control which log levels are the loggers allowed to log at. A validator is a no-argument function (or instance of the java.util.concurrent.Callable interface) that returns a boolean value. The validator argument is used to determine how long should the log-level override be considered valid.
Set turbo-filter strategy for the given strategy name based on multiple logger names, each of which can be assigned with a log level string to control which log levels are the loggers allowed to log at. A validator is a no-argument function (or instance of the java.util.concurrent.Callable interface) that returns a boolean value. The validator argument is used to determine how long should the log-level override be considered valid.
cljdoc is a website building & hosting documentation for Clojure/Script libraries
× close