Error Logging

[Marvin Addison]

I recently noticed that I wasn't getting full stack traces in
idp-process.log, and investigated to find that the behavior caused by the
use of %ex{short} in the logback configs. I have some concerns about that.
While I appreciate the desire to limit noise caused by huge Spring/Jetty
stack traces, displaying the first line of an error is hardly enough to get
to the root cause in many cases. The ideal behavior in my experience would
be to display the fist N lines of the trace for every exception in the
error stack. Seeing the cause is vital in many if not most cases, and this
behavior provides the best of both: insight while limiting noise. It's
important enough that I'd be willing to take an AI to find or develop a
component to provide this behavior.

M
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://shibboleth.net/pipermail/dev/attachments/20150320/4612ca31/attachment.html