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

openshift.sequenceId is missing when openshift.labels.myLabel is used

XMLWordPrintable

    • Logging (Core) - Sprint 220

      BACKGROUNG:
      Logs are appearing in incorrect sequence in Kibana for this an issue was raised and was fixed in Logging 5.4.0.
      [+] https://issues.redhat.com/browse/LOG-2099

      The bug is actually fixed for configuration without structuredTypeKey: openshift.labels.myLabel

      When structuredTypeKey: openshift.labels.myLabel is not used in CLF openshift.sequence is created in below way

      ~~~
      {
      "_index" : "app-000008",
      .....
      .....
      "openshift" :

      { "sequence" : 158990 }

      ,
      ~~~
      Example included with Kibana images in https://access.redhat.com/solutions/6962533

      ISSUE:
      When structuredTypeKey: openshift.labels.myLabel is used in CLF openshift.labels.myLabel is created and openshift.sequence is not created
      ~~~
      "_index" : "app-000001",
      ....
      ....
      "openshift" : {
      "labels" :

      { "myLabel" : "devagiri" }

      ~~~
      Please see the attached images of CLF and Kibana where openshift.sequence is missing.

        1. Sequence missing.png
          Sequence missing.png
          102 kB
        2. CLF.png
          CLF.png
          40 kB

              jcantril@redhat.com Jeffrey Cantrill
              rhn-support-anisal Apurva Nisal
              Votes:
              1 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: