Trying to collect logs for grafana but I'm seeing exception log messages having odd cut-offs and delayed rendering in the console output

dev support
1

I am attempting to consume logs to Grafana in a lucee commandbox docker image. I had planned to send the loggers to the console so I could format and then consume them. However I noticed that exceptions were already shown in the console output, but delayed and chopped mid-message. It feels like it is buffering the errors prior to sending to the output.

I was able to reproduce this in a lucee docker image and also running locally using multiple versions.

For example, my test page is simply:
if I refresh the page a few times, I’ll eventually start to see messages like so:

"[ERROR] runwar.context: teHandler.java:43)
at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:46)
at "
that goes on for about 8000+ characters and then abruptly cuts off.

So I have a few questions:

  1. Is this normal behavior
  2. Is there a better way I could/should be collecting and formatting the logger output?

Thanks!

Don’t forget to tell us about your stack!

OS: commandbox:alpine-3.7.3
Lucee Version: lucee@5.3.10+120, but I also tested lucee@6.0.0.382-SNAPSHOT