## Chapter 2: Architecture

Authors: Ceki Gülcü, Sébastien Pennec

| Copyright © 2000-2006, QOS.ch This work is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 2.5 License .

## Logback architecture

Logback's basic architecture is sufficiently generic so as to apply under different circumstances. At present time, logback is divided into three modules, Core, Classic and Access.

The core module lays the groundwork for the other two modules. The classic module extends core. The classic module corresponds to a significantly improved version of log4j. Logback-classic natively implements the SLF4J API so that you can readily switch back and forth between logback and other logging systems such as log4j or JDK14 Logging. The third module called access integrates with Servlet containers to provide HTTP-access log functionality. The access module will be covered in a separate document.

In the reminder of this document, we will write "logback" to refer to the logback classic module.

## Logger, Appenders and Layouts

Logback has three main types: `Logger`, `Appender` and `Layout`. These three types of components work together to enable developers to log messages according to message type and level, and to control at runtime how these messages are formatted and where they are reported.

The Logger class is part of the classic module. On the other hand, the `Appender` and `Layout` interfaces are part of the core module. For the sake of genericity, logback-core has no notion of loggers.

### Logger context

The first and foremost advantage of any logging API over plain `System.out.println` resides in its ability to disable certain log statements while allowing others to print unhindered. This capability assumes that the logging space, that is, the space of all possible logging statements, is categorized according to some developer-chosen criteria. In logback, this categorization is an inherent part of loggers.

Loggers are named entities. Their names are case-sensitive and they follow the hierarchical naming rule:

Named Hierarchy

A logger is said to be an ancestor of another logger if its name followed by a dot is a prefix of the descendant logger name. A logger is said to be a parent of a child logger if there are no ancestors between itself and the descendant logger.

For example, the logger named `"com.foo"` is a parent of the logger named `"com.foo.Bar"`. Similarly, `"java"` is a parent of `"java.util"` and an ancestor of `"java.util.Vector"`. This naming scheme should be familiar to most developers.

The root logger resides at the top of the logger hierarchy. It is exceptional in that it is part of every hierarchy at its inception. Like every logger, it can be retrieved by its name, as follows:

    Logger rootLogger = LoggerFactory.getLogger(LoggerContext.ROOT_NAME);

All other loggers are also retrieved with the class static `getLogger` method found in the org.slf4j.LoggerFactory class. This method takes the name of the desired logger as a parameter. Some of the basic methods in the `Logger` interface are listed below.

    package org.slf4j;
    public interface Logger {

      // Printing methods:
      public void debug(String message);
      public void info(String message);
      public void warn(String message);
      public void error(String message);
      public void fatal(String message);
    }

Loggers may be assigned levels. The set of possible levels, that is DEBUG, INFO, WARN and ERROR are defined in the `ch.qos.logback.classic.Level` class. Note that in logback, the level class is final and cannot be derived, as a much more flexible approach exist in the form of Marker objects.

If a given logger is not assigned a level, then it inherits one from its closest ancestor with an assigned level. More formally:

Level Inheritance

The effective level for a given logger L, is equal to the first non-null level in its hierarchy, starting at L itself and proceeding upwards in the hierarchy towards the root logger.

To ensure that all loggers can eventually inherit a level, the root logger always has an assigned level. By default, this level is DEBUG.

Below are four examples with various assigned level values and the resulting effective (inherited) levels according to the level inheritance rule.

Example 1

Logger name | Assigned level | Effective level
--- | --- | ---
root | DEBUG | DEBUG
X | none | DEBUG
X.Y | none | DEBUG
X.Y.Z | none | DEBUG

In example 1 above, only the root logger is assigned a level. This level value, `DEBUG`, is inherited by the other loggers `X`, `X.Y` and `X.Y.Z`

Example 2

Logger name | Assigned level | Effective level
--- | --- | ---
root | ERROR | ERROR
X | INFO | INFO
X.Y | DEBUG | DEBUG
X.Y.Z | WARN | WARN

In example 2 above, all loggers have an assigned level value. Level inheritence does not come into play.

Example 3

Logger name | Assigned level | Effective level
--- | --- | ---
root | DEBUG | DEBUG
X | INFO | INFO
X.Y | none | INFO
X.Y.Z | ERROR | ERROR

In example 3 above, the loggers `root`, `X` and `X.Y.Z` are assigned the levels `DEBUG`, `INFO` and `ERROR` respectively. Logger `X.Y` inherits its level value from its parent `X`.

Example 4

Logger name | Assigned level | Effective level
--- | --- | ---
root | DEBUG | DEBUG
X | INFO | INFO
X.Y | none | INFO
X.Y.Z | none | INFO

In example 4 above, the loggers `root` and `X` and are assigned the levels `DEBUG` and `INFO` respectively. The loggers `X.Y` and `X.Y.Z` inherit their level value from their nearest parent `X`, which has an assigned level.

### Printing methods

By definition, the printing method determines the level of a logging request. For example, if `L` is a logger instance, then the statement `L.info("..")` is a logging statement of level INFO.

A logging request is said to be enabled if its level is higher than or equal to the level of its logger. Otherwise, the request is said to be disabled. A logger without an assigned level will inherit one from the context. This rule is summarized below.

Basic Selection Rule

A log request of level p in a logger with an effective level q, is enabled if p >= q.

This rule is at the heart of logback. It assumes that levels are ordered as follows: `DEBUG < INFO < WARN < ERROR< OFF`.

In a more graphic way, here is how the selection rule works. In the following table, the vertical header shows the the level of the logging request, designated by p, while the horizontal header shows effective level of the logger, designated by q.

p/q | DEBUG | INFO | WARN | ERROR | OFF
--- | --- | --- | --- | --- | ---
DEBUG | YES | NO | NO | NO | NO
INFO | YES | YES | NO | NO | NO
WARN | YES | YES | YES | NO | NO
ERROR | YES | YES | YES | YES | NO

Here is an example of the basic selection rule.

    // get a logger instance named "com.foo", with an INFO level.
    Logger logger = LoggerFactory.getLogger("com.foo");
    //set its Level to INFO
    logger.setLevel(Level. INFO);
    Logger barlogger = LoggerFactory.getLogger("com.foo.Bar");

    // This request is enabled, because WARN >= INFO
    logger.warn("Low fuel level.");

    // This request is disabled, because DEBUG < INFO.
    logger.debug("Starting search for nearest gas station.");

    // The logger instance barlogger, named "com.foo.Bar",
    // will inherit its level from the logger named
    // "com.foo" Thus, the following request is enabled
    // because INFO >= INFO.
    barlogger.info("Located nearest gas station.");

    // This request is disabled, because DEBUG < INFO.
    barlogger.debug("Exiting gas station search");

### Retrieving Loggers

Calling the `LoggerFactory.getLogger` method with the same name will always return a reference to the exact same logger object.

For example, in

    Logger x = LoggerFactory.getLogger("wombat");
    Logger y = LoggerFactory.getLogger("wombat");

`x` and `y` refer to exactly the same logger object.

Thus, it is possible to configure a logger and then to retrieve the same instance somewhere else in the code without passing around references. In fundamental contradiction to biological parenthood, where parents always preceed their children, logback loggers can be created and configured in any order. In particular, a "parent" logger will find and link to its descendants even if it is instantiated after them.

Configuration of the logback environment is typically done at application initialization. The preferred way is by reading a configuration file. This approach will be discussed shortly.

Logback makes it easy to name loggers by software component. This can be accomplished by instantiating a logger in each class, with the logger name equal to the fully qualified name of the class. This is a useful and straightforward method of defining loggers. As the log output bears the name of the generating logger, this naming strategy makes it easy to identify the origin of a log message. However, this is only one possible, albeit common, strategy for naming loggers. Logback does not restrict the possible set of loggers. As a developer, you are free to name loggers as you wish.

Nevertheless, naming loggers after the class where they are located seems to be the best general strategy known so far.

### Appenders and Layouts

The ability to selectively enable or disable logging requests based on their logger is only part of the picture. Logback allows logging requests to print to multiple destinations. In logback speak, an output destination is called an appender. Currently, appenders exist for the console, files, remote socket servers, to MySQL, PostgreSQL, Oracle and other databases, JMS, and remote UNIX Syslog daemons.

More than one appender can be attached to a logger.

The `addAppender` method adds an appender to a given logger. Each enabled logging request for a given logger will be forwarded to all the appenders in that logger as well as the appenders higher in the hierarchy. In other words, appenders are inherited additively from the logger hierarchy. For example, if a console appender is added to the root logger, then all enabled logging requests will at least print on the console. If in addition a file appender is added to a logger, say L, then enabled logging requests for L and L's children will print on a file and on the console. It is possible to override this default behavior so that appender accumulation is no longer additive by setting the additivity flag of a logger to false.

The rules governing appender additivity are summarized below.

Appender Additivity

The output of a log statement of logger L will go to all the appenders in L and its ancestors. This is the meaning of the term "appender additivity".

However, if an ancestor of logger L, say P, has the additivity flag set to false, then L's output will be directed to all the appenders in L and it's ancestors upto and including P but not the appenders in any of the ancestors of P.

Loggers have their additivity flag set to true by default.

The table below shows an example:

Logger Name | Attached Appenders | Additivity Flag | Output Targets | Comment
--- | --- | --- | --- | ---
root | A1 | not applicable | A1 | Since the root logger stands at the top of the logger hiearchy, the additivity flag does not apply to it.
x | A-x1, A-x2 | true | A1, A-x1, A-x2 | Appenders of "x" and of root.
x.y | none | true | A1, A-x1, A-x2 | Appenders of "x" and of root.
x.y.z | A-xyz1 | true | A1, A-x1, A-x2, A-xyz1 | Appenders of "x.y.z", "x" and of root.
security | A-sec | false | A-sec | No appender accumulation since the additivity flag is set to `false`. Only appender A-sec will be used.
security.access | none | true | A-sec | Only appenders of "security" because the additivity flag in "security" is set to `false`.

More often than not, users wish to customize not only the output destination but also the output format. This is accomplished by associating a layout with an appender. The layout is responsible for formatting the logging request according to the user's wishes, whereas an appender takes care of sending the formatted output to its destination. The `PatternLayout`, part of the standard logback distribution, lets the user specify the output format according to conversion patterns similar to the C language `printf` function.

For example, the PatternLayout with the conversion pattern "%-4relative [%thread] %-5level %logger{32} - %msg%n" will output something akin to:

    176  [main] DEBUG chapter2.HelloWorld2 - Hello world.

The first field is the number of milliseconds elapsed since the start of the program. The second field is the thread making the log request. The third field is the level of the log request. The fourth field is the name of the logger associated with the log request. The text after the '-' is the message of the request.

### Parameterized logging

Given that loggers in logback-classic implement the SLF4J's Logger interface, certain printing methods admit more than one parameter. These printing method variants are mainly intended to improve performance while minimizing the impact on the readability of the code.

For some Logger `logger`, writing,

    logger.debug("Entry number: " + i + " is " + String.valueOf(entry[i]));

incurs the cost of constructing the message parameter, that is converting both integer `i` and `entry[i]` to a String, and concatenating intermediate strings. This, regardless of whether the message will be logged or not.

One possible way to avoid the cost of parameter construction is by surrounding the log statement with a test. Here is an example.

    if(logger.isDebugEnabled()) {
      logger.debug("Entry number: " + i + " is " + String.valueOf(entry[i]));
    }

This way you will not incur the cost of parameter construction if debugging is disabled for `logger`. On the other hand, if the logger is enabled for the DEBUG level, you will incur the cost of evaluating whether the logger is enabled or not, twice: once in `debugEnabled` and once in `debug`. This is an insignificant overhead because evaluating a logger takes less than 1% of the time it takes to actually log a request.

#### Better alternative

There exists a convenient alternative based on message formats. Assuming `entry` is an object, you can write:

    Object entry = new SomeObject();
    logger.debug("The entry is {}.", entry);

After evaluting whether to log or not, and only if the decision is positive, will the logger implementation format the message and replace the '{}' pair with the string value of `entry`. In other words, this form does not incur the cost of parameter construction in case the log statement is disabled.

The following two lines will yield the exact same output. However, in case of a disabled logging statement, the second variant will outperform the first variant by a factor of at least 30.

    logger.debug("The new entry is "+entry+".");
    logger.debug("The new entry is {}.", entry);

A two argument variant is also availalble. For example, you can write:

    logger.debug("The new entry is {}. It replaces {}.", entry, oldEntry);

If three or more arguments need to be passed, an `Object[]` variant is also availalble. For example, you can write:

    Object[] paramArray = {newVal, below, above};
    logger.debug("Value {} was inserted between {} and {}.", paramArray);

### Configuration

Inserting log requests into the application code requires a fair amount of planning and effort. Observation shows that approximately four percent of code is dedicated to logging. Consequently, even moderately sized applications will contain thousands of logging statements embedded within its code. Given their number, it becomes imperative to manage these log statements without the need to modify them manually.

In order to run the examples in this introduction, you need to make sure that certain jar files are present on the classpath. Please refer to the setup page for further details.

The logback environment is fully configurable programmatically. However, it is far more flexible to configure logback using configuration files. In logback, configuration files are written in XML format.

Existing log4j users can convert their log4j.properties files to logback.xml using our PropertiesTranslator web-application.

Configuring logback from a XML file is an easy task. One just needs to instanciate a `JoranConfigurator` and pass the configuration file, as the following example demonstrate.

Example 2.1: Logback configuration from file (logback-examples/src/main/java/chapter2/MyAppWithConfigFile.java)

    package chapter2;

    //Import SLF4J classes.
    import org.slf4j.Logger;
    import org.slf4j.LoggerFactory;

    import ch.qos.logback.classic.LoggerContext;
    import ch.qos.logback.classic.joran.JoranConfigurator;
    import ch.qos.logback.core.util.StatusPrinter;

    public class MyAppWithConfigFile {

      public static void main(String[] args) {
        Logger logger = LoggerFactory.getLogger(MyAppWithConfigFile.class);
        LoggerContext lc = (LoggerContext) LoggerFactory.getILoggerFactory();

        JoranConfigurator configurator = new JoranConfigurator();
        configurator.setContext(lc);
        configurator.doConfigure(args[0]);

        logger.info("Entering application.");
        Bar bar = new Bar();
        bar.doIt();
        logger.info("Exiting application.");

        StatusPrinter.print(lc.getStatusManager());
      }
    }

This class defines a logger instance variable. It then instantiates a `Bar` object. The `Bar` class is listed below:

Example 2.2: Sample logging class (logback-examples/src/main/java/chapter2/Bar.java)

    package chapter2;

    import org.slf4j.Logger;
    import org.slf4j.LoggerFactory;

    class Bar {

      Logger logger = LoggerFactory.getLogger(Bar.class);

      public void doIt() {
        logger.debug("doing my job");
      }
    }

MyAppWithConfigFile configures logback by using the `JoranConfigurator`. Joran is a XML interpreter, similar to the commons-digester API, but offering several advantages over commons-digester. Here, it parses the xml file and runs actions depending on the tags it finds. To setup the `JoranConfigurator` properly, we passed the `LoggerContext`. A `LoggerContext` is the class that creates and manages Loggers in logback. It is also the class that implements the `org.slf4j.ILoggerFactory` interface.

All other classes only need to retrieve an instance of `org.slf4j.Logger` by calling `LoggerFactory.getLogger()`, and then log away. For example, the only dependence of the `Bar` class is on `org.slf4j.Logger` and `org.slf4j.LoggerFactory`. Except code that configures logback (if such code exists) user code does not need to depend on logback, but on SLF4J instead.

Let us configure logback with the next XML configuration file:

Example 2.3: Basic configuration with a xml file (logback-examples/src/main/java/chapter2/sample-config-1.xml)

    <?xml version="1.0" encoding="UTF-8" ?>

    <configuration>

      <appender name="STDOUT"
        class="ch.qos.logback.core.ConsoleAppender">
        <layout class="ch.qos.logback.classic.PatternLayout">
          <pattern>%d{HH:mm:ss.SSS} [%thread] %-5level %logger{36} - %msg%n</pattern>
        </layout>
      </appender>

      <root>
        <level value="debug" />
        <appender-ref ref="STDOUT" />
      </root>
    </configuration>

We first created an `Appender`, named STDOUT that is of `ConsoleAppender` type. Its layout is managed by a `PatternLayout`, that uses the value of the pattern parameter to generate the logging statement. We then configured the root logger, set its level to DEBUG, and linked the newly configured `ConsoleAppender` to the root logger.

Note that we've set the root logger level explicitly. Since root logger have a DEBUG level by default we could have omitted this.

To run this example, use this command:

    java chapter2.MyAppWithConfigFile src/main/java/chapter2/sample-config-1.xml

Here is what you should see in the console:

    18:15:26.718 [main] INFO  chapter2.MyAppWithConfigFile - Entering application.
    18:15:26.718 [main] DEBUG chapter2.Bar - doing my job
    18:15:26.718 [main] INFO  chapter2.MyAppWithConfigFile - Exiting application.

Logging to the console is a rather simple example. Let's now configure logback so that it logs on the console, but also to a custom file.

Example 2.4: Configuring logback with multiple appenders (logback-examples/src/main/java/chapter2/sample-config-2.xml)

    <?xml version="1.0" encoding="UTF-8" ?>

    <configuration>

      <appender name="STDOUT"
        class="ch.qos.logback.core.ConsoleAppender">
        <layout class="ch.qos.logback.classic.PatternLayout">
          <pattern>%-4relative [%thread] %-5level %class - %msg%n</pattern>
        </layout>
      </appender>

      <appender name="FILE"
        class="ch.qos.logback.core.FileAppender">
        <layout class="ch.qos.logback.classic.PatternLayout">
          <pattern>%-4relative [%thread] %-5level %class - %msg%n</pattern>
        </layout>
        <File>sample-log.txt</File>
      </appender>

      <root>
        <level value="debug" />
        <appender-ref ref="STDOUT" />
        <appender-ref ref="FILE" />
      </root>
    </configuration>

Now, all the logging statements are directed to the console and to a file named sample-log.txt. As you can see, the configuration needed to add an Appender is rather small. The options are declared as xml element, in either Appender configuration. They are read and their value are assigned to the corresponding attribute in the specified java class.

Suppose that we do not want to see the DEBUG level statements in the chapter2 package anymore. This is done by adding the following bold xml snippet to the configuration file, right before the `<root>` element.

Example 2.5: Configuring a specific logger (logback-examples/src/main/java/chapter2/sample-config-3.xml)

    <?xml version="1.0" encoding="UTF-8" ?>

    <configuration>

      <appender name="STDOUT"
        class="ch.qos.logback.core.ConsoleAppender">
        <layout class="ch.qos.logback.classic.PatternLayout">
          <pattern>%-4relative [%thread] %-5level %class - %msg%n</pattern>
        </layout>
      </appender>

      <appender name="FILE"
        class="ch.qos.logback.core.FileAppender">
        <layout class="ch.qos.logback.classic.PatternLayout">
          <pattern>%-4relative [%thread] %-5level %class - %msg%n</pattern>
        </layout>
        <File>sample-log.txt</File>
      </appender>

      <logger name="chapter2">
        <level value="info" />
      </logger>

      <root>
        <level value="debug" />
        <appender-ref ref="STDOUT" />
        <appender-ref ref="FILE" />
      </root>
    </configuration>

Once done, the output is modified to show only statements of level INFO and higher:

    0    [main] INFO  chapter2.MyAppWithConfigFile - Entering application.
    0    [main] INFO  chapter2.MyAppWithConfigFile - Exiting application.

Note that to obtain these different logging behaviors we did not need to recompile code. We could just as easily have logged to a UNIX Syslog daemon, redirected all chapter2 output to a log visualizer, or forwarded logging events to a remote logback server, which would log according to local server policy, for example by forwarding the log event to a second logback server.

Until now, we always had to specifically load the configuration file and pass it to a logback component. However, this step is not necessary in most cases. When logback is not configured by instanciating `JoranConfigurator` objects, it follows a simple policy to configure itself.

Logback first tries to find a file called logback.xml within the classpath.

If no such file is found, it checks for another file called logback-test.xml.

In case none of these files are found, logback configures itself automatically using the `BasicConfigurator` class.

The first two checks allow for two environments to cooperate nicely. When the application using logback is in development and test process, a special file can be used to setup a logging environment that is developer-friendly. Once in production environment, the presence of a logback.xml file overrides any logback-test.xml configuration.

The last step is meant to provide very basic logging functionnality in case no configuration file is provided. In that case, the logging requests are output to the console.

Letting logback load its configuration file is the most often used way of configuring. It allows the user to only import SLF4J classes in her code.

The last step of logback's configuration policy permits the use of a minimal logging configuration right out of the box. Remember the very first example of the introduction. The output was generated due to this feature.

### A peak under the hood

After we have introduced the essential logback components, we are now ready to describe the steps that the logback framework takes when the user invokes a logger's printing method. Let us now analyze the steps logback takes when the user invokes the `info()` method of a logger named com.wombat.

#### 1. Get the filter chain decision

Logback's `TurboFilter` chain is called. These filters may be used to prodvide a context-wide threshold, or to filter out certain events based on basic logging informations such as `Marker`, `Level`, `Logger`, message, or the `Throwable` that was provided in the logging request. If the reply of the filter chain is `FilterReply.DENY`, then the logging request is dropped. If it is `FilterReply.NEUTRAL`, then the next step is processed. In case the reply is `FilterReply.ACCEPT`, the next step is skipped and the logging request is directly processed to step 3.

#### 2. Apply the Logger level filter

Logback compares the effective level of the com.wombat logger with the level of the request (in this example: INFO). If the logging request is disabled, then logback will drop the request without further processing.

#### 3. Create a `LoggingEvent` object

If the request passed the previous filter, or if the `TurboFilter` chain gave a `FilterReply.ACCEPT` result, logback will create a `ch.qos.logback.classic.LoggingEvent` object containing all the relevant parameters of the request such as the logger of the request, the request level, the message, the exception that might have been passed along the request, the current time, the current thread, several information about the class that issued the logging request and the `MDC` map. Note that some of these fields are initialized lazily, that is only when they are actually needed. The `MDC` is used to stamp each requests with specific parameters. It is introduced in the corresponding chapter.

#### 4. Invoking appenders

After the creation of a `LoggingEvent` object, logback will proceed to invoke the `doAppend()` methods of all the applicable appenders, that is, the appenders inherited from the logger context.

All appenders shipped with the logback distribution extend the `AppenderBase` abstract class that implements the `doAppend` method in a synchronized block ensuring thread-safety. The `doAppend()` method of `AppenderBase` also invokes custom filters attached to the appender, if any such filters exist. Custom filters, which can be dynamically attached to any appender, are presented Chapter 6.

#### 5. Formatting the `LoggingEvent`

It is responsibility of the invoked appender to format the logging event. However, most (but not all) appenders delegate the task of formatting the logging event to their layout. Their layout formats the `LoggingEvent` instance and returns the result as a String. Note that some appenders, such as the `SocketAppender`, do not transform the logging event into a string but serialize it instead. Consequently, they do not require nor have a layout.

#### 6. Sending out the `LoggingEvent`

After the logging event is fully formatted it is sent to its destination by each appender.

Here is a sequence UML diagram to show how everything works. You might want to click on the image to display its bigger version.

### Performance

One of the often-cited arguments against logging is its computational cost. This is a legitimate concern as even moderately sized applications can generate thousands of log requests. Much effort is spent measuring and tweaking logging performance. Independently of these efforts, the user should still be aware of the following performance issues.

#### 1. Logging performance when logging is turned off entirely

You can turn off logging entirely by setting the level of the root logger to `Level.OFF`, the highest possible level. When logging is turned off entirely, the cost of a log request consists of a method invocation plus an integer comparison. On a 3.2Ghz Pentium D machine this cost is typically around 20 nanoseconds.

However, any method invocation involves the "hidden" cost of parameter construction. For example, for some logger x writing,

    x.debug("Entry number: " + i + "is " + entry[i]);

incurs the cost of constructing the message parameter, i.e. converting both integer `i` and `entry[i]` to a string, and concatenating intermediate strings, regardless of whether the message will be logged or not.

The cost of parameter construction can be quite high and depends on the size of the parameters involved. To avoid the cost of parameter construction you can use logback's parametrized logging:

    x.debug("Entry number: {} is {}", i, entry[i]);

This will not incur the cost of parameter construction. Compared to the previous call to the `debug()` method, this call will be faster by a very wide margin. The message will be formatted only if the request is processed to the appenders. If it is processed, the component that formats the message offers high performance and does not impact negatively the overall process. It respectively takes 2 and 4 microseconds to format a message with 1 and 3 parameters.

Please notice that, despite the performance points that we just discussed, inserting logging statements in tight-loops or very frequently invoked code is a lose-lose proposal and will not result in high performance. They will slow down your application even if logging is turned off or generate massive (and hence useless) output if enabled.

#### 2. The performance of deciding whether to log or not to log when logging is turned on.

In logback, there is no need to walk the whole logger hierarchy. A logger knows its effective level (that is, its level, once level inheritance has been taken into consideration) when it is created. Should the level of a parent logger be changed, then all child loggers will be contacted and handle the change. Thus, before accepting or denying a request based on the effective level, the logger does not need to search its ancestors.

Given this situation, it takes the same time to decide whether to log or not when logging is turned on as it takes when logging is turned off.

#### 3. Actual logging (formatting and writing to the output device)

This is the cost of formatting the log output and sending it to its target destination. Here again, a serious effort was made to make layouts (formatters) perform as quickly as possible. The same is true for appenders. The typical cost of actually logging is about 9 to 12 microseconds when logging to a file on the local machine. It goes up to 1 millisecond when logging to a database on a remote server.

Although feature-rich, one of the foremost design goals of logback was speed of execution, a requirement which is second only to reliability. Some logback components have been rewritten many times to improve performance.