Uploaded image for project: 'OpenShift Logging'
  1. OpenShift Logging
  2. LOG-1717

Add multi-line exception detection to processing pipeline

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Critical Critical
    • Logging 5.3.0
    • None
    • Log Collection
    • None
    • 5
    • False
    • False
    • NEW
    • OBSDA-113 - Support aggregating back multi-line log messages into a single log message
    • NEW
    • Logging (Core) - Sprint 207, Logging (Core) - Sprint 208

      Story

      As a provider of a service that is deployed on OpenShift,
      I want multi-line exceptions to be captured as a single log event
      So that I see error trace logs as a single event

      Acceptance Criteria

      • Multiline exception traces are forwarded as single log entries (i.e.)
        Exception in thread "main" java.lang.NullPointerException
                at com.example.myproject.Book.getTitle(Book.java:16)
                at com.example.myproject.Author.getBookTitles(Author.java:25)
                at com.example.myproject.Bootstrap.main(Bootstrap.java:14)
        

      Notes

      • EOL characters are stripped by CRIO. We should not guarantee the final message will appear exactly as the original
      • Functional tests should be added to cover all the supported stack's by the plugin
      • We should consider adding a feature to the plugin to add back newline char in assembled messages (if possible)

          There are no Sub-Tasks for this issue.

              jcantril@redhat.com Jeffrey Cantrill
              jcantril@redhat.com Jeffrey Cantrill
              Kabir Bharti Kabir Bharti
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: