Croway opened a new pull request, #1646:
URL: https://github.com/apache/camel-spring-boot/pull/1646

   …thout management access logs
   
   ## Requirements:
   * `management.server.port` must be different from main app port
   * Without separate port, both contexts share the same server and access log 
settings
   
   ## Tomcat Management Access Log Control
   
   `application.properties`:
   ```
   # Enable access logs for main application
   server.tomcat.accesslog.enabled=true
   server.tomcat.accesslog.directory=logs
   server.tomcat.basedir=./target
   
   # Separate management port (required)
   management.server.port=9090
   
   # Disable access logs for management/actuator only
   management.server.accesslog.enabled=false
   ```
   
   Result:
   * Main app (port 8080): Access logs written to access_log.<date>.log
   * Actuator (port 9090): No access logs
   
   ## Undertow Management Access Log Control
   
   `application.properties`:
   ```
   # Enable access logs for main application
   server.undertow.accesslog.enabled=true
   server.undertow.accesslog.dir=logs
   
   # Separate management port (required)
   management.server.port=9090
   
   # Disable access logs for management/actuator only
   management.server.accesslog.enabled=false
   ```
   
   Result:
   * Main app (port 8080): Access logs written to access_log.log
   * Actuator (port 9090): No access logs
   
   ## Jetty Management Access Log Control
   `application.properties`:
   ```
   server.jetty.accesslog.enabled=true
   server.jetty.accesslog.filename=./target/logs/jetty_access.log
   
   # Use separate port for management/actuator endpoints
   management.server.port=9090
   
   # Disable access logs for management context only
   management.server.accesslog.enabled=false
   ```
   
   Result:
   * Main app (port 8080): Access logs written to ./target/logs/jetty_access.log
   * Actuator (port 9090): No access logs


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to