[zer0gravity]

Well, to be really fair compare it with :

  if(logger.isDebugEnabled()){
        logger.debug("...");
  }

And yeah, it requires a bit more typting if you want to enforce a certain event format and want to add more parameters. But you only do that once, and I'd say you gain much more for your effort.

[CHY872]

Fyi, intended usage with most Java loggers is to just call

    logger.debug("...");

and ignore the conditional. If `!logger.isDebugEnabled` then the logger will ignore the message, so it avoids boilerplate.

[zer0gravity]

You want to wrap it in an if in order to avoid doing extra work ( like string concatenation or whatever ) and save some computation. It's to improve performance when logging is not enabled.

[jestar_jokin]

No good if you're computing the message somehow. e.g.

    logger.debug(generateSomethingLarge());

[CHY872]

Generally you would log with placeholders, like

    logger.debug("My logger message has placeholders {}, {}, {}", some, objects, toLog);

which avoids the issue.