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

JSONParserErr when using OTLP in the collector

XMLWordPrintable

    • False
    • None
    • False
    • NEW
    • NEW
    • Hide
      Currently, when looking at logs in the Console which were stored using the new OpenTelemetry data model for the LokiStack output, all results will contain a "JSONParserErr" and an error message about the entry not being parseable as JSON. The previous data model encoded all information as JSON and the Console still uses a query which tries to parse that information, so that both old and new entries are decoded properly. The error is not present in the stored data and only a result of the query and can be ignored.
      Show
      Currently, when looking at logs in the Console which were stored using the new OpenTelemetry data model for the LokiStack output, all results will contain a "JSONParserErr" and an error message about the entry not being parseable as JSON. The previous data model encoded all information as JSON and the Console still uses a query which tries to parse that information, so that both old and new entries are decoded properly. The error is not present in the stored data and only a result of the query and can be ignored.
    • Known Issue
    • Moderate

      Description of problem:

      When it's configured Logging v6.2 for log forwarding to Loki v6.2 using OTLP as documented [0], it's observed in the OpenShift Console UI when displayed the infrastructure and application logs indicating:

      __error__ JSONParserErr 
      __error_details__ Value looks like object, but can't find closing '}' symbol

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

      $ oc get csv -n openshift-logging|grep "logging"
      cluster-logging.v6.2.0 Red Hat OpenShift Logging 6.2.0 cluster-logging.v6.1.2 Succeeded
      

      How reproducible:

      Always

      Steps to Reproduce:

      1. Deploy CLO v6.2 and Loki v6.2 and configure Loki with schema version v13
      2. Create a clusterLogForwarder custom resource with the next yaml:
        apiVersion: observability.openshift.io/v1
        kind: ClusterLogForwarder
        metadata:
          name: collector
          namespace: openshift-logging
          annotations:
            observability.openshift.io/tech-preview-otlp-output: "enabled" 
        spec:
          serviceAccount:
            name: collector
          outputs:
          - name: loki-otlp
            type: lokiStack 
            lokiStack:
              target:
                name: logging-loki
                namespace: openshift-logging
              dataModel: Otel 
              authentication:
                token:
                  from: serviceAccount
            tls:
              ca:
                key: service-ca.crt
                configMapName: openshift-service-ca.crt
          pipelines:
          - name: my-pipeline
            inputRefs:
            - application
            - infrastructure
            outputRefs:
            - loki-otlp
        

        Actual results:

      It's observed in the Observability UI Logging that in the infrastructure and application logs inside the log in Loki is present the next two entries:

      __error__    JSONParserErr
      __error_details__  Value looks like object, but can't find closing '}' symbol
      

      It could be also being observed in the next screenshot:

      Expected results:

      Not "{}error{} JSONParserErr" observed in the infrastructure and application logs.

      Additional info:

      [0] https://docs.openshift.com/container-platform/4.17/observability/logging/logging-6.1/log6x-about-6.1.html#quick-start-opentelemetry_

              Unassigned Unassigned
              rhn-support-ocasalsa Oscar Casal Sanchez
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: