We are trying to setup some automated alarming when errors are written to our log files. The problem we are having is that the message span multiple lines, with no obvious beginning or end to each message. I tried adding literals at the beginning and end of the conversion pattern, but that didn't work because the exception is written after the end of the pattern.
The best solution I could think of is to support a pattern ("%e"?) for the
exception string in the PatternLayout.
If the pattern contains %e, the layout would return false for
IgnoresException, and it would render the exception as part of the
pattern, which would let the end marker come after the exception.
If the pattern does contains %e, it would return true for
IgnoresException, and the behavior would be unchanged.
Make sense?
Has anybody done this?
If not, if I do it will somebody commit it?
Thanks,
Dave
<<attachment: winmail.dat>>
