HTTP Access Log to both file and console

[jfslin]

Is it possible for quarkus.http.access-log.enabled to be logged both to file (ie quarkus.http.access-log.log-to-file=true) and to console (ie quarkus.http.access-log.log-to-file=false)? Playing with the settings seems to show that it's either console or file. If it is actually possible to stream to two different sources, is it possible to have a specific quarkus.http.access-log.pattern for each individual stream?

I am interested in having the console logged to Grafana, but also a quick way of pulling the last 24 hours of access log via file to check the HTTP requests-response codes. I am guessing there is a way to hook all this up to Grafana, but that's been a work in progress.

If there is not a way to stream the access log to both console and file, I will just stick with file stream for now.

Thank you.

[phillip-kruger]

There is no way currently, but we should be able to add this. I'll have a look

[cescoffier]

It might be possible using the JBOSS Logging Access Log Handler

Set log-to-file to false and configure the access log category (io.quarkus.http.access-log by default). Then configure the log category to go in a file and in the console at the same time.

[cescoffier]

This works:

quarkus.http.access-log.enabled=true
quarkus.http.access-log.log-to-file=false

quarkus.log.handler.file.access-log.enable=true
quarkus.log.handler.file.access-log.path=application.log
quarkus.log.handler.file.access-log.format=%d{yyyy-MM-dd HH:mm:ss} %s%e%n

quarkus.log.handler.console.access-console.format=%d{yyyy-MM-dd HH:mm:ss} %s%e%n


quarkus.log.category."io.quarkus.http.access-log".handlers=access-log,access-console
quarkus.log.category."io.quarkus.http.access-log".use-parent-handlers=false

[phillip-kruger]

Awesome !

[jfslin]

@cescoffier Thank you so much, this works for me as well.

One more question though: using the default format string quarkus.log.handler.file.access-log.format=%d{yy-MM-dd HH\:mm\:ss} %-5p [%c{3.} - %M] %s%e%n works great, but changing it to other arguments (as noted https://quarkus.io/guides/http-reference#configuring-http-access-logs) leads to an exception. Is it because it's following the arguments outlined in https://quarkus.io/guides/logging#logging-format instead?

[error]: Build step io.quarkus.deployment.logging.LoggingResourceProcessor#setupLoggingRuntimeInit threw an exception: java.lang.IllegalArgumentException: Encountered an unknown format character
        at org.jboss.logmanager.formatters.FormatStringParser.getSteps(FormatStringParser.java:228)
        at org.jboss.logmanager.formatters.PatternFormatter.setPattern(PatternFormatter.java:80)
        at org.jboss.logmanager.formatters.ColorPatternFormatter.<init>(ColorPatternFormatter.java:54)
        at io.quarkus.runtime.logging.LoggingSetupRecorder.configureConsoleHandler(LoggingSetupRecorder.java:545)
        at io.quarkus.runtime.logging.LoggingSetupRecorder.createNamedHandlers(LoggingSetupRecorder.java:411)
        at io.quarkus.runtime.logging.LoggingSetupRecorder.initializeBuildTimeLogging(LoggingSetupRecorder.java:314)
        at io.quarkus.deployment.logging.LoggingResourceProcessor.setupLoggingRuntimeInit(LoggingResourceProcessor.java:316)
        at java.base/java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:733)
        at io.quarkus.deployment.ExtensionLoader$3.execute(ExtensionLoader.java:854)
        at io.quarkus.builder.BuildContext.run(BuildContext.java:256)
        at org.jboss.threads.ContextHandler$1.runWith(ContextHandler.java:18)
        at org.jboss.threads.EnhancedQueueExecutor$Task.doRunWith(EnhancedQueueExecutor.java:2516)
        at org.jboss.threads.EnhancedQueueExecutor$Task.run(EnhancedQueueExecutor.java:2495)
        at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1521)
        at java.base/java.lang.Thread.run(Thread.java:1583)
        at org.jboss.threads.JBossThread.run(JBossThread.java:483)

        at io.quarkus.builder.Execution.run(Execution.java:123)
        at io.quarkus.builder.BuildExecutionBuilder.execute(BuildExecutionBuilder.java:79)
        at io.quarkus.deployment.QuarkusAugmentor.run(QuarkusAugmentor.java:159)
        at io.quarkus.runner.bootstrap.AugmentActionImpl.runAugment(AugmentActionImpl.java:331)

The ones I've tried are (none of these work):

• quarkus.log.handler.file.access-log.format=%s, %B, %D, %m, %R, %h, %u
• quarkus.log.handler.file.access-log.format=%s, %B, %D, %m, %R, %<q, %{i,User-Agent}, %h, %u
• quarkus.log.handler.file.access-log.format=%{RESPONSE_CODE}r, %{BYTES_SENT}b, %{RESPONSE_TIME}ms,%{METHOD}, %{REQUEST_PATH}, %{QUERY_STRING}, %{i,User-Agent}, %{REMOTE_HOST}, %{REMOTE_USER}

[cescoffier]

Yes, this approach uses the JBoss Logging argument, so, you should use https://quarkus.io/guides/logging#logging-format.

I didn't know we have multiple ways (3 to be exact) to write the access.log. We may want to "streamline" this a bit...

[jfslin]

Sounds good. Thank you for responding so quickly.