Uploaded image for project: 'ONAP Operations Manager'
  1. ONAP Operations Manager
  2. OOM-885

Beijing oom component log messages missing in Elasticsearch

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Medium
    • Resolution: Done
    • Affects Version/s: Beijing Release
    • Fix Version/s: Beijing Release
    • Labels:
      None

      Description

      There are Beijing oom component log messages that do not appear in Elasticsearch. The following issues exist: 

      1. the log source field is missing for log4j log events
      2. the oom component logs are not parsed by logstash because many logback log patterns exist
      3. some oom component split MDC fields with "," in addition to the existing "\t"

       

        Attachments

          Issue Links

          No reviews matched the request. Check your Options in the drop-down menu of this sections header.

            Activity

              People

              • Assignee:
                nealch Neal Chatterley
                Reporter:
                nealch Neal Chatterley
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: