| |||||||||||||
They should be paying attention to the lumberjack projectThey should be paying attention to the lumberjack projectPosted Apr 15, 2012 6:33 UTC (Sun) by lindi (subscriber, #53135)In reply to: They should be paying attention to the lumberjack project by jzbiciak Parent article: Toward more reliable logging
You'd also want to have a way to extract that "eth0" in a programmatic way.
(Log in to post comments)
They should be paying attention to the lumberjack project Posted Apr 20, 2012 21:18 UTC (Fri) by giraffedata (subscriber, #1954) [Link] You'd also want to extract the "0000:03:00.0", "r8169" (device driver name), and possibly "up".And the date, host, and source values aren't from the kernel, so they wouldn't be in there.
They should be paying attention to the lumberjack project Posted Apr 20, 2012 21:29 UTC (Fri) by dlang (✭ supporter ✭, #313) [Link]
the information may not be from the kernel, but by the time anything other than the log transport sees the data, it will need to be there (and arguably the timestamp should be put there by the kernel)
They should be paying attention to the lumberjack project Posted Apr 20, 2012 22:28 UTC (Fri) by giraffedata (subscriber, #1954) [Link] Aren't we talking about in what form the kernel should produce log messages?
They should be paying attention to the lumberjack project Posted Apr 20, 2012 22:30 UTC (Fri) by dlang (✭ supporter ✭, #313) [Link]
I had wandered a bit from that, but yes, that's where we started.
And the kernel should put the timestamp on the messages it generates, you don't know how long it's going to be before some other process picks them up and could add a timestamp to them.
|
|||||||||||||