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

[release-5.7] Loki search does not allow special chars

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done-Errata
    • Icon: Undefined Undefined
    • Logging 5.7.6
    • Logging 5.7.1
    • Log Console
    • False
    • None
    • False
    • NEW
    • VERIFIED
    • Prior to this change, the observability Loki console search field did not accept special chars that should be escaped. This change allows special characters to be escaped when the content filter is used.
    • Bug Fix

      Description of problem:

      When using the observability loki console, the search field does not accept special chars that should be escaped. For example, introduce the term "manager-role" (with quotes).

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

      4.13 with logging 5.7.1

      How reproducible:

      Alwasy

      Steps to Reproduce:

      1. Install the loki stack and configure the logging operator to use it
      2. Select the loki search
      3. In content, introduce some text between quotes, like "manager-role"
      

      Actual results:

      An exception in the search

      Expected results:

      Search using an escaped sequence

      Additional info:

      https://grafana.com/blog/2021/01/05/how-to-escape-special-characters-with-lokis-logql

            jezhu@redhat.com Jenny Zhu
            rgordill1@redhat.com Ramon Gordillo Gutierrez
            Kabir Bharti Kabir Bharti
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: