search

deanhiller / databus

time series data in cassandra with visualization(NREL's opensource databus project)
Other
53 stars 21 forks source link

Log level does not seem to work #22

Closed hopcroft closed 10 years ago

hopcroft commented 10 years ago

Setting the log level in the configuration file with 

application.log

does not seem to affect the output from Play. I was assuming I could use the log4j levels TRACE, DEBUG, INFO, WARN, ERROR and FATAL ?

deanhiller commented 10 years ago

we need to remove that from application.conf. You can control log levels in very fine grained detail in the file logback.xml controlling even what certain classes log or whole packages or the whole system. You can even control if the logs go the screen vs. go to a file vs. go to a database. google logback for more information on configuration of logging(There is tons of documentation on that). I think our default log files also tell the system to reread the log file every 30 seconds so you don't need to restart the system as well.

hopcroft commented 10 years ago

So DataBus is using logback, not log4j? And the application.log properties are not used?

deanhiller commented 10 years ago

logback and SLF4J(we use SLF4j) was created by the creator of log4j and works much better as well as being able to still log from 3rd party jars that use log4j, commons logging, jdk logging etc. etc. so we use logback.

I made a mistake earlier...you want to read the configuration of SLF4j not log4j.

and yes, we do not use application.conf at all for logging config. thanks, Dean

hopcroft commented 10 years ago

got it, thanks.