Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-9568

log parser should be able to generate a log indicating which rule was applied

    • Icon: Improvement Improvement
    • Resolution: Won't Fix
    • Icon: Minor Minor
    • log-parser-plugin
    • None

      In using the log parser, I have had amusing false negatives and false positives.

      I would be very helpful if there was a setting that created a log file showing the log file being applied, the rule being applied and the associated log file line.

      for example: (log_parser_debug_log_<project_name>build<build_number>.txt)

      Rule File: log_parsing_rules.txt

      error\t14\t345\tSomething bad happened to generate a fatal error.

      where

      • error is the label being applied
      • 14 is the line of the rules file
      • 345 is the line of the log being parsed
      • the remaining text is the line from the log

      Additionally, being able to specify the separator string (shown here as a tab) would be helpful.

          [JENKINS-9568] log parser should be able to generate a log indicating which rule was applied

          Charles Wilson created issue -
          Charles Wilson made changes -
          Description Original: In using the log parser, I have had amusing false negatives and false positives.

          I would be very helpful if there was a setting that created a log file showing the log file being applied, the rule being applied and the associated log file line.

          for example: (log_parser_debug_log_<project_name>_build_<build_number>.txt)

          Rule File: log_parsing_rules.txt

          error\t14\t345\tSomething bad happened to generate a fatal error.

          Additionally, being able to specify the separator string (shown here as a tab) would be helpful.
          New: In using the log parser, I have had amusing false negatives and false positives.

          I would be very helpful if there was a setting that created a log file showing the log file being applied, the rule being applied and the associated log file line.

          for example: (log_parser_debug_log_<project_name>_build_<build_number>.txt)

          Rule File: log_parsing_rules.txt

          error\t14\t345\tSomething bad happened to generate a fatal error.

          where

          - error is the label being applied
          - 14 is the line of the rules file
          - 345 is the line of the log being parsed
          - the remaining text is the line from the log

          Additionally, being able to specify the separator string (shown here as a tab) would be helpful.
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 139736 ] New: JNJira + In-Review [ 175141 ]
          Martin Reinhardt made changes -
          Resolution New: Won't Fix [ 2 ]
          Status Original: Open [ 1 ] New: Closed [ 6 ]

            rgoren rgoren
            charles_wilson_dell Charles Wilson
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: