Ralph Goers

That is a fair point. We have a site.css but it contains almost nothing. When I look at what xdoc and markdown do, they are generating class names that are...

Please see [#2385](https://github.com/apache/logging-log4j2/pull/2385) as this should do what you want - for Java. I am not sure how to incorporate this into Kotlin. You can now do: ``` ScopedContext.newInstance().where("key1", "value1").where("key2",...

@rocketraman I guess I am not grasping at all what you want. With my PR you can now do: ``` class T { private static final Logger log = LogManger.getLogger(T.class);...

@rocketraman Again, I don't understand. ScopedContext IS a builder. Each where method adds a new key/value pair to the context. The run and call methods are, in essence, the builders....

OK. Personally, I see little value in adding context data to a logger. That simply wouldn't fit with any use cases I work with. However, it might if Logger names...

@rocketraman I understand your example but I am not sure how it works in practice. I have to presume that the Connection class can operate on multiple Connection instances. A...

I don't actually see a problem being stated anywhere here. What exactly is wrong?

Log4j 2.14.0 will include a new component, JsonTemplateLayout that uses a template to describe the format of the JSON. It was donated by the author of https://github.com/vy/log4j2-logstash-layout who is now...

First, I have to ask some obvious questions. 1. Why isn't your first thought to recommend changing this to ``` logger.error("Doing this thing failed. Context Id: {}, SomeSettings: {}", context.id,...

The current behavior is actually intentional. There is a ton of ambiguity involved when the last parameter is a throwable. Log4j 2 included this behavior since it was present in...