Uploaded image for project: 'Log4j 2'
  1. Log4j 2
  2. LOG4J2-1

Custom rendering of exception associated with logging event

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.0-alpha1
    • Component/s: Layouts
    • Labels:
      None

      Description

      In http://marc.info/?l=log4j-user&m=120898200413495&w=2, Robert Pepersack essentially asks for a method of overriding the use of Exception.printStackTrace() to capture the stack trace of the associated exception. This can partially be done in log4j 1.x by providing a custom layout that returns false for ignoresThrowable and then performs the rendering of the exception as part of the layout. However, it would not affect LoggingEvents that were deserialized. Also, if an AsyncAppender is used, the layout would be rendering an exception after it may have been modified.

      The log4j 2 pipeline should not have this issue as the extraction phase done by the layout should pull any info needed from the exception and the responsibility would not be split among WriterAppender, ThrowableInformation and the layout. So likely there is no additional design criteria involved here, just the final design should be checked that it satisfies this use case.

        Attachments

          Activity

            People

            • Assignee:
              ralph.goers@dslextreme.com Ralph Goers
              Reporter:
              carnold@apache.org Curt Arnold
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: