On 2021-11-05 12:37, Imobach Gonzalez Sosa wrote:
In our case, I would say that our logs are not ready to be shown to the end user.
No, they definitely are not. They are much too detailed. They were never meant for end users. Logging is done on many levels, and the log level is even configurable. An end user needs messages that are specifically designed for an end user; i.e. - communicating in terms that an end user can understand - translated (!) messages [*] - the right amount of information, i.e. one line per message - don't swamp the user with irrelevant details [*] If anybody considers that or even thinks loudly about it, I will refuse handling any bugs in the future. ;-) Just think about an y2log full of messages in Finnish or Hungarian language; you don't even need to go as far as Chinese or Korean. That would completely defeat the purpose of the y2log as a debugging tool for us.
They contain a lot of unneeded stuff, there are typos, and so on. It is maybe time to think about cleaning up our logs? 🙂
It's ALWAYS time for cleaning up the logs. I have been asking for that for many years. But this is not the reason for that: We have different needs from logs than an end user. We need more details (and I'd very much prefer proper formatting, not just dumping 10k of garbage in one single line) and better classification, e.g. not allowing external tools like Dracut to dump every message on stderr because of insane limitations of other tools that grab those messages. But that's another story for another day. Kind regards -- Stefan Hundhammer <shundhammer@suse.de> YaST Developer SUSE Software Solutions Germany GmbH GF: Ivo Totev; HRB 36809, AG Nürnberg