-
Bug
-
Resolution: Duplicate
-
Normal
-
None
-
Logging 6.3.0
-
Incidents & Support
-
0
-
False
-
-
False
-
NEW
-
NEW
-
Bug Fix
-
-
-
Log Storage - Sprint 272
- JSONParserErr when using OpenTelemetry data model in the Collector.
- After configuring the Logging v6.3 for log forwarding to Loki v6.3 using the OpenTelemetry data model as documented [1], Infrastructure and application logs under Observe => Logs section indicating following error message:
__error__JSONParserErr
__error_details__Value looks like object, but can't find closing '}' symbol
- Logging and Loki Operator version:
$ oc get csv NAME DISPLAY VERSION REPLACES PHASE cluster-logging.v6.3.0 Red Hat OpenShift Logging 6.3.0 Succeeded cluster-observability-operator.v1.1.1 Cluster Observability Operator 1.1.1 cluster-observability-operator.v1.1.0 Succeeded loki-operator.v6.3.0 Loki Operator 6.3.0 Succeeded
Steps to Reproduce:
**
- Deploy CLO v6.3 and Loki v6.3, and configure Loki with schema version v13.
- Create a clusterLogForwarder custom resource with following configuration:
apiVersion: observability.openshift.io/v1 kind: ClusterLogForwarder metadata: name: collector namespace: openshift-logging annotations: observability.openshift.io/tech-preview-otlp-output: "enabled" spec: managementState: Managed outputs: - lokiStack: authentication: token: from: serviceAccount dataModel: Otel target: name: logging-loki namespace: openshift-logging name: default-lokistack tls: ca: configMapName: openshift-service-ca.crt key: service-ca.crt type: lokiStack pipelines: - inputRefs: - application - infrastructure - audit name: default-logstore outputRefs: - default-lokistack serviceAccount: name: collector
- Navigate to OpenShift WebConsole => Administrator => Observe => Logs => Check Application or Infrastructure logs.
Here is the Screenshot for better understanding:
Expected results:
Not "{}error{} JSONParserErr" observed in the infrastructure and application logs.
- duplicates
-
-
- New
-
