Although, I see a lot of code that's written to log every entry and exit point from each and every method called it isn't one of the good programming practices (it's surprising to some).
The only scenario when you would find this information useful is when you're debugging an exception. But the trace of every method invoked before the exception was thrown is already available in the exception's stack trace which leaves this kind of logging redundant.
It's only at places where the exception handling is already questionable that it would help. For e.g, the usual approach of log and forget (to some this is what exception handling is) without giving any serious thought to whether the exception should get escalated or even halt execution or not, and the just plain horrible eating exceptions up with catch (exception e) {// nothing happened}.