Is it possible to redirect Gradle logs to slf4j/logback.
I know you can use a custom SLF4J logger https://docs.gradle.org/current/userguide/logging.html#sec:sending_your_own_log_messages, but where should the logback.properties should sit?
Also, besides your messages can you redirect all Gradle messages?
You can see the rules for loading config in the logback documentation here https://logback.qos.ch/manual/configuration.html
Specifically:
Logback tries to find a file called logback-test.xml in the classpath.
If no such file is found, logback tries to find a file called logback.groovy in the classpath.
If no such file is found, it checks for the file logback.xml in the classpath..
Related
I have updated my log4j version to log4j-core 2.16. I have added one more dependency as per the document. And I am using log4j2.properties for the appender and file generation process. But my file is not generating in the given location.
Thanks in advance!!
I am trying to do a setup for production environment, so I wanted to keep log4j.properties out of my application jar file.
For that I have kept my application.properties and log4j.properties files parallel to my spring-boot jar file. And I have given logging.config: file:log4j.properties in my application.properties. This doesn't seem to work. Spring is still picking up the log4j.properties file which is placed inside the jar file.
I have tried giving the absolute path in logging.config property like C:\Users\furquan\project\jars\log4j.properties, but it still the log4j.properties that was being used was the one inside the jar file.
Please help, its important !!!
-Dlogging.config=/path/to/log4j.properties
Or you can specify it in your application.properties or bootstrap.properties.
From 26.5 Custom log configuration
And just a note:
After spring boot 1.4, Log4j 1 support has been removed. So maybe you can consider use the default logback, or use log4j2 instead.
In a springboot application, I have a single jar, and then a subdirectory config with application.properties, applicationContext.xml, and log4j...properties file.
I am trying to externalize the log4j config. The application.properties is externalized this way.
But, when springboot runs it is using the log4j config file from within the jar file. By using the -Dlog4j.debug option I can see that log4j uses my external file first, but when spring starts it overrides the log4j setting with the one in the jar.
here is an example startup (with all options)
java -Dlog4j.debug
-Dlogging.config="file:/opt/config/log4j-qa.properties"
-Dlog4j.configuration="file:/opt/config/log4j-qa.properties"
-jar /opt/myjarName.jar
--spring.config.location=/opt/config/
on first startup log4j states
log4j: Reading configuration from URL file:/opt/config/log4j-qa.properties
then on springboot start
log4j: Reading configuration from URL jar:file:/opt/dms-events-api.jar!/log4j-qa.properties
but I want it to read only the external file file:/opt/config/log4j-qa.properties
resolution:
In our application we had line
#ImportResource("classpath:applicationContext.xml")
which then defined the log4j properties file from the classpath:
the simple solution
1. create a /config directory at the root of the api application and put the properties files there
2. remove the ImportResource line, it isn't needed now
3. add a line to the the application.properties file
logging.config=file:config/log4j-${our environment var}.properties
the explanation
By creating a /config directory at the root of the project then
we can work in eclipse as usual and find our properties files.
--and then to externalize configs
simply add a config directory off of where the application jar is and put properties files there.
Two problems are there:
Configuration for externalise: - Tried and works below one for me in spring boot jar
-Dlog4j.configuration=file:/Users/test/Any-Folder/log4j.properties
Spring logging takes over - for that you need to exclude the logging module. PFB the config for Gradle build.
configurations {
all*.exclude module : 'spring-boot-starter-logging'
}
I have a spring-boot application with apache camel and log4j2 as the underlying log provider. Is it possible to use camel log component to write to the log files as configured by the log4j2.xml?
Below jar files are there in the classpath:-
log4j-over-slf4j-1.7.16.jar
logback-classic-1.1.5.jar
logback-core-1.1.5.jar
log4j-api-2.4.1.jar
log4j-core-2.4.1.jar
jcl-over-slf4j-1.7.16.jar
jul-to-slf4j-1.7.16.jar
slf4j-api-1.7.16.jar
You currently have two logger implementations configured: Log4j 2 and Logback. If you want to do all your logging with Log4j2 then you need to add the Log4j SLF4J bridge and remove the Logback jars. I also recommend you use the latest Log4j 2 version (2.6.1). That gives the following dependencies:
log4j-api-2.6.1.jar
log4j-core-2.6.1.jar
log4j-slf4j-impl-2.6.1.jar (routes SLF4J API calls to Log4j 2)
log4j-jcl-2.6.1.jar (routes Commons Logging API calls to Log4j 2)
log4j-jul-2.6.1.jar (also set system property java.util.logging.manager to org.apache.logging.log4j.jul.LogManager)
slf4j-api-1.7.16.jar
You don't need:
log4j-over-slf4j-1.7.16.jar
logback-classic-1.1.5.jar
logback-core-1.1.5.jar
jcl-over-slf4j-1.7.16.jar
jul-to-slf4j-1.7.16.jar
About configuration, by default Log4j2 looks for a file called log4j2.xml in the classpath, but you can also specify the location with a system property.
The Log4j 2 manual is much better than the Log4j 1 documentation and shows many example configurations.
We are running OSGI bundles with pax-runner. We are logging using logback over slf4j.
The problem is logback tries to look for logback.xml in classpath, but in pax-runner where should I place logback.xml so that pax-runner configure logback accordingly?
I have tried with JoranConfigurator to load logback.xml which is included in bundle classpath, but it assumes classpath as the container in which the bundle is running (in my case it is runner folder where all the bundle jars are placed).
Any help would be appreciated.
Thanks in advace.
The usual approach would be to create a fragment bundle that is attached to the logback bundle and put logback.xml in there. Fragment bundles "extend" other bundles, so their contents are available to the classloader of the host bundle. This way, logback can find logback.xml in the classpath.
Another solution would be to configure logback to read the configuration
file from outside the classpath.
This can be done by setting VM options -Dlogback.configurationFile=/dir/conf/logback.xml