| |||||||||||||
KS2011: Structured error loggingKS2011: Structured error loggingPosted Oct 25, 2011 19:21 UTC (Tue) by raven667 (subscriber, #5198)Parent article: KS2011: Structured error logging
Here is a crazy thought; is it possible at compile time to get a hash of the contents of the printk() call (before format string replacements) to generate a unique ID? That should give every unique version of a message a unique identifier that could be a key for searching and parsing. Other kinds of conventions or standards for the contents of a message, especially for multi-line messages, would be useful as well to simplify parsing but anything that requires massive changes all over the kernel is probably no good.
(Log in to post comments)
KS2011: Structured error logging Posted Oct 27, 2011 7:18 UTC (Thu) by epierre (subscriber, #60841) [Link]
If you change the format string to either correct a typo or add a little more information, the hash value changes, that makes the identifier very unstable.
KS2011: Structured error logging Posted Oct 27, 2011 11:10 UTC (Thu) by Felix.Braun (subscriber, #3032) [Link]
The thought of translating error messages was also floated. That would obviously change the has value. But then, I think that nowadays every sysadmin has some basic understanding of english. So I'm not so sure translation would even be necessary.
KS2011: Structured error logging Posted Nov 3, 2011 13:52 UTC (Thu) by renox (subscriber, #23785) [Link]
> But then, I think that nowadays every sysadmin has some basic understanding of english.
Totally wrong, just think about the use of Linux on desktops where each user is also a "sysadmin".
|
|||||||||||||