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

[release-5.2] Events listing out of order in Kibana 6.8.1

    XMLWordPrintable

Details

    • False
    • False
    • NEW
    • VERIFIED
    • Hide
      With this change, a sequence number is added to the log record to help order entries that have matching timestamps. Prior to this change, some log forwarder outputs do not recognize nanosecond precision and have no way to order records that have matching timestamps.
      Show
      With this change, a sequence number is added to the log record to help order entries that have matching timestamps. Prior to this change, some log forwarder outputs do not recognize nanosecond precision and have no way to order records that have matching timestamps.
    • Logging (Core) - Sprint 216, Logging (Core) - Sprint 218

    Description

      We are seeing an issue if 2 (or more) log messages came out with the same millisecond in their timestamp, their order in Kibana output (if sorted by timestamps) could be unpredictably listed out of order.

      Attachments

        Issue Links

          Activity

            Public project attachment banner

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

              People

                jcantril@redhat.com Jeffrey Cantrill
                rhn-support-sjhanwar Sarvesh Jhanwar (Inactive)
                Giriyamma Karagere Ramaswamy Giriyamma Karagere Ramaswamy
                Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved: