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

Japanese log messages are garbled at Kibana

    XMLWordPrintable

Details

    • False
    • None
    • False
    • NEW
    • VERIFIED
    • Before this update, non latin characters displayed incorrectly in Kibana. With this update Kibana displays all valid UTF-8 symbols correctly.
    • Hide

      1. Install Cluster Logging version 5.4.2.
      2. Create a project and pod.
      3. Create Japanese log message in pod.
      $ oc rsh sample-pod-xxxx
      sh-4.4$ echo "こんにちは" > /proc/1/fd/1
      sh-4.4$ exit
      4. Confirm the pod log message is not garbled.
      $ oc logs sample-pod-xxxx
      こんにちは
      5. Access the Kibana console and create "app-*" index pattern
      6. Add filter "message", you can confirm that the logs are garbled.

      Show
      1. Install Cluster Logging version 5.4.2. 2. Create a project and pod. 3. Create Japanese log message in pod. $ oc rsh sample-pod-xxxx sh-4.4$ echo "こんにちは" > /proc/1/fd/1 sh-4.4$ exit 4. Confirm the pod log message is not garbled. $ oc logs sample-pod-xxxx こんにちは 5. Access the Kibana console and create "app-*" index pattern 6. Add filter "message", you can confirm that the logs are garbled.
    • Log Collection - Sprint 221, Log Collection - Sprint 222

    Description

      Japanese log messages are garbled at Kibana in version 5.4.2.

      Japanese characters are not garbled in the previous version 5.3.8.

      Attachments

        Activity

          Public project attachment banner

            context keys: [headless, issue, helper, isAsynchronousRequest, project, action, user]
            current Project key: LOG

            People

              vparfono Vitalii Parfonov
              rhn-support-mmatsuta Masafumi Matsuta
              Anping Li Anping Li
              Votes:
              1 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: