Development of Log4j happens based on a) what committers are interested in doing or b) patches that are submitted by users. Sometimes we discuss things we want to develop in advance but most of the time we decide to do something and just do it.
You are the first person to ask for metrics from the AsyncAppender. We already have a JMX component so I would imagine reporting of those metrics would be integrated with that if it was implemented. I’ve not heard anyone mention integrating with those 3 libraries. As I noted above, patches are always welcome! Ralph > On Sep 30, 2017, at 4:16 PM, Yaroslav Skopets <y.skop...@gmail.com> wrote: > > Hi guys, > > I was going through the source code of `log4j2` and didn't notice any > metrics that could tell how the system is doing. > > Most importantly, classes like `AsyncAppender` might just silently drop > errors instead of making such incidents noticeable. > > So, do you have any plans to introduce metrics for those cases? And, > ideally, provide bindings to libraries like `Dropwizard`, `Prometheus`, > `Micrometer` ? > > Thanks in advance! > > -- > Best regards, > Yaroslav Skopets --------------------------------------------------------------------- To unsubscribe, e-mail: log4j-user-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-user-h...@logging.apache.org
