New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
collect access.log to docker log driver #84
Comments
I think the following section in the default <!-- Access log processes all example.
Documentation at: /docs/config/valve.html
Note: The pattern used is equivalent to using pattern="common" -->
<Valve className="org.apache.catalina.valves.AccessLogValve" directory="logs"
prefix="localhost_access_log" suffix=".txt"
pattern="%h %l %u %t "%r" %s %b" /> If all else fails, you could create a short |
I've modified my conf/server.xml, this works for me:
|
Nice, thanks for confirming @srossross! 👍 |
I have a containerized app that spews it's log messages to standard out. It runs on tomcat, and we created a symbolic link from the tomcat access log to /dev/stdout which seemed to work, but we found that occasionally the application messages were clashing with the access log messages. I'm wondering if there's any reason to think this /proc/self/fd approach would be any better? |
In server.xml
This sends the accesslog into stdout. |
Tomcat catalina.log is collected to stdout,but access.log is output to file in the container。
How do I to collect access.log by docker log driver?
The text was updated successfully, but these errors were encountered: