Feature changed by: Lukas Ocilka (locilka) Feature #318921, revision 10 Title: YaST should log time like dmesg and journalctl Requested by: Arvin Schnell (aschnell) Partner organization: openSUSE.org Description: YaST should log the time in its log-file like 'dmesg' and 'journalctl -- output short-monotonic' so that times in the various logs can be compared and events can be synchronized. Business case (Partner benefit): openSUSE.org: Easier to analyse logs in bug reports. Discussion: #5: Joachim Werner (joachimwerner) (2015-05-06 14:05:21) I've created a separate request for SP2 and removed SP1. Let's do the change for openSUSE in any case. + #9: Lukas Ocilka (locilka) (2016-01-18 10:14:25) (reply to #6) + I actually don't think this is a good idea. Both examples `journalctl` + and `dmesg` log in kind of a DB and can export this to different + formats (or by using filters). Yast log is written directly to disk as + is. + Moreover, the current format makes sense for most of the Yasters more + than the new one, because we are interested in "when" the problem + actually happened. We would not be able to distinguish one Yast run + from another if there was, e.g. a restart in between. + Additionally, if you check different logs in your /var/log/, they use + different formatting, but most of these use something similar to Yast. + The only acceptable way (having timestamp from the boot) in the Yast + log is ADDING this to the log, but definitely not replacing the current + date and time with something else. + Customer benefit is missing - what I see is a possible benefit for Yast + developers when comparing different logs. -- openSUSE Feature: https://features.opensuse.org/318921

Feature changed by: Jiri Srain (jsrain) Feature #318921, revision 15 Title: YaST should log time like dmesg and journalctl Requested by: Arvin Schnell (aschnell) Partner organization: openSUSE.org Description: YaST should log the time in its log-file like 'dmesg' and 'journalctl -- output short-monotonic' so that times in the various logs can be compared and events can be synchronized. Use Case: You have a bug report where some error is logged with seconds since system start (journalctl). Even if you have all logs there is currently no way to know what YaST did at that time. So I want "various logs can be compared and events can be synchronized". The feature request does not ask to drop the time in human readable format. So just logging the journalctl time at the start would be also fine. Business case (Partner benefit): openSUSE.org: Easier to analyse logs in bug reports. Discussion: #5: Joachim Werner (joachimwerner) (2015-05-06 14:05:21) I've created a separate request for SP2 and removed SP1. Let's do the change for openSUSE in any case. #9: Lukas Ocilka (locilka) (2016-01-18 10:14:25) (reply to #6) I actually don't think this is a good idea. Both examples `journalctl` and `dmesg` log in kind of a DB and can export this to different formats (or by using filters). Yast log is written directly to disk as is. Moreover, the current format makes sense for most of the Yasters more than the new one, because we are interested in "when" the problem actually happened. We would not be able to distinguish one Yast run from another if there was, e.g. a restart in between. Additionally, if you check different logs in your /var/log/, they use different formatting, but most of these use something similar to Yast. The only acceptable way (having timestamp from the boot) in the Yast log is ADDING this to the log, but definitely not replacing the current date and time with something else. Customer benefit is missing - what I see is a possible benefit for Yast developers when comparing different logs. + #11: Jiri Srain (jsrain) (2016-11-01 10:12:48) + Lukas, passing to you as we discussed, this comes from inside the team + and we should find ways to accommodate developers' needs. + Based on in-team discussion and agreement, feel free to postpone for + SLE13. -- openSUSE Feature: https://features.opensuse.org/318921