Logging format not applied to String named logger when run as a Lambda function?

[roamingthings]

I'm using Quarkus for AWS Lambda functions. I'm also using the json-logging extension but the following is also true for a custom format set in the application.properties file.

When I create a logger using a String (name) rather than a Class, the custom format is not applied to my logging output, when I run the application as the real Lambda function. However, in tests everything works as expected.

I wonder if I miss something? If it's an issue I'm happy to create a GitHub issue and try to reproduce it in a sample-application.

[quarkus-bot[bot]]

/cc @matejvasek (amazon-lambda), @patriot1burke (amazon-lambda)

[dmlloyd]

It could be an issue; a reproducer would be needed to tell for sure though.

[roamingthings]

I will try to create a reproducer in the next days, when I have some spare time.

[roamingthings]

I created a project to reproduce the issue, but it's working there as expected. So I assume I have to figure out the difference between the reproducer and my "real" project.

[roamingthings]

I did some more research on my issue and found out that the issue arises from the library I am using (open-html-to-pdf) and the class-preloading mechanism from Quarkus: The logging-system from the library will initialize itself and replace all handlers and formats from its loggers. Therefore it's not an issue of Quarkus but how the library handles logging.

The solution I came up with is that I will remove the handlers/formatters (again) and re-apply the Quarkus handler.