I have a Tomcat web app that checks its configuration integrity in a listener. If an issue is found it throws an exception and the deploy is aborted. This exception is logged just fine in a log file in Tomcat's directory on disk but for some reason it does not appear in AWS stream. Once the app is deployed the logs do get through to AWS.
In other words the first logger does work in the above scenario whilst the second one doesn't.
I have a Tomcat web app that checks its configuration integrity in a listener. If an issue is found it throws an exception and the deploy is aborted. This exception is logged just fine in a log file in Tomcat's directory on disk but for some reason it does not appear in AWS stream. Once the app is deployed the logs do get through to AWS.
In other words the first logger does work in the above scenario whilst the second one doesn't.
logback.zip