Quarkus - Configuring Logging

Run time configuration of logging is done through the normal file.

Configuration property fixed at build time - ️ Configuration property overridable at runtime

About the MemorySize formatA size configuration option recognises string in this format (shown as a regular expression): [0-9]+[KkMmGgTtPpEeZzYy]?.If no suffix is given, assume bytes.

Logging is done on a per-category basis. Each category can be independently configured.A configuration which applies to a category will also apply to all sub-categories of that category,unless there is a more specific matching sub-category configuration.

The quotes shown in the property name are required as categories normally contain '.' which mustbe escaped. An example is shown in File TRACE Logging Configuration.

Root logger configuration

The root logger category is handled separately, and is configured via the following properties:

Symbol	Summary	Description
`%%`	`%`	Renders a simple `%` character.
`%c`	Category	Renders the category name.
`%C`	Source class	Renders the source class name.^[2]
`%d{xxx}`	Date	Renders a date with the given date format string, which uses the syntax defined by `java.text.SimpleDateFormat`.
`%e`	Exception	Renders the thrown exception, if any.
`%F`	Source file	Renders the source file name.^[]
`%h`	Host name	Renders the system simple host name.
`%H`	Qualified host name	Renders the system’s fully qualified host name, which may be the same as the simple host name, depending on OS configuration.
`%i`	Process ID	Render the current process PID.
`%l`	Source location	Renders the source location information, which includes source file name, line number, class name, and method name.^[2]
`%L`	Source line	Renders the source line number.^[]
`%m`	Full Message	Renders the log message plus exception (if any).
`%M`	Source method	Renders the source method name.^[2]
`%n`	Newline	Renders the platform-specific line separator string.
`%N`	Process name	Render the name of the current process.
`%p`	Level	Render the log level of the message.
`%r`	Relative time	Render the time in milliseconds since the start of the application log.
`%s`	Simple message	Renders just the log message, with no exception trace.
`%t`	Thread name	Render the thread name.
`%t{id}`	Thread ID	Render the thread ID.
`%z{<zone name>}`	Time zone	Set the time zone of the output to `<zone name>`.
`%X{<MDC property name>}`	Mapped Diagnostics Context Value	Renders the value from Mapped Diagnostics Context
`%X`	Mapped Diagnostics Context Values	Renders all the values from Mapped Diagnostics Context in format {property.key=property.value}
`%x`	Nested Diagnostics context values	Renders all the values from Nested Diagnostics Context in format {value1.value2}

Console DEBUG Logging, No color, Shortened Time, Shortened Category Prefixes

File TRACE Logging Configuration

quarkus.log.file.enable=true
# Send output to a trace.log file under the /tmp directory
quarkus.log.file.path=/tmp/trace.log
quarkus.log.file.level=TRACE
quarkus.log.file.format=%d{HH:mm:ss} %-5p [%c{2.}] (%t) %s%e%n
quarkus.log.category."io.quarkus.smallrye.jwt".level=TRACE

Applications and components may use any of the following APIs for logging, and the logs will be merged:

JDK java.util.logging

1. Some extensions may define customized default log levels for certain categories, in order to reduce log noise by default. Setting the log level in configuration will override any extension-defined log levels.

. Format sequences which examine caller information may affect performance