No maters which tool you use, but you MUST log !
If you develop an application of more then 3 lines of code (and do not participate to a Java Compact Code Competition), at least one every 5 should be a log line.
The worst parts of programming are documenting and then logging, specially because most time we add add and add logging during the troubleshooting of bugs, but then we never rationalize them and so thousands of useless logs are generated and the really useful few ones got lost in an ocean of noise.
The core of a good logging is the choose of the right detail and information you put into the messages, and of a tool that enable you to easily activate and set the needed level at runtime with out overloading too much the execution of the application.
As almost all the technical works you must find the right equilibrium between too much and too few, and you can only use your thumb as a meter.
But you MUST always keep in your mind the good old rule:
IF YOU DO NOT LOG YOU’LL NEVER KNOW WHAT YOU ARE DOING WRONG !