Loading...

Type: Bug
Resolution: Done
Priority: Major
Fix Version/s: Logging 5.4.0
Affects Version/s: None
Component/s: Log Collection
Labels:
- devel_ack+

Blocked:
False
Ready:
False
Docs QE Status:
NEW
QE Status:
VERIFIED
Release Note Text:

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.
Market:

Sprint:
Logging (Core) - Sprint 214, Logging (Core) - Sprint 215, Logging (Core) - Sprint 216, Logging (Core) - Sprint 217

SFDC Cases Links:
SFDC Cases Counter:
SFDC Cases Open:

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.