David Beaumont

100% agreed. I'm looking at ways to easily convert from one to the other.

We've thought about this a lot over the years, but the general consensus was that if the context allocations are an issue, then the cost of logging (formatting strings, processing...

If you know the backend you're using, you can just test using the backend's idiomatic approach. E.g. for JUL, just install a test log handler to capture the records and...

Ahh yes, the right way to do that is using the GrpcScopedLoggingContext which sadly I don't think is open-sourced yet. Basically if your Platform instance returns true for "shouldForceLogging" then...

@ronshapiro would you be up for this (since I'm a Maven noob).

Sounds like a plan. Note that SimpleMessageFormatter was never intended to be more than it is. It was always known not to be a great general purpose solution (hence the...

The parsers were written to handle existing formatting in Google. Printf format was written with the idea that other people would extend it, but now it seems that that's probably...

And unless it wasn't clear, reusing the Log4J2 stuff would also be fine by me if there are no "show stoppers". https://logging.apache.org/log4j/2.x/manual/layouts.html Especially the bits about PatternLayout and MDC stuff.

Apologies for not spotting some of these lingering issues (I'm not getting the email notifications I expected for this project). To put it in perspective a bit, Flogger deliberately doesn't...

@jbduncan where do you think adding new docs would make it clearest? I've made a couple of changes in code docs for LoggerConfig (internally so far, but should be pushed...