Hello Adam,
I am very sorry for the frustrating experience. I can certainly see you do
an excellent job in getting engaged with the project to get this feature
request rolling. Thank you so much for that.
I read your conversation with Piotr and I get your point – yes, neither
migration to Log4j 3
Volkan,
Not frustrating at all, I'm coming into this without any real experience with
how log4j approaches API design.
> Thinking naively: Assuming you already thought about it, why doesn't the
> following work for you?
> 1. Cast the `LoggerContext` to `AsyncLoggerContext`
> 2. Reflectively ext
*Short answer:* I would suggest using reflection for the time being. We
don't anticipate any changes in that part of the code base in the
foreseeable future.
*Slightly longer answer:* Log4j has never had a holistic observability view
to its internals. We need something new (if not, from scratch),
