You’re right, I should have shown this; luckily the Error Class’ getStackTrace() method contains everything we need to extract both the calling method so it can be presented to the Logging function (after a bit of String Manipulation.

A previous post of mine touches on this.

Thanks for the post!

One question … its not clear to me how you would get the methodName into every log message using this approach – without relying on a manual approach and a diciplined team like in Jesse Warden’s example.

I suppose one could define a logger for every single method but there must surely be a better solution.