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

Vector Incorrectly Assigns Some Logs with a Level of "default"

XMLWordPrintable

    • False
    • None
    • False
    • NEW
    • NEW
    • Hide
      Before this change, the vector mistakenly set the 'default' log level. With this update, the detection of the log level has been improved via the enhancement of the regular expression (regexp) for log level detection, ensuring that the correct log level is now set.
      Show
      Before this change, the vector mistakenly set the 'default' log level. With this update, the detection of the log level has been improved via the enhancement of the regular expression (regexp) for log level detection, ensuring that the correct log level is now set.
    • Bug Fix
    • Log Collection - Sprint 243, Log Collection - Sprint 244, Log Collection - Sprint 245

      Description of problem:

      When using Vector as the logging collector, some log formats correctly contain the level, but are still getting assigned a level of "default" by Vector.  

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

      cluster-logging v5.6.6

      How reproducible:

      This happens consistently with logs from most, if not all, of the pods from the Advanced Cluster Management operator. There may be other operator logs outside of ACM this impacts as well.

      Steps to Reproduce:

      1. Install ACM on a three-node cluster
      2. Install cluster-logging v5.6.6 and the elasticsearch-operator on the cluster
      3. Configure the ClusterLogForwarder to send logs to the default Elastic using Vector
      4. Log into the local Kibana Discover dashboard and filter for level: "default" and kubernetes.namespace_name: "open-cluster-management-agent-addon"

      Actual results:

      Search results contain several entries labeled as level: "default", but the message clearly has a level of "info" or similar.

      Expected results:

      Search results contain entries that legitimately do not have a log level in the message.

      Additional info:

      Please see the attached for an example log file

       

              vparfono Vitalii Parfonov
              scarlisl@redhat.com Sean Carlisle
              Anping Li Anping Li
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: