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

[release-5.8] Disable automatic discovery of log level in Loki for OpenShift Logging

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Done
    • Icon: Normal Normal
    • Logging 5.8.16
    • Logging 5.8.14
    • Log Storage
    • None
    • False
    • None
    • False
    • NEW
    • VERIFIED
    • See LOG-6320
    • Bug Fix
    • Log Storage - Sprint 261, Log Storage - Sprint 262, Log Storage - Sprint 263, Log Storage - Sprint 264

      Recent versions of Loki contain an automatic discovery of log levels if none is present in structured metadata ("discover_log_levels" in the Documentation).

      The collector configuration created by the Cluster Logging Operator already contains a section which does discovery of log level, but because it uses a different field to encode this information this causes the automatic discovery of Loki to evaluate the message as well.

      Because this leads to different results, I think it would be better to disable Loki's discovery feature and rely on the configuration in the collector, which is under the control of our project. This should reduce confusion by two different values appearing in the log entries.

              rojacob@redhat.com Robert Jacob
              rojacob@redhat.com Robert Jacob
              Kabir Bharti Kabir Bharti
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: