Details
-
Bug
-
Resolution: Done-Errata
-
Undefined
-
Logging 5.7.1
-
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
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
Attachments
Issue Links
- clones
-
OCPBUGS-14902 Loki search does not allow special chars
-
- Closed
-
- git code review opened
-
LOG-4457 Loki search does not allow special chars
-
- Closed
-
- links to
-
RHSA-2023:4933 Logging Subsystem 5.7.6 - Red Hat OpenShift
- mentioned on
(1 mentioned on)