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

[master] Console timestamps for log lines does not match log @timestamp

XMLWordPrintable

    • False
    • None
    • False
    • NEW
    • ON_QA
    • Prior to this update, the timestamps shown in the console logs did not match the @timestamp from the message. With this update we are now correctly setting the timestamp field that matches the message.
    • Bug Fix
    • Log Collection - Sprint 261, Log Collection - Sprint 262, Log Collection - Sprint 263, Log Collection - Sprint 264, Log Collection - Sprint 265, Log Collection - Sprint 266, Log Collection - Sprint 267
    • Important

      Description of problem:

      The console timestamps column for individual log lines does not align to the @timestamp field from the log record. There is generally a 10+ second difference. In EFK, the timestamps came from CRIO directly and was properly aligned.

      How reproducible:

      Seems to be always in our environment

      Steps to Reproduce:

          1. View logs in the console 
    2.
    3.

      Actual results:

      Different of 10+ seconds in time.

      Expected results:

      Times should be aligned

      Additional info:

              cahartma@redhat.com Casey Hartman
              rhn-support-mrobson Matt Robson
              Anping Li Anping Li
              Votes:
              3 Vote for this issue
              Watchers:
              12 Start watching this issue

                Created:
                Updated:
                Resolved: