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

[release-5.5] fluentd multiline exception plugin fails to detect JS client exception

    • Icon: Bug Bug
    • Resolution: Won't Do
    • Icon: Undefined Undefined
    • None
    • None
    • Log Collection
    • False
    • None
    • False
    • NEW
    • NEW
    • Before this update, a multiline exception from Javascript client could not be combined into a single line. After this update, fluentd can combine such type of exception into one output iine.
    • Bug Fix
    • Log Collection - Sprint 233, Log Collection - Sprint 234

      Description of problem:

      fluentd multiline exception plugin fails to detect JS client exception

      Version-Release number of selected component (if applicable):

      fluentd 1.14.6

      How reproducible:

      Always

      Steps to Reproduce:

      setup fluentd as collector and configure CLF to detect multiline exception detection.

      prepare an appilcation which generates following log lines

       

      Error    
          at bls (<anonymous>:3:9)    
          at <anonymous>:6:4    
          at a_function_name            
          at Object.InjectedScript._evaluateOn (http://<anonymous>/file.js?foo=bar:875:140)    
          at Object.InjectedScript.evaluate (<anonymous>) 

       

       

      Actual results:

      The output gets each exception line as a separate output line

      Expected results:

      The exception should be combined into one output iine.

      Additional info:

            [LOG-3919] [release-5.5] fluentd multiline exception plugin fails to detect JS client exception

            Closing this as there are no reported customer cases and we fixed in 5.7

            Jeffrey Cantrill added a comment - Closing this as there are no reported customer cases and we fixed in 5.7

            vparfono anli@redhat.com The issue this was cloned from seem to be verified now. It looks like this needs retesting on 5.5 as well and this issue should be part of the release. Please move it to the correct status, so that I know whether it should be attached to the 5.5.11 advisory.

            Robert Jacob added a comment - vparfono anli@redhat.com The issue this was cloned from seem to be verified now. It looks like this needs retesting on 5.5 as well and this issue should be part of the release. Please move it to the correct status, so that I know whether it should be attached to the 5.5.11 advisory.

            Anping Li added a comment - - edited

            Move back to POST, as we only fix partial issue.

            Anping Li added a comment - - edited Move back to POST, as we only fix partial issue.

            Anping Li added a comment -

            Verified on 5.5.10

            Anping Li added a comment - Verified on 5.5.10

              vparfono Vitalii Parfonov
              vimalkum@redhat.com Vimal Kumar
              Qiaoling Tang Qiaoling Tang
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: